EIP-4337 and EIP-7702 are the two production paths for account abstraction on Ethereum. They share most of the same features — batched calls, gas sponsorship, session keys, recovery flows — but reach them through different architectures. EIP-4337 deploys a separate smart-account contract that holds funds and processes UserOperations through a dedicated mempool. EIP-7702 lets an existing externally owned account temporarily delegate execution to a contract without redeploying.
The two are not mutually exclusive. Most production wallet stacks (Safe, Biconomy, ZeroDev, Alchemy) support both, and the choice depends on the user's situation. Users wanting a fresh smart-account address typically pick ERC-4337. Users wanting to keep their existing address while gaining smart-wallet features typically pick EIP-7702.
What Is EIP-4337?
ERC-4337 is an application-level account abstraction standard finalized in March 2023 and authored by Vitalik Buterin, Yoav Weiss, Dror Tirosh, Shahaf Nacson, and Alex Forshtat. It avoids consensus changes by introducing a parallel transaction-handling system: smart-account contracts, UserOperations, bundlers, and an EntryPoint contract.
The architecture has four main components defined by the ERC-4337 specification:
Smart account — a contract that holds the user's funds and exposes a
validateUserOpfunction. The user's "account" is this contract address, not their EOA.UserOperation — a struct that wraps the intent (what to call, with what data, paid for by whom). Signed by the user, posted to a separate mempool.
Bundler — an off-chain agent that picks UserOperations from the mempool and posts them as standard transactions to the EntryPoint.
EntryPoint — a singleton contract (deployed at 0x0000000071727De22E5E9d8BAf0edAc6f37da032) that validates UserOperations and dispatches calls to the appropriate smart account.
Because the design avoids touching consensus, ERC-4337 deployed without a hard fork. It has been live on Ethereum mainnet, every EVM L2, and most EVM-compatible chains for over two years.
What Is EIP-7702?
EIP-7702 is a Core Standards Track EIP that activated with the Pectra hard fork on May 7, 2025. It introduces Type 4 transactions, which carry a list of authorizations. Each authorization is a signature from an EOA pointing to a contract address. When the transaction executes, the named EOA temporarily inherits the contract's bytecode.
The full EIP-7702 specification describes the transaction format and the rules for code injection. Unlike ERC-4337, EIP-7702 does require a hard fork because it changes how the EVM interprets account state. The change is bounded: outside of transactions, the EOA still behaves like a normal account, and the user can revoke the delegation by signing a new authorization to the zero address.
The historical context matters. EIP-7702 replaced ERC-3074, an earlier proposal that gave one trusted invoker contract too much power. EIP-7702 distributes that trust by letting users sign delegations to any contract.
How Are They Different?
The architectural split produces concrete differences in how each is deployed and operated. The clearest comparison is on six dimensions:
Dimension | ERC-4337 | EIP-7702 |
Activated | March 2023 (no fork) | May 7, 2025 (Pectra hard fork) |
Account address | New smart-account contract | Existing EOA |
User key | Any signature scheme (ECDSA, BLS, passkey) | Same ECDSA key as the EOA |
Mempool | Separate UserOp mempool | Standard mempool |
Setup cost | Deploy contract account (~$5-50 in gas) | One-time signature, no deployment |
Fund migration | Required (move from EOA to contract) | Not required (EOA keeps funds) |
The deployment-cost gap matters most for new users with small balances. A $20 portfolio cannot afford a $30 smart-account deployment but can sign an EIP-7702 authorization for free.
What Features Do Both Support?
Both standards support the core account-abstraction feature set:
Batched transactions — execute multiple actions (approve, swap, deposit) in one signature.
Gas sponsorship via paymaster — a third party pays gas; the user holds no ETH.
Session keys — temporary scoped keys for limited operations (e.g., "trade up to $100 within one hour").
Custom signature schemes — ERC-4337 supports any signature out of the box; EIP-7702 supports them via the delegated contract.
Social recovery — guardian-based key rotation if the user loses their primary key.
Spending limits — onchain enforcement of daily or per-transaction caps.
The feature parity is intentional. EIP-7702's design goal was to bring ERC-4337 features to existing EOAs without forcing migration. Production wallet stacks like ZeroDev and Safe's smart-account documentation implement the same modular architecture under both standards.
When to Pick Each
The decision usually comes down to whether the user has an existing address worth preserving. Three patterns dominate:
New users — prefer ERC-4337. A fresh smart-account contract gives the cleanest UX. The user never has an EOA to migrate from. Counterfactual deployment (the contract address is computed before deployment) lets users receive funds at their address before paying any gas.
Existing users with established addresses — prefer EIP-7702. Address reputation matters for ENS, social connections, NFT collections, and onchain identity. EIP-7702 keeps the address while adding smart-wallet features.
Mixed flows — combine both. Many production wallets use ERC-4337 for new accounts and EIP-7702 for existing EOAs, with the same backend smart-account logic in both cases. The wallet UX abstracts the difference.
Security Considerations
Both standards expand the attack surface relative to vanilla EOAs, in different ways:
ERC-4337 risks — the smart-account contract is the target of all interactions. A bug in the validation logic can lock funds or allow unauthorized withdrawals. Audits of well-known implementations (Safe, Biconomy, Kernel) have found and fixed multiple critical issues. The eth-infinitism reference repository is the most-vetted starting point.
EIP-7702 risks — phishing-via-delegation is the canonical concern. A user tricked into signing an authorization to a malicious contract effectively hands over their EOA. Wallet UIs need to surface delegated code clearly and offer easy revocation. Storage collisions between successive delegations are a secondary concern.
Shared concerns — gas-sponsorship paymasters can be DoS-ed or drained if poorly designed. Session keys with overly broad scope (e.g., unlimited approvals) reintroduce risks the original token approval model created.
Security teams now treat account abstraction as its own audit category. OpenZeppelin's account-abstraction series and Spearbit's published portfolio include detailed reviews of both standards.
Adoption Data
By mid-2025, ERC-4337 had processed over 50 million UserOperations cumulatively across mainnet and L2s, with daily volume oscillating between 200,000 and 1 million UserOps depending on chain activity. The BundleBear analytics dashboard tracks per-bundler and per-chain UserOp counts in real time.
EIP-7702 adoption has tracked Pectra activation. In the first 90 days after May 7, 2025, Type 4 transactions on Ethereum mainnet ramped from a handful of test transactions to tens of thousands per day, with the majority being gas-sponsored onboarding flows from MetaMask and Coinbase Wallet rollouts. Layer 2 adoption followed at varying speeds, with Arbitrum and Optimism integrating EIP-7702 within the first two months.
The two standards are now compounding rather than substituting. ERC-4337 supplies the smart-account contracts; EIP-7702 supplies the entry path for users with existing addresses. Wallet vendors increasingly offer a single UX that hides the underlying choice.
How These Standards Affect Stablecoin Movement
Both ERC-4337 and EIP-7702 enable patterns that matter for stablecoin payments. Gas sponsorship lets a recipient pay network fees instead of the sender, which is the foundation of "gasless" stablecoin transfers in payment apps. Batched transactions let a swap and a transfer settle in one user signature, important for cross-chain flows where multiple actions need to coordinate.
For developers integrating stablecoin transfers, the standards expand the pool of usable wallets. Onboarding a user with $50 of USDC and no ETH used to require either custodial onboarding or a sponsor's manual relayer. Now an EIP-7702 authorization plus an ERC-4337 paymaster covers the same flow with no custodian. Eco's intent-based routing accepts authorization signatures from both schemes, allowing B2B payout APIs and swap aggregators to onboard users without forcing wallet migrations.
FAQ
Is EIP-7702 replacing ERC-4337?
No. The two are complementary. ERC-4337 supplies the smart-account contract architecture; EIP-7702 supplies a way for existing EOAs to opt into that architecture. Most production stacks support both. The choice depends on whether the user wants a fresh address or to keep their existing one.
Can I use ERC-4337 features without deploying a new account?
With EIP-7702, yes. An EOA can sign an authorization pointing to a smart-account contract and gain the same batching, sponsorship, and session-key features without redeploying. Before Pectra (May 2025), this required either deploying a smart account or relying on offchain relayers.
Which option costs more in gas?
Setup costs differ. ERC-4337 requires deploying the smart-account contract, which costs $5-$50 depending on chain and bytecode size. EIP-7702 only requires a one-time signature for the authorization, with no deployment. Per-transaction overhead is similar; both add modest validation costs above standard transactions.
Can a contract use both EIP-4337 and EIP-7702?
The same wallet logic can serve both. Production wallets like Safe and Biconomy ship a single smart-account implementation that responds to both UserOperations (for ERC-4337 path) and direct calls from delegated EOAs (for EIP-7702 path). The unified codebase reduces audit scope and improves consistency.
Does EIP-7702 work on every L2?
It works on L2s that have integrated the Pectra changes into their fork schedule. Major rollups — Arbitrum, Optimism, Base, Linea — have either shipped support or have it on their published roadmap. Smaller chains follow at varying speeds. ERC-4337, in contrast, has been deployed on every EVM chain since 2023 because it requires no fork.