Account abstraction allows blockchain accounts to use programmable validation rules. In Ethereum, this expands beyond the traditional model in which an externally owned account authorises transactions through a private-key signature. It can support alternative signing policies, recovery arrangements, and different ways to pay transaction fees.12

Programmable policiesReport an errorSuggest an improvement

A wallet can require extra approvals for a large transfer, restrict transactions to selected destinations, or provide backup keys for recovery. These are examples of policies that account code can enforce; account abstraction does not give every wallet the same recovery or permission system. Ethereum's roadmap describes such flexibility as a way to improve both security and usability.2

Batching can combine related actions, such as approving a token and then spending it, in one atomic transaction. Sponsorship allows another party to cover fees, while restricted permissions can let an application perform a narrow set of actions without receiving unrestricted account control.3

ERC-4337Report an errorSuggest an improvement

ERC-4337 defines a route to account abstraction that does not require changes to Ethereum's consensus rules. A user submits a UserOperation, an instruction object processed by supporting infrastructure. A bundler includes one or more operations in a regular transaction that calls the EntryPoint contract.1

The account's code validates the operation. An optional paymaster can sponsor its execution, with fees charged against a deposit held through the EntryPoint. Sponsorship changes who pays; execution still consumes gas. Bundlers validate operations before including them, and the specification addresses denial-of-service risks from account and paymaster behaviour.1

EIP-7702Report an errorSuggest an improvement

EIP-7702 takes a complementary approach: an externally owned account can authorise delegation to contract code while retaining its address. The delegation persists beyond the transaction that installs it and can be replaced or cleared with another valid authorisation. Its specified uses include batching, sponsored fees, and restricted sub-keys.3

Ethereum activated EIP-7702 in the Pectra upgrade on 7 May 2025. ERC-4337 and EIP-7702 are distinct mechanisms: the former describes operation processing through contracts and bundlers, while the latter changes the protocol to permit account-code delegation.413

Further protocol workReport an errorSuggest an improvement

As of 31 October 2026, EIP-8141 remains a draft proposal for frame transactions: contract calls that separately handle validation, gas-payment approval, and execution. Ethereum's roadmap schedules frame transactions for Hegotá in 2027, while warning that the upgrade scope is not final. This is planned work, rather than an already activated replacement for ERC-4337 or EIP-7702.56

Security considerationsReport an errorSuggest an improvement

Programmable authority also makes the chosen code security-critical. EIP-7702 warns that a poorly implemented delegate can give an attacker near-complete control of an account. Its security discussion includes replay protection and signing the intended transaction parameters. Additional features therefore need correct implementation and clear authorisation; installing delegation alone does not provide a recovery policy or make an account safe.3

See alsoReport an errorSuggest an improvement

ReferencesReport an errorSuggest an improvement

  1. ^ a b c d Buterin, V., et al. ERC-4337: Account Abstraction Using Alt Mempool. https://eips.ethereum.org/EIPS/eip-4337 

  2. ^ a b Ethereum documentation. Account abstraction. https://ethereum.org/roadmap/account-abstraction/ 

  3. ^ a b c d Buterin, V., Wilson, S., Dietrichs, A., and lightclient. EIP-7702: Set Code for EOAs. https://eips.ethereum.org/EIPS/eip-7702 

  4. ^ Ethereum documentation. Pectra. https://ethereum.org/roadmap/pectra/ 

  5. ^ Buterin, V., et al. EIP-8141: Frame Transaction. Draft, accessed 2026-10-31. https://eips.ethereum.org/EIPS/eip-8141 

  6. ^ Ethereum documentation. Ethereum roadmap. Accessed 2026-10-31. https://ethereum.org/roadmap/