ERC-4337 is an Ethereum standard that lets smart contract accounts submit user-authorized actions through a separate UserOperation flow. A bundler forwards valid operations to an EntryPoint contract, which checks them and calls the account. ERC-4337 is one implementation of the broader idea of account abstraction; it does not replace Ethereum’s consensus transaction format.
| Directories | Ethereum Technology & Infrastructure |
|---|
How the flow works
- A wallet or application creates a UserOperation containing the requested action, account, fee limits, nonce, and account-defined authorization data.
- A bundler checks the operation against its supported rules and submits one or more operations through the EntryPoint in an ordinary on-chain transaction.
- The smart account validates the request and executes it. If a paymaster is included, that contract can agree to cover the operation’s gas cost under its own rules.
A UserOperation is not itself an Ethereum transaction. It is an application-layer request that becomes an on-chain action only after a bundler includes it. The account contract defines how signatures and permissions are checked, so two wallets using ERC-4337 can have different security and recovery features.
What it enables
Because the account supplies its validation and execution logic, a wallet can support features such as multisignature approval, passkeys, spending limits, batched calls, or sponsored fees. These are capabilities that a particular account, bundler, and paymaster may implement; the standard does not make every wallet support every feature or guarantee that a sponsor will pay.
Limits and security considerations
Operations can be rejected during simulation or execution, and users still depend on the account contract, bundler infrastructure, and any paymaster they choose. Separate operation mempools can apply different rules. Fees, sponsorship limits, recovery policies, and contract risk therefore vary by wallet and service. ERC-4337 changes the wallet transaction path, not Ethereum’s consensus rules.
History
The ERC-4337 proposal was created on September 29, 2021. Its specification describes the UserOperation, EntryPoint, smart-account validation, bundler behavior, and optional paymaster flow. Later revisions also describe how an EIP-7702 authorization can be supplied alongside an operation; that integration is optional and does not make the two standards identical.
Related Terms
See Also
- Does Ethereum TPS Include Layer 2 Transactions?
- Is Ethereum Staking Making the Network More Centralized?
- What Is MEV — And Why Every Ethereum Transaction Is a Game?
Sources
- ERC-4337: Account Abstraction Using Alt Mempool — the official specification for UserOperations, EntryPoint execution, smart accounts, bundlers, paymasters, and security limits.
- ERC-7769: JSON-RPC API for ERC-4337 — the standard RPC methods used to submit and inspect UserOperations with bundlers.
- ERC-7562: Account Abstraction Validation Scope Rules — the validation restrictions that bundlers enforce when checking account and paymaster code.