Cowrie Research

eip-7702-primary-sources-2026-05-07

3 min read

EIP-7702 primary sources — 2026-05-07

Project status in this pass

  • No standalone EIP-7702 whitepaper or litepaper surfaced.
  • The clearest current source of truth was the final EIP itself, supplemented by Ethereum.org’s official Pectra 7702 implementation guidelines.
  • The sources consistently frame EIP-7702 as a base-layer delegation primitive for EOAs that is meant to plug into the broader ERC-4337 / smart-account ecosystem rather than replace it.

Primary-source snapshots

1) Canonical EIP page

  • URL: https://eips.ethereum.org/EIPS/eip-7702
  • Key excerpt/signals:
    • The abstract says EIP-7702 adds a new EIP-2718 transaction type that allows EOAs to set code in their account.
    • It defines an authorization list of tuples formatted as [chain_id, address, nonce, y_parity, r, s].
    • It says a delegation indicator 0xef0100 || address is written to the authorizing account’s code.
  • Why it mattered:
    • This is the clearest evidence that EIP-7702 belongs in the corpus as a protocol-level delegation primitive, not just as wallet UX marketing.

2) Raw EIP text / motivation and design philosophy

  • URL: https://raw.githubusercontent.com/ethereum/EIPs/master/EIPS/eip-7702.md
  • Key excerpt/signals:
    • The motivation names batching, sponsorship, and privilege de-escalation as the three target feature families.
    • The rationale says persistent delegation was chosen to avoid splitting UX progress between smart-contract wallets and short-lived EOA scripts.
    • The EIP says applications must not expect to ask users to sign authorizations directly and that wallets should not provide such an interface.
  • Why it mattered:
    • These passages show where power is expected to concentrate: wallet-approved delegation templates and smart-account tooling above the base primitive.

3) Raw EIP text / state-transition specifics

  • URL: https://raw.githubusercontent.com/ethereum/EIPs/master/EIPS/eip-7702.md
  • Key excerpt/signals:
    • The spec defines transaction type 0x04 and charges PER_EMPTY_ACCOUNT_COST * authorization list length.
    • Delegation tuples are processed before execution, and the authority nonce is incremented when a tuple is valid.
    • Processed delegation indicators are not rolled back even if later execution reverts.
    • Delegation can be cleared by pointing at the null address.
  • Why it mattered:
    • This is the strongest evidence that 7702 is a real state-transition and authority primitive with unusual failure semantics, not merely a higher-layer wallet convention.

4) Raw EIP text / compatibility and broken assumptions

  • URL: https://raw.githubusercontent.com/ethereum/EIPs/master/EIPS/eip-7702.md
  • Key excerpt/signals:
    • The rationale says EOAs can point directly to existing ERC-4337 wallet code.
    • It also says allowing tx.origin to set code breaks the assumption that msg.sender == tx.origin only occurs in the topmost execution frame.
    • The text explicitly discusses how this affects flash-loan-style guards and reentrancy assumptions.
  • Why it mattered:
    • This is the most important mechanism-level consequence for the corpus: 7702 shifts legacy EOA semantics toward smart-account semantics and weakens older contract heuristics built around EOAs.

5) Ethereum.org Pectra 7702 guidelines

  • URL: https://ethereum.org/roadmap/pectra/7702/
  • Key excerpt/signals:
    • The guidelines say dapps should integrate through standardized wallet interfaces like ERC-5792 and ERC-6900 rather than requesting 7702 authorizations directly.
    • They recommend permissionless, censorship-resistant relaying and specifically point builders toward ERC-4337 bundlers and EntryPoint-compatible flows.
    • They warn about init frontrunning, storage collisions, phishing, and arbitrary-delegation exposure.
    • They list known audited implementations and recommend hardware wallets whitelist trusted delegation contracts.
  • Why it mattered:
    • This source makes the governance surface concrete: 7702 is nominally permissionless, but real-world adoption is likely to run through wallet-curated allowlists, audited templates, and standardized wallet interfaces.

Working conclusion

EIP-7702 is best cataloged as Ethereum delegation-semantics infrastructure: it gives EOAs a persistent pointer into smart-account logic while shifting practical power upward to wallet-approved implementations, bundler/paymaster stacks, and higher-level interfaces like ERC-5792 and ERC-6900.

Graph View