Check what a record proves.

Public demo verification (hash match)

1. Generate a receipt on /proof (run the demo).
2. Copy the receipt JSON.
3. Compute the hash: sha256(JSON.stringify(receipt)).
4. Confirm it matches the displayed hash.

Example (Node.js)

import crypto from "node:crypto";

const receipt = /* paste JSON object */;
const hash = crypto.createHash("sha256").update(JSON.stringify(receipt)).digest("hex");
console.log("0x" + hash.slice(0, 16));

What this proves (and what it doesn’t)

• Checks: whether the receipt JSON matches the hash saved by the local demo. Both are stored in the same browser and can be replaced together.
• Doesn’t prove: identity, key custody, or ledger immutability (those require signatures + storage semantics).

Production verification

Evaluate the actual receipt type, signer, trust anchor, request binding and storage path for your workflow. A local hash match does not establish those properties or prove a real action occurred.

See: Security