Skip to content

26. EIP-7702

A short explainer (by Patrick Collins) on EIP-7702, which lets a regular EOA temporarily behave like a smart account. It’s the natural companion to the ERC-4337 lesson: where 4337 gives you smart accounts as a separate thing, 7702 upgrades the account you already have. Conceptual context only — no implementation required.

  • The gap it fills — ERC-4337 smart accounts are powerful, but everyone already has an EOA, and migrating is friction. EIP-7702 lets an existing EOA point to smart-contract code so it can act like a smart account when needed.
  • Delegating to code — with 7702, an EOA can, for a transaction, adopt a contract’s logic — gaining features like batching, gas sponsorship, and custom permissions without abandoning its address or history.
  • Why it matters — it brings account-abstraction benefits to the hundreds of millions of existing EOAs, rather than requiring users to create and fund a brand-new smart account. It’s a major UX step for wallets.
  • Part of a protocol upgrade — unlike ERC-4337 (pure contract layer), EIP-7702 is an Ethereum protocol change, included in the Pectra upgrade. That’s why it can grant new powers to plain EOAs.
  • Relationship to 4337 — think of them as complementary: 4337 defines the smart-account ecosystem (bundlers, paymasters, EntryPoint); 7702 lets ordinary accounts plug into that world.
  • Conflating 7702 with 4337. Both advance account abstraction, but 4337 is a contract-layer standard for new smart accounts, while 7702 is a protocol change that upgrades existing EOAs.
  • Assuming you must implement this. In this course it’s context — know what it enables and why it’s a UX milestone.
  • Thinking the EOA becomes a contract permanently. It’s about an EOA being able to act with contract logic, not ceasing to be an EOA.
  • What does EIP-7702 let an existing EOA do?
  • Why is upgrading existing accounts (rather than creating new smart accounts) a big UX deal?
  • How do EIP-7702 and ERC-4337 differ in terms of where they live — protocol vs. contract layer?

Module 4: L2, Indexing, Security & Web3 Identity.