Verify
Verify a document
Drop the file and the owner’s reveal (digest and nonce, or a reveal file). This page hashes the file in your browser and checks the salted commitment against PUBLIC receipts. The file stays on this device. A bare document hash is never enough, and is never published.
Try it on the demo file
Download the anonymized demo document, then drop it below together with the owner reveal file you were given (digest and nonce). The file is hashed in your browser. It stays on this device.
Waiting for a file and a reveal.
What PASS and REFUSED mean
PASS: every claim in scope is supported by a stored source passage.
REFUSED: claim failures, unresolved holds, or missing evidence blocked the document. HOLD on a claim is never itself a failure; an unresolved HOLD can still refuse the document.
What the three cryptographic checks prove
Signature valid: the published tree head matches the DEMO KEY (Ed25519 public key). Inclusion: this receipt hash is in the Merkle log. Record unchanged: the canonical manifest still hashes to the logged leaf. The signing key on this staging build is a DEMO KEY, labelled on every receipt page. Its fingerprint is in the page footer.