DORAHACKS KEEPERHUB HACKATHON 2026 // AGENT ECONOMY
SEPOLIA TESTNET · 11155111
STATUS: 719/719 TESTS PASSING
0 DUP / 50 WORKERS

PAY INVOICES THROUGH KEEPERHUB WITHOUT DOUBLE-SPENDING

AI agents can't move money safely on their own — they guess, retry, and overpay. ReqKeeper takes a Request Network invoice, checks it hasn't been paid, verifies the exact bytes that will hit the chain, and sends payment through KeeperHub exactly once. No duplicates. No wasted gas. 38 real settlements on Sepolia prove it works.

SOURCE CODE ↗ SUBMISSION DOCS ↗
PIPELINE ⇄ KEEPERHUB CALLDATA GATE // 0 GAS
DRAG · CLICK TO RUN GATE: 0 GAS · 0 DUP
719/719
Tests Passing
142 suites · all green
0 DUP
50-Worker Race
50 workers, 1 payment, 0 duplicates
9/9
Crash Recovery
Process killed mid-payment, recovered every time
47/47
Signatures Verified
Invoice payer/payee identity confirmed
38
On-Chain Settlements
Real transactions on Sepolia testnet
24H ∞
Expiry Bug Fixed
Keys no longer expire after 24 hours
THE THEME · DORAHACKS KEEPERHUB 2026
“KeeperHub executes — deterministically, on demand, with full control and an auditable record. Agents are probabilistic by design. Onchain value transfer does not forgive that, ask an agent to move funds and it reinterprets what you meant, at the moment it matters most, every single time. KeeperHub removes the reinterpretation, your agent composes a workflow through our MCP server, you review it, you dry run it without touching the chain, and then that exact workflow executes. Nothing is inferred at execution time.”
— DoraHacks & KeeperHub Hackathon Brief
What ReqKeeper adds to KeeperHub:
ReqKeeper makes KeeperHub safe for autonomous payments. It links every payment to a verified Request invoice, checks transaction data before broadcast, and guarantees each invoice is paid only once — even across crashes or network retries.

HOW IT WORKS

Five checks between an invoice and a payment. Each one prevents a different class of failure.

STEP 1
Read Invoice
Checks the Request Network invoice to confirm payer, payee, amount, and cryptographic signatures.
✓ Fake invoices blocked
STEP 2
Check Rules
Verifies spending limits, allowed tokens, and recipient addresses before touching the chain.
✓ Zero gas wasted
STEP 3
Reserve Payment
Locks the invoice in the local database so concurrent workers cannot pay twice.
✓ 50 workers → 1 payment
STEP 4
Verify Calldata
Decodes transaction bytes and checks every parameter against invoice facts before sending.
✓ Tampered data blocked
STEP 5
Send via KeeperHub
Dispatches through KeeperHub's REST or MCP API, then confirms receipt on Sepolia.
✓ 38 confirmed on Sepolia

RUN IT YOURSELF

Click a command to see real output, or copy it to run locally. No credentials needed.

npm test
UPSTREAM BUG FIX · KEEPERHUB PR #2372

Bug found and fixed: idempotency key stays locked after failures (PR #2372, resolving Issue #1840).

When a transaction failed permanently (out of gas, contract revert), KeeperHub locked the idempotency key forever — blocking any retry. Our PR releases the key on terminal failures while keeping duplicate protection intact. 17 unit tests pass.

EXPLORE THE CONSOLE

Six views into real settlement data, test runs, and interactive demos.

01 / PROOFS RECORDED
See 50 workers race on 1 invoice with 0 duplicates, plus crash recovery logs.
Open Proofs →
02 / OVERVIEW 83 ROWS
Charts and breakdown of all 83 recorded rows and real settlement transactions.
Open Overview →
03 / OBLIGATIONS SEARCHABLE
Searchable table of all 83 Sepolia obligations and 30 test cases.
Open Obligations →
04 / SIMULATOR INTERACTIVE
Step-by-step interactive replay showing 1 send on first try, 0 sends on retry.
Open Simulator →
05 / KEEPERHUB SURFACES REST + MCP
Direct comparison of KeeperHub REST API vs MCP server.
Open Surfaces →
06 / VERIFY LOCALLY 11 CHECKS
Commands you can run locally to check every proof yourself. Zero API keys needed.
Open Verify →

PROOF

50-Worker Race

Crash Recoverynpm run crash
One Payment End-to-End
    Payments via REST & MCP
    ObligationKeeperHub executionTransactionBlockSends