Bitcoin YearsThe Atlas
Menu

Bitcoin Years › Tools › Timestamp

Bitcoin timestamp

Prove that a file existed, exactly as it is, by the time a Bitcoin block was mined. Check an .ots proof here, or stamp a new file. Your browser does all the hashing: the file never leaves your device.

Verify a proof

Stamp a file

Stamping sends the file's SHA-256 hash, and nothing else, to the public OpenTimestamps calendar servers.

How it works

The proof is a short list of steps: append these bytes, hash, prepend those, hash again. Starting from your file's SHA-256, the steps end at the merkle root of one Bitcoin block, the 32 bytes every block header commits to. Your browser replays every step itself and fetches only that block's header from mempool.space (or blockstream.info) to compare. If one byte of the file changed, the first hash would differ and the path would lead nowhere.

Rewriting that block would mean redoing all the proof of work since it, which is why a Bitcoin timestamp is hard to fake. The same idea, a hash in a block as proof of time, is section 3 of the white paper, the timestamp server; see Bitcoin's own records on Proof of History.

Questions

What does a Bitcoin timestamp prove?

That a file existed, exactly as it is, no later than the time of a Bitcoin block. It does not prove who made it or that it was not made earlier.

Does my file get uploaded?

No. Your browser computes the file's SHA-256 hash; only that 32-byte hash goes to the calendar servers when you stamp. Verifying asks only for public block headers and, for a proof that is not finished yet, sends the proof's hash to the calendar that holds it.

What is an .ots file?

An OpenTimestamps proof: the list of hash steps that lead from your file's hash to the merkle root of a Bitcoin block. Anyone can check it, with this page or with the open-source ots client.

Why does a new stamp say it is not in a block yet?

Calendar servers collect many hashes and put one combined hash into a Bitcoin transaction. That takes a few hours. Open this page again with the same .ots file later and it fetches the finished path and offers the completed proof.

Who runs the calendar servers?

Independent volunteers of the OpenTimestamps project (opentimestamps.org); the stamp is sent to several so that one going offline does not matter. They never see your file, only its hash.

How is this different from the Proof of History page?

Proof of History shows Bitcoin's own historic transactions as raw bytes. This page lets you put your own file into the same clock.

Proof format: OpenTimestamps; this page uses its own small reader of the format, with hashes from @noble/hashes (MIT). Calendar servers: OpenTimestamps (a. and b.pool.opentimestamps.org), Eternity Wall, Catallaxy. Block headers: mempool.space, blockstream.info. The example is the hello-world proof from the OpenTimestamps client repository, loaded from GitHub.