Verify a report
Choose an engagement report and this page will tell you whether it is the file PeerTest produced, when that was recorded, and whether the record is anchored somewhere nobody can edit.
Your file does not leave your browser. It is hashed here, and only the hash is sent — sixty-four characters that reveal nothing about the app or the people who tested it. PeerTest answers with a Merkle path, a signed root and an OpenTimestamps receipt, and this page checks all three arithmetically rather than taking our word for any of it.
Checking it without us
This page is not the authority and should not be. The same three checks run from a command line, against a saved attestation, with no network and nothing of ours:
node verify.mjs report.html attestation.jsonThe verifier is MIT-licensed and readable. A verifier nobody can read is a promise rather than a proof.
What each answer means
- This file is what PeerTest produced
- The SHA-256 of your file matches a digest PeerTest recorded, and the record says when. If the file has been edited since, this fails — that is what it is for.
- It was recorded when it says
- The record is a leaf in a Merkle tree whose root PeerTest signed. The path is folded here, in your browser, and it either reaches that root or it does not.
- The root is in a block
- The signed root was published to OpenTimestamps and committed to Bitcoin. Until a block confirms it — which takes hours, and is an ordinary state rather than a problem — this says not yet rather than failing.