What is ERC-4337?
ERC-4337 is the Ethereum standard that delivers account abstraction without changing Ethereum’s core protocol. It introduces a separate, parallel transaction-mempool system in which “accounts” are smart contracts instead of plain key pairs. This lets wallets sponsor gas fees, pay gas in any token, batch multiple operations into one transaction, implement social recovery, and enforce custom security policies — all features impossible with a standard externally owned account (EOA).
The bottom line: ERC-4337 is the reason modern Web3 wallets can offer an experience closer to a fintech app (no seed-phrase panic, no need to hold ETH for gas, biometric login) while staying non-custodial. It is the technical backbone of “smart accounts” from providers like Coinbase, Safe, Biconomy, and ZeroDev. For the broader concept, see Account Abstraction.
How ERC-4337 Works / Technical Details
Why Not Just Change the Protocol?
Native Ethereum accounts (EOAs) are tied to a single private key: whoever holds the key controls the account, and only that key can pay gas. Upgrading EOAs at the protocol level requires a hard fork and years of consensus debate. ERC-4337’s genius is to achieve the same result without a protocol change by adding a new transaction layer on top.
The Four Core Components
- UserOperation (UserOp). A pseudo-transaction object describing what the user wants to do, signed by the smart account. It is not a real Ethereum transaction yet.
- Bundler. A network participant (see Bundler) that collects many UserOperations from the mempool, validates them, and packages them into a single real Ethereum transaction submitted to a block.
- EntryPoint. A singleton smart contract that executes the bundle, verifying each UserOperation’s signature and gas, and orchestrating calls between accounts, paymasters, and the target contracts.
- Paymaster. An optional smart contract that sponsors or substitutes gas payment, enabling gasless transactions or paying gas in ERC-20 tokens.
The End-to-End Flow
- The user signs a UserOperation (intent) with their smart account
- The UserOp goes to the alt mempool (a separate pool for UserOps)
- A bundler picks up UserOps, validates signatures, and bundles them
- The bundler submits one transaction to the EntryPoint
- The EntryPoint executes each UserOp: verifies the account, optionally uses a paymaster for gas, and calls the target contract
- The bundler is reimbursed; the paymaster settles gas
This architecture means users never need ETH in their wallet and never deal with raw transactions — they just sign intents.
Smart Account Features Enabled
- Gasless transactions — a paymaster covers gas
- Pay gas in any token — pay in USDC instead of ETH
- Transaction batching — approve + swap + deposit in one signature
- Session keys — grant a dApp limited, time-boxed permission to act on your behalf
- Social / multi-sig recovery — recover access without a seed phrase
- Custom validation — any signature scheme, passkeys, biometrics, multi-sig
Notable Examples and Adoption
Coinbase Smart Wallet
Coinbase’s smart wallet is built on ERC-4337 and paymasters, letting users onboard with no ETH and pay gas with the token they’re transacting, targeting mainstream users who would otherwise bounce at the gas requirement.
Safe (formerly Gnosis Safe)
Safe, the most widely used smart-contract wallet, adopted ERC-4337 modules to add paymaster-sponsored transactions and improved UX while retaining its battle-tested multi-sig security model.
Account Abstraction on L2s
Several L2s (notably Polygon with its native AA, and Optimism/Base via their stack) have gone further, implementing account abstraction at the protocol level. But ERC-4337 remains the cross-chain standard that works on Ethereum mainnet and every EVM chain without protocol changes.
Paymaster-Sponsored Onboarding
Many dApps now sponsor the first N transactions for new users via paymasters, removing the “I need to buy ETH first” friction that historically killed conversion.
How to Use and Understand ERC-4337
For Users
- You get a smoother experience — biometrics, no seed phrases, gasless onboarding — without giving up self-custody. Your account is still controlled by keys you hold (or recover socially).
- Understand the trust model. A sponsored paymaster can see your transactions; a bundler can censor (but you can switch bundlers). The underlying custody remains yours.
- Recovery matters. Set up social recovery or multi-sig so losing one device doesn’t lock you out.
For Developers
- Build smart accounts with ERC-4337-compatible SDKs (Biconomy, ZeroDev, Alchemy, Pimlico) rather than reimplementing the stack.
- Use paymasters to remove gas friction for onboarding, but budget for it — paymaster sponsorship is a real cost.
- Validate carefully. Bundlers must validate UserOps without on-chain state changes that could invalidate the bundle (the validation/execution separation rule), or the bundle can revert and the bundler loses gas.
- Account for the alt mempool’s distinct economics — UserOps are ordered and bundled differently than regular transactions.
Frequently Asked Questions
Q: Do I need ETH to use an ERC-4337 wallet? A: Not necessarily. A paymaster can sponsor your gas or let you pay in another token. That said, someone always pays the underlying gas in ETH — it’s just not always you.
Q: Is ERC-4337 more or less secure than a regular wallet? A: It depends on the implementation. Smart accounts can be more secure (multi-sig, social recovery, spend limits) but add smart-contract risk. Well-audited accounts like Safe are considered very secure.
Q: What’s the difference between ERC-4337 and EIP-3074/EIP-7702? A: ERC-4337 adds a separate transaction layer without protocol changes. EIP-3074 and EIP-7702 are protocol-level changes that let EOAs delegate to smart contracts. They’re complementary approaches; ERC-4337 shipped first and works today across all EVM chains.