Category: native account-abstraction transaction standard / validation-and-execution control plane / rollup protocol infrastructure
Summary: RIP-7560 is best cataloged as protocol-level account-abstraction infrastructure rather than as a wallet feature or a minor optimization to ERC-4337. Its core move is to introduce a native AA transaction type whose sender is a smart-contract account, then split transaction handling into explicit validation and execution phases with optional deployer and paymaster frames. The mechanism significance is that RIP-7560 tries to pull smart-account validation, fee sponsorship, and execution ordering back into the canonical protocol path, reducing reliance on the higher-layer bundler and EntryPoint stack while preserving much of ERC-4337’s mental model.
What it does:
Proposes a new EIP-2718 AA transaction type for smart-contract accounts
Splits transaction flow into distinct validation and execution phases, with optional deployer and paymaster frames plus paymaster post-operation logic
Lets a smart-contract account validate itself through a validateTransaction(...) method instead of depending on an EOA signature as the base transaction primitive
Supports direct gas charging from the sender or an optional paymaster and adds an explicit builderFee field for block-builder incentives
Keeps compatibility hooks with adjacent native-AA work such as EIP-7702 authorizations and RIP-7712 keyed nonces
Aims to move account abstraction from a custom mempool and bundler path toward canonical transaction inclusion, especially on rollups
Key claims:
The draft abstract says RIP-7560 combines EIP-2938 and ERC-4337 into a comprehensive native account-abstraction proposal, which is the clearest signal that it belongs in the corpus as protocol-level execution infrastructure rather than wallet UX
The motivation says ERC-4337’s higher-layer approach carries extra gas overhead, weaker alignment with in-protocol censorship-resistance techniques, reliance on a smaller set of participating nodes and custom RPC methods, and awkward tx.origin behavior, which shows the proposal is trying to relocate those costs from infrastructure to protocol rules
The specification introduces a new AA transaction type whose payload includes sender, deployer, paymaster, execution data, nonce key and sequence, gas fields, and an EIP-7702-compatible authorization list, making the transaction itself the account-abstraction control surface
The draft explicitly separates validation from execution and describes multiple top-level frames for sender deployment, sender validation, paymaster validation, execution, and paymaster post-operation, which matters because it turns what ERC-4337 handled through EntryPoint orchestration into first-class protocol flow
The gas section says maximum gas is pre-charged directly from the sender or paymaster balance, showing that RIP-7560 preserves fee sponsorship but removes the outer meta-transaction wrapper that ERC-4337 depends on today
The ERC-4337 docs summarize RIP-7560 as native AA through a new transaction type in the Ethereum protocol, emphasize lower gas and canonical mempool inclusion, and frame it as primarily intended for rollups while EIP-7701 targets Ethereum L1
The same docs note that tooling and RPC layers must be updated for encoding, nonce handling, gas estimation, and validation behavior, which is a strong clue that RIP-7560 is not merely a wallet standard but a broad infra migration surface
The draft’s relationship to RIP-7712 is also analytically important: keyed nonce lanes are optional extensions on top of RIP-7560, so transaction sequencing and concurrency are being broken out into a distinct native-AA control layer rather than buried inside wallet implementation details
Whitepaper: No standalone RIP-7560 whitepaper or litepaper surfaced in this pass. The clearest source of truth was the raw RIP draft, backed by the ERC-4337 documentation summary and the public Magicians discussion thread; see ../../whitepapers/rip-7560-primary-sources-2026-05-07.md.