RIP-7560 primary sources — 2026-05-07

Project status in this pass

• No standalone RIP-7560 whitepaper or litepaper surfaced.
• The clearest source of truth was the raw RIP draft, backed by the ERC-4337 documentation summary.
• The sources consistently frame RIP-7560 as protocol-level account-abstraction infrastructure rather than as a wallet-only UX standard.

Primary-source snapshots

1) Raw RIP markdown

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7560.md
• Key excerpt/signals:
  • The abstract says RIP-7560 combines EIP-2938 and ERC-4337 into a comprehensive native account-abstraction proposal.
  • It proposes splitting transaction handling into validation, execution, and post-transaction logic.
  • It explicitly allows contract B to pay gas for a transaction executed from account contract A.
• Why it mattered:
  • This is the clearest evidence that RIP-7560 belongs in the corpus as protocol-level validation and fee-routing infrastructure.

2) Raw RIP markdown / motivation and tradeoff framing

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7560.md
• Key excerpt/signals:
  • The motivation says ERC-4337 carries roughly extra gas overhead for a basic UserOperation relative to a basic transaction.
  • It also highlights reliance on a smaller set of participating nodes, non-standard RPC methods, and weaker alignment with in-protocol censorship-resistance techniques.
  • The text treats backward compatibility with the ERC-4337 ecosystem as a design goal, not something to discard.
• Why it mattered:
  • These claims show that RIP-7560 is trying to relocate account-abstraction complexity from higher-layer infrastructure toward canonical protocol rules while keeping existing smart-account mental models legible.

3) Raw RIP markdown / transaction structure and phases

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7560.md
• Key excerpt/signals:
  • The specification introduces a new EIP-2718 transaction type with fields for sender, deployer, paymaster, execution data, nonce key and sequence, gas limits, builder fee, and EIP-7702-compatible authorizations.
  • It defines multiple top-level frames: sender deployment, sender validation, paymaster validation, execution, and paymaster post-operation.
  • The sender contract is expected to expose validateTransaction(...) for validation.
• Why it mattered:
  • This is the strongest signal that RIP-7560 is not just a different envelope for ERC-4337-style payloads; it turns AA flow structure into a native execution-layer primitive.

4) ERC-4337 documentation summary

• URL: https://docs.erc4337.io/core-standards/rip-7560.html
• Key excerpt/signals:
  • The docs describe RIP-7560 as native AA via a new transaction type in the Ethereum protocol.
  • They contrast canonical mempool inclusion and lower gas costs against ERC-4337’s custom mempool and higher overhead.
  • They frame RIP-7560 as primarily intended for rollups, while EIP-7701 is positioned as the L1-native sibling.
• Why it mattered:
  • This is the clearest implementation-facing explanation of why RIP-7560 changes where account-abstraction authority and infrastructure burdens live.

5) Public discussion thread

• URL: https://ethereum-magicians.org/t/rip-7560-native-account-abstraction/16664
• Key excerpt/signals:
  • Only the thread title surfaced cleanly in this pass, but it confirms the draft’s public standards-discussion venue.
• Why it mattered:
  • Even without good body extraction, the thread anchors RIP-7560 in an active standards process rather than a dead document.

Working conclusion

RIP-7560 is best cataloged as native account-abstraction transaction infrastructure: it formalizes validation, fee sponsorship, and execution sequencing inside the protocol path instead of outsourcing them to the current ERC-4337 EntryPoint-and-bundler layer.