Skip to content

OpenTimestamps

Timestamping of documents on the Bitcoin blockchain, through the open OpenTimestamps protocol and its public calendar servers.

OpenTimestamps

Drop a file here to timestamp it, or a receipt/proof (*.ots) to verify it.

Available operations

One box for three operations: the page recognizes the file type on its own.

Timestamp

Drop any file: the browser computes its fingerprint for the calendar servers. You get an .ots receipt.

Upgrade

Drop an .ots receipt: once the fingerprint is in a Bitcoin block, it becomes a full, verifiable proof.

Verify

Drop an .ots proof: the page checks it against the Bitcoin block explorers and shows you the date it attests.

How it works

Three steps, from the file on your computer to a block of the Bitcoin blockchain.

Fingerprint

The browser computes the file’s hash, a fingerprint that uniquely identifies it, sending it to no one.

Aggregation

Calendar servers gather thousands of fingerprints into a Merkle tree, attested by a single transaction.

Anchoring

The tree’s root enters a Bitcoin block: from then on, altering the date is prohibitive for anyone.

From receipt to proof

Immediately. You download an .ots receipt: it lists the calendar servers reached, but is not yet verifiable.

After about an hour. The fingerprint enters a Bitcoin block and the calendar servers can complete the receipt.

From then on. Dropping the receipt again upgrades it to a proof: anyone can verify it, even with a Bitcoin node.

Document with a Bitcoin wax seal

Why OpenTimestamps

An open protocol, independent of vendors and blockchains, suitable for third-party auditability requirements.

Private

The fingerprint is sent, never your document.

Free

Public calendar servers, with no registration.

Verifiable

Checked without any server or intermediary.

Robust

Protected by the Bitcoin network’s proof-of-work.

Value and limits of the proof

A timestamp attests to the existence of a file, not to its content.

What it attests

The existence of the file, unchanged, before the attested date.

  • Highest reliability with Bitcoin
  • Lower reliability on other chains
  • Private chains: operator trust

What it cannot attest

Nothing about the file’s author or the merit of its content.

  • Authorship: needs a signature
  • Veracity, validity or correctness
  • Absence of hidden timestamps
Warning

Retention of the document and the proof

The timestamped document is never transmitted to the calendar servers: the user is responsible for storing the file and its attestation proof. The submission receipt can only be upgraded through the calendar servers used for submission, whereas the complete proof can be verified independently.

Technical details

Advanced tutorial

The OpenTimestamps protocol broken down into its six steps: hash computation, submission, loading, reading, upgrade and proof verification.

View the tutorial