Verify a receipt — right here, in your browser
Everything runs client-side: this page has a Content-Security-Policy that forbids talking to any other host, so your receipt never leaves this tab — you can even cut the network once the page is loaded and verification still works.
.attest bundle or .attest.json receipt here
or click to pick a file
No receipt handy? download it — a receipt from a fictional store, Nebula Games, that no longer exists.
Drop or pick the issuer’s key-manifest JSON:
Prove a receipt is yours (salt disclosure)
A receipt seals a commitment to the buyer’s identifier. Disclosing the salt lets a verifier recompute it — a deliberate, replayable proof: whoever you show it to can replay it, so disclose only to parties you would show the receipt to anyway (spec §8.1). This page stores nothing.
The case
An archive holds an offline copy of a digital good it is authorized to release, but only to the people who bought it — a game, an album, a film, an ebook, a piece of software. The store that sold it is gone, and its customer database went with it. The archive still has to decide, with no human in the loop, which claimants may download the file. That decision is what attest is for — and only that: while the seller is still around, or hands the buyer a DRM-free installer, or where a judge is the one reading the evidence, nothing here is needed. No archive runs such a gate today; whether anyone ever will is the open question.
How it works
- The store signs. At checkout, the seller signs a receipt — title, terms, artifact hashes, survivability promises — with its published signing keys.
- You hold it. The buyer keeps the
.attestbundle anywhere: disk, cloud, USB. No account has to stay alive. - Anyone verifies, offline. Any verifier — this page, the CLI, a marketplace — checks the signature against the issuer’s key material. The store can disappear; the math doesn’t.
What attest is not
- Not the content. A receipt is evidence of a license grant — it never hosts, indexes, or unlocks the work itself.
- Not a DRM tool. It never strips or bypasses DRM, and a receipt for a DRM-bound purchase says so honestly.
- Not a blockchain. A signed receipt needs no consensus, token, or wallet. (A strictly optional transparency-anchoring layer is future roadmap — the only place a chain will ever appear.)
- Not a resale market. v0.1 defines no transfer protocol at all; v0.2 §17 adds transfer only where the issuer mediates it, and never a general right to resell.
Skeptical? Good — read the FAQ, it answers the questions a reasonable person asks.