ERC-4337 vs EIP-7702 Ethereum/EVM standard comparison
ERC-4337 and EIP-7702 are complementary account-abstraction paths: 4337 defines the UserOperation, EntryPoint, bundler, and paymaster architecture; 7702 lets existing EOAs delegate execution to contract code.
ERC-4337 and EIP-7702 are complementary paths to account abstraction. ERC-4337 (mainnet 2023) defines the UserOperation, EntryPoint singleton, bundler, and paymaster architecture — smart accounts get first-class transactor behavior via a parallel mempool. EIP-7702 (Pectra, 2025) lets existing EOAs delegate execution to smart account code via a signed authorization tuple, unlocking 4337-style flows without migrating addresses. Together: EOAs can behave like smart accounts (7702) inside the AA infrastructure (4337). The trade-off is that 7702's ECDSA key remains authoritative even after delegation.
Spec diff.
| ERC-4337 | EIP-7702 | |
|---|---|---|
| primary object | UserOperation from a smart account | set-code transaction from an EOA |
| infrastructure | bundler + EntryPoint + optional paymaster | normal transaction path plus delegated code |
| existing address migration | not by itself; new smart account address is common | yes; existing EOA keeps its address |
| gas sponsorship | paymaster via EntryPoint | usually paired with 4337/paymaster infrastructure |
| signature / validation | validateUserOp on account | EOA authorizes delegation; delegated code handles execution |
| residual EOA key | not present for native contract accounts | present unless future revocation patterns are added |
The clean distinction
ERC-4337 is an account-abstraction architecture. It defines the UserOperation object, EntryPoint validation flow, bundler role, paymaster sponsorship path, and account-side validation hook.
EIP-7702 is an EOA upgrade primitive. It lets an externally owned account temporarily behave as if it had contract code, which gives existing addresses a path into smart-wallet behavior without redeployment.
Why they are complementary
7702 solves the migration problem that 4337 alone could not solve: users already have EOAs with assets, ENS records, transaction history, reputation, and airdrop eligibility. 4337 solves the ecosystem problem around bundlers, paymasters, and wallet infrastructure. In production, wallets can use 7702 to upgrade the address and 4337 infrastructure to route sponsored or bundled operations.
The remaining gap
Neither standard is a complete permission vocabulary. ERC-4337 leaves validation policy to each account implementation. EIP-7702 delegates execution to code, but the original EOA key remains a serious lifecycle question. The LUKSO comparison is useful because LSP0 and LSP6 start from the account and permission layer instead of patching it around an EOA.