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.jsonBatch 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
- The record is unaltered since it was signed.
- The holder of the published key issued it, and when.
- What was asked: the site, the action, and a hash of the listing.
What it does not prove
- That a site acted. The basis is self_reported. A listing counts as gone when a fresh search no longer shows it.
- That the receipt was not revoked after it was issued. An offline check cannot see that.
- The sample here is signed with a demo key.
Files
- receipt-verifier.js (the verifier this page runs)
- receipt-vectors.js (builds the 17 checks)
- receipt-signed.json (the four signed receipts)
- receipt-verify.py (independent verifier in Python)
- receipt-key.json (public key)
- receipt-spec (format and check order)
Key id