Seen on my terms

Check a receipt

Open verification. Closed production.

Verify the receipt without receiving the person's history or the production logic behind it. Patent pending.

Check one

Add a request hash to confirm the receipt covers that exact request. The hash is the SHA-256 of the sorted-key JSON of site, action and listing_ref.

Run the 17 checks

Valid, altered, forged, expired, wrong audience, wrong binding and bad batch proof. Your browser builds them from four signed receipts and runs the same verifier file you can download below.

Download vectors.json

Batch root

The four sample receipts are bound into one Merkle root:

computing

Bitcoin timestamp: not submitted yet. The root is published here first, so a later timestamp can be checked against it.

What a valid receipt proves

What it does not prove

Files

Key id