Receipt verification

Every priced or refused decision commits a keccak256 record into an append-only, hash-chained ledger. Each record's chain hash makes after-the-fact rewriting detectable. Paste a receipt's record_hash to verify it against the live chain.

Decision ledger verified — 0 records keccak256

How verification works

1. Each record commits: request id, service, request hash, market/event ids, rule hash, model version, the probability or refusal, interval, confidence, economics, why-summary, calibration scope, source freshness, time, payment reference, previous hash, and chain hash.
2. Verifying recomputes every record hash and re-links the chain; any edit anywhere breaks the chain from that point forward.
3. No private payment data is ever stored in a receipt.