EIP-7702 Wallet Delegation, Permissions, and Security Trade-Offs
Summary
The document explains how EIP-7702 lets an externally owned account delegate to smart-contract code for a transaction while retaining its EOA role. It presents EOAs as the ultimate account owners: they can change delegated implementations or transact directly, bypassing the delegated account’s validation. These powers create security and storage concerns because delegated code may access shared account storage, making careful state management important.
The article outlines wallet features the authors consider useful for adoption: atomic batches such as approval plus swap, alternative gas payment or sponsorship, scoped session permissions, and attention to gas costs. It also describes a hardware-wallet-centered ownership model, in which limited permissions could let other accounts transact while containing the damage from a compromised permissioned account. These are design proposals and expectations, not measured results. The text provides no implementation details, security proofs, or cost benchmarks, and its upgrade timing is presented as a schedule rather than verified outcome.
Key ideas
- EIP-7702 allows an EOA to delegate account behavior to smart-contract code while remaining the root owner.
- An EOA can redelegate to another implementation or submit transactions that bypass delegated validation.
- Shared storage across delegates raises collision and account-state corruption risks.
- Batch execution, gas abstraction, and scoped sessions are proposed ways to improve wallet usability.
- Minimal smart-account logic and constrained permissions are presented as ways to manage costs and security.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.