RIP-7755 primary sources — 2026-05-09

Classification takeaway

RIP-7755 is most useful as a proof-based fulfiller-compensation and destination-execution standard for cross-L2 calls, not as a bridge brand or generic “intent protocol.” Its core mechanism is that a user posts a request and locks compensation on the source chain, a fulfiller executes the destination-side call, and the fulfiller only gets paid after proving the destination inbox recorded fulfillment. The important comparison is therefore not just “is this cross-chain?” but “what exactly is being standardized?” In RIP-7755, the answer is provable execution-and-payment flow, not routing APIs or a shared order envelope.

Primary sources reviewed

1. RIP-7755 draft in the ethereum/RIPs repo — https://raw.githubusercontent.com/ethereum/RIPs/master/RIPS/rip-7755.md

   • Best canonical source for abstract, motivation, interface definitions, attribute design, and settlement model.
   • Confirms status is Draft, created 2024-08-11, and frames the proposal as a standard for cross-chain calls within the Ethereum rollup ecosystem.

2. GitHub view of the same proposal — https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7755.md

   • Useful as the human-readable canonical home of the proposal.
   • Helps preserve a stable corpus pointer even if raw fetch formats change later.

3. Ethereum Magicians discussion thread — https://ethereum-magicians.org/t/rip-7755-contract-standard-for-cross-l2-calls-facilitation/20776

   • Canonical public discussion venue referenced by the proposal.
   • In this pass, lightweight fetch only surfaced the thread title cleanly, so deeper discussion detail should be revisited later if reviewer debate becomes important.

4. Base proof-of-concept repository — https://github.com/base-org/RIP-7755-poc

   • Strong evidence that production-oriented rollup builders are testing the model in code.
   • Useful for tracking whether the standard’s abstract proof flow is implementable in a real builder environment.

5. Base proof-of-concept README — https://raw.githubusercontent.com/base-org/RIP-7755-poc/main/README.md

   • Helpful summary of how Base describes the proposal in practice.
   • Confirms the repository is explicitly framed as a proof-of-concept implementation of the RRC-7755 protocol.

Key takeaways from primary sources

• RIP-7755 is trying to restore directness to cross-chain execution. The motivation section explicitly contrasts the proposal with centralized relayers, non-Ethereum trust layers, and abstract intent systems that hide execution control behind solver architecture.
• The most important primitive is the source-side reward lock plus destination-side fulfillment receipt. This separates “who can execute” from “who is entitled to compensation,” with compensation contingent on later proof.
• The settlement logic matters more than the request event. Many systems emit an order or intent event; RIP-7755’s differentiator is the proof path from destination inbox storage back through rollup/L1 state assumptions.
• The attribute system is where much of the real market design lives. Nonce, delay, expiry, precheck, magic-spend, reward, and oracle attributes all shape whether a given request is attractive, safe, or even possible for fulfillers to execute.
• The standard is low-level enough to matter as a comparison class for cross-chain account abstraction. The optional ERC-4337 path shows the authors want the same provable-fulfillment model to work for smart-account execution, not just plain low-level calls.
• The spec does not eliminate implementation concentration. It openly depends on chain-specific proof-validation logic and on chains exposing the right state roots/oracle paths, which likely favors more sophisticated infra operators even if the standard remains permissionless.

Mechanism lens

• Best current classification: proof-based cross-L2 call standard / fulfiller-compensation rail / execution-verification primitive.
• Closest comparison classes in the current corpus:
  • ERC-7683 for order-expression and filler-network standardization.
  • Skip Go Fast and Across for solver-financed fast execution with later settlement.
  • Hyperlane, LayerZero, and Axelar as foils when message attestations or external verification committees replace native proof-oriented settlement.
• Reusable insight: RIP-7755 is a reminder that “cross-chain intents” can standardize very different layers — the request envelope, the settlement proof, the filler market, or the verification rail — and those layers should not be collapsed into one category.

Whitepaper / docs status

• No standalone whitepaper surfaced in this pass.
• The RIP draft itself is the real primary document.
• The Base proof-of-concept repo is worth tracking because it is a practical signal that the standard has implementer attention, not just standards-forum attention.