Repository navigation
Exactly-once settlement of Request Network obligations through KeeperHub.
Request owns obligation identity. KeeperHub owns deterministic execution. ReqKeeper owns the
seam between them: the part that decides whether a send has already happened, and refuses
rather than guesses.
What is proven, and where the proof lives
Every number below is recomputed from docs/evidence/*.json by npm run verify:all, which uses
no credentials and reads Sepolia through public RPCs. docs/TRUTH.md is generated from that run.
- 50 concurrent worker processes against one obligation: 1 broadcast, 1 transaction, 0 duplicates.
- 3 workers against real KeeperHub and real Sepolia: one payment, reference
0xd9e6ee9360a89ed9,
transaction0x41b01a14cbdb8dd65c41eeb13285bfe9d47e1dc95990e33b0486ca5e5e353f52. - 9 crash checkpoints, real SIGKILL at each: zero duplicate payments.
- 38 recorded settlements, 38 physical sends, 38 distinct transactions and references.
- 38 replays of a settled obligation: 0 sends.
- 45 refusals, all before any provider write, at zero gas.
- 46 of 46 payment references re-derive from
keccak256(requestId + salt + paymentAddress). - Value moved through both KeeperHub surfaces: 38 over REST, 3 over MCP, each MCP settlement
carrying the KeeperHub execution id that produced it.
What it does not claim
Sepolia only; mainnet chain ids are refused in code. Settlement is confirmed at a stated depth,
never called final. The 50-worker race runs against a counting fixture; the live race is the
3-worker run above. docs/TRUTH.md carries the full list.
Assets
demo.mp4 — 95 seconds, no narration, every figure in it read from the evidence files at render
time.
Console: https://reqkeeper.vercel.app