ERC-4337: Account Abstraction Using Alt Mempool

Paper title ERC-4337: Account Abstraction Using Alt Mempool
Authors Vitalik Buterin; Yoav Weiss; Dror Tirosh; Shahaf Nacson; Alex Forshtat; Kristof Gazso; Tjaden Hess
Created September 29, 2021
Status Final Standards Track ERC
Project Ethereum
License CC0 (copyright and related rights waived)
Official source Final ERC-4337 specification and copyright notice

This page is an educational summary of a technical specification, not a verbatim reproduction or financial advice. The official EIP identifies its authors and states that copyright and related rights are waived under CC0. Consult the specification for the normative rules.

Protocol documentation Documentation
Directories Ethereum Whitepapers & Research

ERC-4337 describes one way to add programmable account behavior to Ethereum without changing the consensus protocol or introducing a new consensus-layer transaction type. A smart account uses the account-abstraction model to create a UserOperation; a bundler transports it through a separate operation-mempool process; and an EntryPoint contract validates and executes it. This design adds wallet and service infrastructure, so a wallet’s features and security still depend on its own implementation.

Why the proposal uses a separate path

A normal externally owned account (EOA) authorizes transactions with a key and uses Ethereum’s ordinary transaction pool. A contract account can apply programmable rules, but a contract cannot originate an ordinary transaction by itself. ERC-4337 moves the account’s validation and execution rules into smart-account code while leaving Ethereum’s underlying consensus transaction format unchanged. Earlier designs that sought account abstraction through protocol changes are outside the scope of this mechanism.

ERC-4337 is an interface and set of rules for this higher-layer flow. It does not make every existing wallet an ERC-4337 account, guarantee that every EVM network supports a particular deployment, or automatically add recovery or sponsored fees to a wallet.

What a UserOperation contains

A UserOperation describes an action requested by a smart account. The current specification includes the sender account and nonce, call data, gas limits and fee fields, and the account’s signature data. It can also include factory data when an account needs to be deployed and optional Paymaster fields when another party agrees to cover gas. For EIP-7702 delegated accounts, the specification defines a special factory marker and initialization data. The fields presented to an account off-chain are encoded into a packed form for EntryPoint execution; old examples using only the earlier initCode and paymasterAndData layout should be read in their version context.

The signature field is interpreted by the account’s validation code. The standard does not itself provide a passkey, multi-signature policy, social recovery, or a session key. A wallet may implement one or more of those features, but users must check the specific wallet’s rules and recovery process.

How bundling and execution work

  1. The wallet builds and signs a UserOperation for its smart account.
  2. A bundler checks the operation against the supported validation and mempool rules, including simulation, before accepting or forwarding it.
  3. The bundler groups eligible operations into an ordinary Ethereum transaction that calls the relevant EntryPoint contract.
  4. EntryPoint calls the account’s validation logic, executes approved calls, and settles the operation’s gas cost from the account or its Paymaster arrangement.

The outer transaction still uses the network’s normal fee system. A bundler submits that transaction and expects the operation’s fee settlement to cover the work. Inclusion is not guaranteed: operations can fail validation, be rejected under a bundler’s rules, or wait while services or network conditions change.

Bundlers, EntryPoint, and staking

Bundlers are transaction services that accept UserOperations and submit bundles. The EIP defines validation, simulation, reputation, and mempool rules, but it does not require every bundler to stake ETH as a universal condition for participating. Stake and reputation rules apply to particular entities or validation behaviors. A Paymaster’s EntryPoint deposit used to pay gas is also distinct from any locked stake.

EntryPoint is the contract that processes a bundle and coordinates account validation, execution, and fee settlement. Implementations are versioned and deployments are network-specific; do not assume every EVM chain uses the same address or supports the same version. Wallet developers and users should verify the address, code, supported version, and chain from the project’s authoritative deployment information. The official account-abstraction contract release notes describe version-specific changes and warn integrators to verify deployments.

What a Paymaster can and cannot do

A Paymaster is an optional contract that agrees, under its own validation rules, to pay the gas cost for an eligible UserOperation. It must maintain an EntryPoint deposit for those charges; the deposit is separate from stake. A dapp or wallet can use this arrangement to sponsor a user’s operation, subject to its budget, eligibility rules, and service availability.

ERC-4337 does not change the network’s native gas settlement asset. A product may let a user reimburse a sponsor in an ERC-20 token, or may price sponsorship in another way, but that conversion or collection is application-specific. The Paymaster still needs the appropriate native-asset deposit to settle the operation through EntryPoint. “Gasless” therefore describes who pays on the user’s behalf, not a transaction with no network cost.

Relationship to EIP-7702

EIP-7702 is related to account abstraction but uses a different protocol mechanism. It lets an EOA authorize code delegation through a set-code transaction; the delegation can persist until it is changed or cleared. Ethereum’s Pectra upgrade, which included EIP-7702, activated on mainnet on May 7, 2025. The current ERC-4337 specification also describes how a delegated EIP-7702 account can participate in the UserOperation flow. This makes the mechanisms compatible in some designs, not interchangeable: ERC-4337 supplies the UserOperation, bundler, and EntryPoint path, while EIP-7702 adds a way for an existing EOA to authorize delegated code. Delegation does not remove the need to protect the account’s signing authority or to assess the code being authorized. See the official EIP-7702 specification and the Ethereum Foundation’s Pectra documentation.

Trade-offs and security considerations

Smart-account flexibility comes with more components to understand: wallet code, EntryPoint version, bundler service, and sometimes a Paymaster. Gas overhead depends on the account implementation, operation, network, and contract version, so one fixed overhead figure is not a general ERC-4337 guarantee. Service concentration or outages can affect availability, while a sponsor can change its policy or stop accepting operations.

Before using a smart account, check its validation and upgrade permissions, signer and recovery setup, supported networks, and any service provider’s sponsorship rules. A malicious or incorrectly configured delegated wallet or Paymaster can create losses or unexpected fees. ERC-4337 provides a processing framework; it does not certify an account contract or make every implementation equally safe.

Social Media Sentiment

A small sample of 2026 r/ethereum discussions shows interest in simpler wallet flows and flexible fee payment, alongside frustration about fragmented implementations and uneven support across wallets and networks. A July discussion asking which account-abstraction approach should become the standard focused on adoption by major wallets and token-fee support across L2s. A September discussion clarified that users may reimburse a sponsor in a token while the underlying gas is still settled in ETH, and debated whether a proposed protocol-level change would add something new. These are individual forum conversations, not a representative survey or a measure of overall user sentiment. Read the July 2026 discussion about implementation fragmentation and wallet adoption and the September 2026 discussion about gas sponsorship and native settlement.

Last updated: 2026-10

Related Terms

See Also

Sources

Last updated: 11 October 2026