Proof explorer
Verify a
compute receipt.
Every billable operation produces a signed record. Look one up by receipt ID or hash and check it yourself — no account required.
- Receipts signed
- 4
- Receipts anchored
- 0
- Signer
- Platform key
- Network
- Robinhood Chain Testnet
Anchors
Recent anchor batches.
Merkle roots of receipt batches. Individual receipts are only listed to their project.
| Batch | Merkle root | Receipts | Status | Transaction | Created |
|---|---|---|---|---|---|
| batch_01M2KAFF7F… | 0x318f1d4e…ecf830 | 4 | Built · not broadcast | — | 2026-09-15 20:00:05 UTC |
Method
How verification works.
Verification depends only on public data and standard Ethereum cryptography. The platform cannot alter a receipt without invalidating its signature.
- 01CanonicalizeSerialize the payload with sorted keys and no whitespace.
- 02Hashkeccak256 over the UTF-8 bytes gives the receipt hash.
- 03RecoverEIP-191 recovery over the 32-byte hash yields the signer.
- 04IncludeThe receipt hash is a leaf in a batch Merkle tree.
- 05AnchorThe batch root is recorded by ReceiptAnchor on Robinhood Chain.
Signers
Trusted receipt signers
Receipts signed by any other address are reported as untrusted.
- 0x4A445F5EbB3e0f2494BF93d64108d28bc9D3e8B2Current