Cowrie Research

rip-7755

4 min read

RIP-7755

  • Name: RIP-7755 (Cross-L2-Call)
  • URL: https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7755.md
  • Category: cross-L2 call standard / proof-based fulfiller-compensation rail / destination-call verification standard
  • Summary: RIP-7755 is best understood as a low-level standard for paying offchain fulfillers to execute a destination-chain call only when that execution can later be proven onchain. Its reusable mechanism is not “bridging” in the generic sense, but a two-sided Outbox/Inbox request-and-receipt system plus a settlement layer that verifies destination execution from source-chain state assumptions. The useful comparison is against ERC-7683 and solver-based bridge systems: RIP-7755 is trying to standardize provable destination execution and reward release, not the outer intent envelope, routing API, or a particular filler network.
  • What it does:
    • Defines an origin-chain Outbox that accepts a cross-chain call request, locks fulfiller compensation, and emits a discovery event
    • Defines a destination-chain Inbox that executes the requested low-level calls and stores an immutable fulfillment receipt if all requested calls succeed
    • Lets offchain fulfillers relay and execute the destination-side call, then later claim compensation on the source chain by submitting a proof of fulfillment
    • Specifies a chain-specific storage-proof-based settlement flow that verifies the destination chain’s stored FulfillmentInfo before releasing rewards
    • Uses ERC-7786-style attributes to parameterize nonce, delay/expiry, precheck contracts, paymaster funding requests, rewards, inbox routing, requester identity, and L2 oracle details
    • Supports both standard low-level call arrays and ERC-4337-style cross-chain UserOp flows where the destination receiver can be an EntryPoint
  • Key claims:
    • The draft says the goal is to minimize trust assumptions for cross-chain calls by relying on shared state relationships between Ethereum and its rollups rather than on a privileged relayer set or external bridge trust model
    • The proposal’s strongest conceptual move is separating three roles — request posting, destination execution, and later proof-based compensation — so fulfillers can compete on execution without being paid unless execution is provable onchain
    • The standard is intentionally lower-level than most intent systems. The motivation section explicitly criticizes abstracted intent architectures that restrict direct control over execution, which makes RIP-7755 a useful comparison class whenever a protocol claims to be “intent-based” but quietly hides execution control and trust assumptions inside its solver stack
    • The storage-proof settlement sequence is the analytically important part: reward release depends on proving the destination inbox receipt through L2/L1 state roots and contract storage proofs, not merely on a message attestation from some third-party bridge network
    • The attribute system matters because it exposes where practical market design lives even after standardization: expiry policy, finality delay, prechecks, magic-spend funding, reward asset/amount, and oracle configuration all shape which requests fulfillers will actually price and execute
    • The optional ERC-4337 path is worth tracking because it extends the standard from plain contract calls into permissioned smart-account execution, with the 7755 inbox/paymaster stack preserving receipt creation and gas sponsorship constraints
    • This remains a Draft, and the spec itself admits proof validation is chain-specific. So even if the abstract mechanism standardizes, implementation complexity and chain-specific oracle/state-root assumptions may still concentrate power in a smaller set of sophisticated fulfillers and production-grade proof/verification stacks
    • The Base proof-of-concept repository is useful evidence that RIP-7755 is not only a forum idea; major rollup-aligned builders are actively testing the model in code
  • Whitepaper: No standalone whitepaper surfaced in this pass. The canonical materials were the RIP draft itself, the Magicians discussion venue, and the Base proof-of-concept repository; see ../../whitepapers/rip-7755-primary-sources-2026-05-09.md.
  • Sources:

Internal linkages

  • Higher-level intent-shell that solves a different layer of the problem: erc-7683

  • Strongest production comparison for fast transfer versus proof-based reward release: across

  • Smart-account execution crossover where cross-chain requests can target EntryPoint-style flows: erc-4337

  • Reusable lens: once expiry policy, proof configuration, oracle assumptions, and fulfiller sophistication start to matter, the visible cross-chain call label stops telling you much.

  • Last reviewed: 2026-05-09 UTC

Graph View

Backlinks