ARTICLESX
May 8, 2025#AA· 12 min

Pectra — EIP-7702 turns your EOA into a smart account

Your plain wallet can now temporarily run contract code in a transaction: batching, gas sponsorship, session keys — no migration.

For a decade there were two kinds of accounts: EOAs (your wallet, controlled by a private key, can't run code) and contracts (can run code, can't initiate transactions). Account abstraction tried to merge them. ERC-4337 did it *around* the protocol. EIP-7702, shipped in Pectra, does it *in* the protocol — for the addresses people already have.

What it actually does

7702 adds a new transaction type that lets an EOA attach contract code to itself for the duration of a transaction (or persistently, by pointing at an implementation). Your 0x-wallet temporarily *becomes* a smart account, executes contract logic, then is a normal EOA again.

  EOA (0xAlice)
     │  signs a 7702 tx: "run code at 0xImpl as me"
     ↓
  ┌─────────────────────────────┐
  │ 0xAlice, now executing 0xImpl│
  │  • batch: approve + swap     │  ← one signature, many actions
  │  • paymaster pays the gas    │  ← gasless for the user
  │  • session key, limits, ...  │
  └─────────────────────────────┘
     │ tx ends → 0xAlice is a plain EOA again
An EOA borrowing contract code for one tx

Why it matters

  • Batching — approve-then-swap in a single signed action, no more two-popup dance.
  • Gas sponsorship — apps can pay gas for users; onboard someone with zero ETH.
  • Session keys & limits — scoped permissions for a game or a dapp, revocable.
  • No new address — your funds, history and ENS stay put; you upgrade in place.

The sharp edges

Pointing your own account at contract code is powerful and therefore dangerous. Sign the wrong 7702 authorization and you've delegated your EOA to a malicious implementation that can sweep it. Wallets have to treat the delegation target like a contract approval — show it, scope it, let you revoke it. The footgun moved; it didn't disappear.

  • Phishing surface — a malicious delegate can act as you; the authorization signature is the new thing to guard.
  • Revocation — you can re-point or clear the delegation, but wallets must make that easy and visible.
  • Per-chain — a delegation is set per chain, so multi-chain UX has to manage it everywhere.

Pectra carried more than 7702: EIP-7251 raised the effective validator balance cap from 32 to 2048 ETH (run the same stake with far fewer validators), alongside other staking and UX changes. But 7702 is the one ordinary users will actually *feel*.

It doesn't replace 4337 — the two compose. But for the average wallet, 7702 is the moment account abstraction stopped being a separate product and became a property of *your* account.