0xef0100 || contractAddress in your code slot, redirecting execution to that contract whenever your EOA is invoked. It unlocks powerful capabilities like batching (Bundling), gas sponsorship (Relaying), multi-sig, passkeys, and more, all while keeping your familiar address and key.
Why It Matters
- Upgrades without migration: Your users keep their existing EOA. No address change or fund transfers needed.
- Smart account features: batch transactions, sponsored gas, custom auth, and passkey support become native.
- Designed for coexistence: with ERC-4337’s abstract architecture; they complement each other perfectly.
EIP-4337 vs EIP-7702 at a Glance
| Feature | EIP-4337 | EIP-7702 |
|---|---|---|
| Smart account model | External smart wallet using EntryPoint | EOA delegates to smart contract via designator |
| Migration required | Yes, EOAs must become SCAs | No, EOAs remain same address |
| Infrastructure | Off-chain bundlers/EntryPoint/Paymaster | On-chain native execution once supported by wallets |
| Best use case | Rich palettes today (multi-sig, custom flows) | Lean, backward-compatible UX enhancement, low friction |
Security & UX Considerations
- Trust required: Delegation gives execution power over your EOA. Only delegate to vetted, trusted contracts.
- Control remains: Your private key still governs the account—preserving flexibility but requiring strong custody.
- Wallet adoption is key: Until wallets support 7702, none of this matters in production environments.