{{ plugin_icon }} OpenTimestamps

Your ArchiveBox server

Hashed hashes.json, added 16 random bytes, then hashed the combined bytes.

Saved the random bytes and verification steps in hashes.json.ots.

Hook started · {{ result.start_ts|date:"Y-m-d H:i:s" }} UTC

32-byte hash→

OpenTimestamps servers

Loading submission time…

Received the submitted hash and returned the timestamp proof.

Batch fingerprint→

Bitcoin

Publication target for the combined batch fingerprint.

Use the saved proof to verify its inclusion in a confirmed block.

Block time · available when verifying the proof

Verify publication

OpenTimestamps anchors the fingerprint of hashes.json in the Bitcoin blockchain, proving that the recorded content fingerprints existed by the confirmed block’s timestamp. Verification checks the archived files against those fingerprints and follows the timestamp proof to that Bitcoin block.

The timestamp also covers any TLSNotary receipt and saved response listed in the manifest. A declined or failed TLSNotary proof does not prevent timestamping the other archived files.

Download the proof and manifest, then open OpenTimestamps Stamp & Verify. Select hashes.json.ots and then hashes.json to check the timestamp and its Bitcoin attestation. A pending proof is waiting for Bitcoin confirmation.

Upgrade and verify later

Keep both files together. After Bitcoin confirmation, upgrade and verify with the OpenTimestamps client:

ots upgrade hashes.json.ots
ots verify hashes.json.ots

How the archive trust chain works · OpenTimestamps client documentation