Verify a timestamp proof yourself
The check page on this site verifies proofs using block headers from public block explorers. If you'd rather trust nobody but Bitcoin, verify with the official OpenTimestamps client and your own node.
What you need
- The original file and its proof (
video.mp4andvideo.mp4.ots). A check link from this site holds the proof: open it and choose “Download the proof”. - Python 3 and the OpenTimestamps client.
- For verifying: a Bitcoin Core node. The client's documentation says a pruned node is fine.
Steps
- Install the client:
pip3 install opentimestamps-client - If the proof is still pending, complete it by asking the calendars named inside it:
When the calendars have anchored it in Bitcoin, the client reports that the timestamp is complete.ots upgrade video.mp4.ots - Verify it. With the original file next to the proof:
The client hashes the file, follows the proof to a Bitcoin block using your node, and reports the block and date, for example:ots verify video.mp4.otsSuccess! Bitcoin block 358391 attests existence as of 2015-05-28.
The client's own README has more options, including how to point it at a node with different settings.
What “attests existence as of” means
The file existed no later than that block was mined. Block timestamps are only accurate to within an hour or two, so treat the time as approximate.
Without a node
The check page does the same calculation in your browser. It fetches the block header from two block explorers, checks they agree and that the header has real Bitcoin proof of work, and checks the proof leads to it. That's a strong check, but you're relying on the explorers to give you the block at the right height. A node removes that reliance.