Before vs After IRSB
What changes when you add receipts, bonds, and disputes to intent execution.
This compares the current intent ecosystem with the IRSB design. Protocol contracts are live on Sepolia. Off-chain integration (solver, watchtower, Cloud KMS signing + EIP-7702 delegation) is in progress.
| Aspect | Without IRSB | With IRSB |
|---|---|---|
| Execution Proof | No standardized proof. Solvers claim execution without verifiable evidence. | Cryptographic receipts with intentHash, evidenceHash, and solver signatures on-chain. |
| Solver Accountability | No consequences for bad fills, missed deadlines, or front-running. | Staked bonds (min 0.1 ETH) slashable for violations. 3 strikes = permanent ban. |
| Dispute Resolution | Manual, off-chain complaints. No formal process. Users are on their own. | 1-hour challenge window. Deterministic auto-slash for timeouts. Optimistic resolution with counter-bonds for complex cases. |
| Solver Reputation | Siloed per protocol. Opaque. Based on informal trust, not data. | On-chain IntentScore. Portable via ERC-8004. Weighted composite of success rate, dispute history, and stake. |
| User Compensation | None. Users absorb losses from bad solver behavior. | 80% of slashed bond goes to affected user. Challenger gets 15%. |
| Intent Verification | Users trust the solver blindly. No way to audit execution path. | V2 dual attestation (solver + client EIP-712 signatures). Privacy levels for sensitive data. |
| Cross-Protocol Identity | Solvers start from zero reputation on every new protocol. | ERC-8004 agent registration. IRSB publishes validation signals readable by any protocol. |
| Payment Accountability | HTTP payments (x402) have no proof of delivery on-chain. | irsb-x402 package links HTTP 402 payments to on-chain receipts proving service delivery. |
| Key Security | Hot wallets with private keys. Single point of compromise. | Cloud KMS + EIP-7702 WalletDelegate: keys never leave HSM hardware, on-chain caveat enforcers (spend limits, time windows, allowed targets, allowed methods, nonce). |
| Signing Policy | Sign anything requested. No typed action constraints. | EIP-7702 WalletDelegate with 5 caveat enforcers restricts all delegated transactions. SpendLimitEnforcer, TimeWindowEnforcer, AllowedTargetsEnforcer, AllowedMethodsEnforcer, NonceEnforcer. |
Execution Proof
Without IRSB
No standardized proof. Solvers claim execution without verifiable evidence.
With IRSB
Cryptographic receipts with intentHash, evidenceHash, and solver signatures on-chain.
Solver Accountability
Without IRSB
No consequences for bad fills, missed deadlines, or front-running.
With IRSB
Staked bonds (min 0.1 ETH) slashable for violations. 3 strikes = permanent ban.
Dispute Resolution
Without IRSB
Manual, off-chain complaints. No formal process. Users are on their own.
With IRSB
1-hour challenge window. Deterministic auto-slash for timeouts. Optimistic resolution with counter-bonds for complex cases.
Solver Reputation
Without IRSB
Siloed per protocol. Opaque. Based on informal trust, not data.
With IRSB
On-chain IntentScore. Portable via ERC-8004. Weighted composite of success rate, dispute history, and stake.
User Compensation
Without IRSB
None. Users absorb losses from bad solver behavior.
With IRSB
80% of slashed bond goes to affected user. Challenger gets 15%.
Intent Verification
Without IRSB
Users trust the solver blindly. No way to audit execution path.
With IRSB
V2 dual attestation (solver + client EIP-712 signatures). Privacy levels for sensitive data.
Cross-Protocol Identity
Without IRSB
Solvers start from zero reputation on every new protocol.
With IRSB
ERC-8004 agent registration. IRSB publishes validation signals readable by any protocol.
Payment Accountability
Without IRSB
HTTP payments (x402) have no proof of delivery on-chain.
With IRSB
irsb-x402 package links HTTP 402 payments to on-chain receipts proving service delivery.
Key Security
Without IRSB
Hot wallets with private keys. Single point of compromise.
With IRSB
Cloud KMS + EIP-7702 WalletDelegate: keys never leave HSM hardware, on-chain caveat enforcers (spend limits, time windows, allowed targets, allowed methods, nonce).
Signing Policy
Without IRSB
Sign anything requested. No typed action constraints.
With IRSB
EIP-7702 WalletDelegate with 5 caveat enforcers restricts all delegated transactions. SpendLimitEnforcer, TimeWindowEnforcer, AllowedTargetsEnforcer, AllowedMethodsEnforcer, NonceEnforcer.