RIP-7712 primary sources — 2026-05-07

Project status in this pass

• No standalone RIP-7712 whitepaper or litepaper surfaced.
• The clearest source of truth was the raw RIP markdown, backed by the ERC-4337 documentation summary page.
• The sources consistently frame RIP-7712 as nonce and sequencing infrastructure for native account abstraction, not as a wallet-UX standard.

Primary-source snapshots

1) Raw RIP markdown

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7712.md
• Key excerpt/signals:
  • The abstract says RIP-7712 modifies RIP-7560 transactions by replacing the existing nonce-based sequencing mechanism with an on-chain pre-deployed contract.
  • The motivation says accounts need to express intentions like allowing transactions to mine in any order or keeping separate sequential flows isolated from each other.
  • The specification defines the nonce as uint256 nonceKey || uint256 nonceSequence and stores nonce state per account and per key.
• Why it mattered:
  • This is the clearest evidence that RIP-7712 belongs in the corpus as replay-protection and sequencing infrastructure.

2) Raw RIP markdown / NonceManager details

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7712.md
• Key excerpt/signals:
  • The RIP introduces a NonceManager predeploy that validates and increments keyed nonces during a dedicated validation frame.
  • It also exposes a query path for reading the current nonceSequence for a given nonceKey.
  • The pseudocode makes the keyed nonce mapping and increment rules explicit.
• Why it mattered:
  • These details show that RIP-7712 is not just a notation change; it adds a shared execution primitive that other account-abstraction components must coordinate around.

3) Raw RIP markdown / legacy nonce and EIP-7702 caveat

• URL: https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7712.md
• Key excerpt/signals:
  • nonceKey == 0 keeps the legacy nonce path.
  • The legacy nonce still matters for EOAs, deployment flows, and EIP-7702 authorizations.
  • The backwards-compatibility section warns that sending a RIP-7712 transaction may not invalidate a previously signed EIP-7702 authorization tuple.
• Why it mattered:
  • This is the strongest signal that RIP-7712 changes the practical interaction between replay protection and delegation or revocation semantics across mixed account models.

4) ERC-4337 documentation summary

• URL: https://docs.erc4337.io/core-standards/rip-7712.html
• Key excerpt/signals:
  • The docs summarize RIP-7712 as multi-dimensional nonces for smart-contract accounts in RIP-7560 transactions.
  • They explicitly connect separate nonce lanes to multisig flows, automation, modular-account plugins, and delegated session keys.
  • The relation table links RIP-7712 to RIP-7560, ERC-4337, EIP-7702, and ERC-6900 / ERC-7579.
• Why it mattered:
  • This is the clearest implementation-facing explanation of why keyed nonces matter for the modular smart-account stack and for future wallet-control surfaces.

5) Discussion thread

• URL: https://ethereum-magicians.org/t/rip-7712-multi-dimensional-256-bit-nonce-for-rip-7560-account-abstraction-transactions/20094
• 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 useful body extraction, the thread anchors the RIP in the live account-abstraction standards process.

Working conclusion

RIP-7712 is best cataloged as keyed nonce and sequencing infrastructure for native account abstraction. The decisive evidence in this pass was the two-dimensional nonce design, the NonceManager predeploy, the dedicated validation frame, and the compatibility caveats showing that nonce handling is becoming an explicit control surface for modular smart accounts rather than a hidden wallet implementation detail.