
For most of Ethereum’s history an account was one of two things: a key-controlled address (an externally owned account, or EOA) that can sign transactions but holds no code, or a contract that holds code but cannot start a transaction on its own. Account abstraction is the long effort to blur that line so wallets can batch actions, let someone else pay gas, or recover from a lost key. Two standards now do most of that work, and they are often confused.
ERC-4337: smart accounts without a fork
ERC-4337 is an application-layer standard with status Final. Its abstract states that it “completely avoids the need for consensus-layer protocol changes”. Instead of sending a normal transaction, the wallet produces a UserOperation, which the spec describes as “a structure that describes a transaction to be sent on behalf of a user”. Bundlers collect UserOperations and submit them through a singleton EntryPoint contract. A paymaster, if used, is “a helper contract that agrees to pay for the transaction, instead of the sender itself”.
The cost of this approach is that the account must be a contract from the start. A user with an existing EOA has to move funds to a new address to get the features.
EIP-7702: code for an existing address
EIP-7702, “Set Code for EOAs”, is a core protocol change that shipped in the Pectra upgrade, activated on mainnet on 7 May 2025 at epoch 364032 according to ethereum.org. It adds a new transaction type (0x04). The account owner signs an authorization tuple naming a contract address; the protocol then writes a delegation designator, the bytes 0xef0100 followed by that address, into the account’s code. From then on, calls to the EOA run the delegated contract’s code in the EOA’s own context.
The address stays the same, so balances, approvals and history stay where they are. That is the practical gain over a fresh ERC-4337 account. The two are also complementary: a delegated EOA can point at code that is itself an ERC-4337-compatible account, and use bundlers and paymasters from there.
The risk that moved
EIP-7702 is unusually blunt about its main hazard. Its security section warns that “the code specified by an authorization has unrestricted access to the account” and that “few users have the level of sophistication to reasonably verify the code they are delegating to”. An authorization signed with chain ID 0 is valid on every chain that supports the feature. Signing a delegation is therefore closer to handing over the account than to approving a single token, and a malicious delegation request is a new phishing shape that wallet interfaces must catch.
Two further points are worth keeping straight. Delegation does not retire the original private key: the specification still allows an account whose code is a delegation indicator to originate transactions, so whoever holds that key keeps that power. A delegation can be cleared by delegating to the zero address, which the spec says resets the account’s code. And a delegated account is only as safe as the contract it points to, so an audit of that contract matters more than the wallet’s interface.
The Settlement Test
- What settles: for ERC-4337, the bundler’s transaction to the EntryPoint is an ordinary Ethereum transaction and settles like any other. For EIP-7702, the authorization itself is recorded in the type-0x04 transaction, and the delegation persists until replaced.
- What it costs: ERC-4337 adds verification overhead per UserOperation, paid by the user or a paymaster. EIP-7702 adds the cost of the set-code transaction once. Neither makes gas disappear; sponsorship changes who pays.
- What breaks: a bug in the account or delegated contract, a malicious delegation, or a paymaster that stops paying. In each case the protocol does exactly what was signed.
What to check in a wallet that offers these features
Which contract does the wallet delegate to, who wrote it, and has it been reviewed? Does the wallet show you the delegation target in plain language before you sign? Does it refuse chain-ID-0 authorizations unless you ask for them? And if a paymaster sponsors your gas, what happens when it stops? Our guide to account abstraction and ERC-4337 and the glossary entry on account abstraction cover the base concepts.
Primary sources
Educational content, human-edited and possibly AI-assisted. It describes how systems work and is not financial, legal or tax advice. Report an error via our corrections page.


