Proof
Don't trust us.
Verify.
Every attempt, every decision and every reply is written into a chain of records, each signed by the guardian's key and linked to the previous one. Nobody can change or remove a record without breaking the chain — and your browser checks it, not our server.
The signed ledger · test chain
Records
—
Head
—
On-chain anchors
—
Live status
Guardian process
—
Last heartbeat
—
Queue
—
Average latency
—
Model
—
Code version
—
Who signs, who holds
Guardian signer
—Signs records only. It holds no funds and cannot move money.
Vault (Safe)
—
Payment router
—Do not send ETH to this address directly: pay only from the site. A plain transfer carries no payment data, so it is not a payment and is not refunded automatically.
Project wallet
—
Anchoring key
0x2dd5e469762145ddaab554f2a6e1ada27e1d7686Balance reading…Sends the hourly anchor of the ledger head (a 0 ETH transaction to itself).
Reconciliation
—
Payouts
—
The plan (who gets what, in which Safe transaction, and the terms of the winner's streams) is signed into the ledger before the Safe's signers send it; they check it here. Each transaction is then checked on chain (its transfers and streams) and signed as its own record.
What v1 does not prove (yet)
- The ledger proves that nothing was changed after being signed. Until records are anchored on-chain, a fully rewritten chain signed again with the same key could only be caught by someone who kept an earlier copy — download it and keep it.
- The receipt shows the exact request and, when the round ends, the exact response. It proves what we sent and received, not what happens inside the model provider.
- The server code shown in "code version" is our claim; open-sourcing and reproducible deploys come later.
- The books (deposits, amounts forwarded, owed and paid out) are our database's records: your browser compares them with the balances it reads on chain, not with every transfer.
- Payments run on Robinhood Chain testnet for now: test ETH with no value. Free rounds keep a simulated vault.