Verify without OriginProof

1. The file is the one recorded

Compute the SHA-256 of your file and compare it with the entry's “Content SHA-256”.

shasum -a 256 my-track.wav        # macOS / Linux
certutil -hashfile my-track.wav SHA256   # Windows

For sealed text, the recorded value is the SHA-256 of your secret (from your key file, as bytes) followed by the exact text.

2. The record says what the receipt says

Each entry is a small JSON record with sorted keys and no spaces. Its SHA-256 is the entry's “Record hash”. Fill in the values from the technical record (for a single record without a receipt, receiptId and seqNo are null):

printf '%s' '{"contentHash":"<CONTENT SHA-256>","kind":"item","proofId":"PR-XXXXXXXX","receiptId":"<receipt id>","recordedAt":"2026-11-13T12:00:00.000Z","seqNo":1,"v":1}' | shasum -a 256

kind is item for a file, commitment for sealed text and snapshot for a project folder.

3. The record existed when Bitcoin says

Download the entry's .ots file from the receipt page and check it with the open-source OpenTimestamps client:

pip install opentimestamps-client
ots info originproof-PR-XXXXXXXX.ots                       # shows the Bitcoin block
ots verify -d <RECORD HASH> originproof-PR-XXXXXXXX.ots    # needs a Bitcoin node

Without your own Bitcoin node, ots info shows the block number and the path to it; the block's Merkle root can then be compared on any block explorer. Learn more at opentimestamps.org.

All three checks together show that this exact content existed no later than that Bitcoin block. They do not show who made it. How OriginProof works.