Offline Verification

Verify a Decision Receipt

Paste a Decision Receipt JSON below to inspect its structure, recorded replay status, policy result, and attestations. No account or API key is required; signer identity still depends on a key established out of band. A valid result concerns the receipt record and does not prove that the described action occurred or was correct.

Two samples, on purpose. Load a Real Receipt pulls the newest entry from the public ledger — it is genuine and it passes. Load Synthetic Invalid Sample is fictional and uses a placeholder signature; it is expected to fail. Seeing both is the point: a verifier that cannot fail tells you nothing when it passes.

Do all of this without us. This page runs the checks on our server, which means you are still taking our word for the result. Two kits remove that: the verify kit (25 KB, Python 3) checks a receipt against the published Ed25519 key on your own machine, and the replay kit (30 KB, Node 20) re-executes the decision and reproduces its hash. No install, no account, no network. Each ships adversarial fixtures and a self-test, because a tool that cannot demonstrate a failure is indistinguishable from one that always says yes. Verification answers is this what you signed; replay answers was the decision reproducible; neither substitutes for the other.