IRSB
The accountability layer for intent-based transactions
Four systems that work together — on-chain contracts, a solver execution engine, an independent watchtower, and a policy-gated signing gateway — so every intent gets a receipt, every solver has skin in the game, and violations are caught automatically.
The Ecosystem
Four systems. One accountability layer.
No Proof or Consequences
Protocol
On-chain contracts for receipts, bonds, disputes, and escrow. 3 verified contracts, 308 tests.
No Execution Engine
Solver
Execute intents, produce evidence, submit receipts. Pluggable job types with CLI and HTTP interfaces.
No Independent Monitoring
Watchtower
Monitor receipts, detect violations, file disputes. Rule engine with configurable violation detection.
No Secure Signing
Agent Passkey
Policy-gated signing via Lit Protocol PKP. 2/3 threshold signatures across TEE nodes.
How It Works
The intent lifecycle from submission to accountability.
Submit Intent
User expresses what they want (ERC-7683 format)
Solver Executes
Bonded solver picks up and fills the intent
Receipt Posted
Cryptographic proof of execution goes on-chain
Challenge Window
1 hour for anyone to dispute with evidence
Finalize
No dispute = receipt finalizes, reputation updates
Deployed on Sepolia
3 contracts verified on Etherscan. 308 passing tests. Open source.
Where to Start
Understand the Protocol
Read the one-pager, see what changes before vs after, review the roadmap.
One-Pager →Explore the Architecture
Contracts, parameters, security model, deployed addresses, all 4 repos.
Architecture →Interested in integrating IRSB?
We are working with early partners to test integration patterns.