IRSB Protocol — Executive Summary

The Problem

ERC-7683 standardizes cross-chain intent formats, but doesn't address what happens after a solver accepts an intent. There is no standardized proof of execution, no economic consequence for bad fills, and no portable reputation for solvers. Users delegate execution and hope for the best.

What IRSB Does

IRSB (Intent Receipts & Solver Bonds) adds four primitives to intent execution:

• 1.Receipts — On-chain cryptographic proof that a solver executed an intent. V1 (single signature) and V2 (dual attestation with EIP-712).
• 2.Bonds — Solvers stake collateral (min 0.1 ETH). Slashable for violations.
• 3.Disputes — 1 hour challenge window. Deterministic auto-slash for timeouts. Optimistic resolution with counter-bonds for complex cases.
• 4.Reputation — IntentScore: on-chain composite metric derived from execution history. Portable via ERC-8004.

Key Parameters

Slashing Distribution

When a solver's bond is slashed: 80% to the affected user, 15% to the challenger, 5% to the protocol treasury. After 3 jailings, the solver is permanently banned.

Standards Compatibility

• ERC-7683 — Receipts reference intentHash from cross-chain orders
• ERC-8004 — IRSB is a Validation Provider, publishing signals to the agent reputation registry
• x402 — irsb-x402 package bridges HTTP 402 payments to on-chain receipts

Current State

• Deployed on Sepolia testnet — 3 core contracts verified on Etherscan
• 308 passing tests including fuzz tests
• 4 open-source repositories (MIT license)
• TypeScript SDK + CLI tools (npm: irsb, irsb-x402)
• Cloud KMS + EIP-7702 delegation live — WalletDelegate with 5 caveat enforcers. Agent-passkey deprecated.
• ERC-8004 agent registered (ID: 967) — signal publishing not yet enabled
• Solver v0.1.0 (chain-connected, Cloud KMS signing, receipt submission). Watchtower v0.3.0 (chain-connected, real on-chain data, dispute filing)

Deployed Contracts (Sepolia)

Outlook

Next steps: security audit, mainnet deployment, and first protocol integration. The goal is to establish IRSB as an open standard — an ERC/EIP proposal for intent accountability that any protocol can adopt. Multi-chain deployment (Arbitrum, Base, Polygon) follows mainnet.