The idea in one minute
- A hash function turns any file into a fixed fingerprint. Change one byte, get a different fingerprint. More on hashes →
- The fingerprint is put into a transaction on a public blockchain.
- The transaction is included in a block with a network timestamp. Every later block builds on it, so it cannot be changed or moved.
- Later, you recompute the hash of your file and show it matches the one on-chain.
That proves the file existed at or before the block time.
Why not just trust a company's database?
A database entry can be edited by whoever runs the database. A public blockchain record is held by thousands of independent computers: nobody, including the timestamping service, can alter or backdate it.
Batching: many files, one transaction
Writing each file separately is slow and costly. Services combine many hashes into a single summary hash (often using a Merkle tree) and write that. Each file's proof still links back to the anchored value. SecureAuthor anchors twice a day, at 00:00 and 12:00 UTC on Polygon Mainnet.
What a blockchain timestamp proves — and what it doesn't
Proves: this exact file existed no later than time T, and the record is unchanged.
Does not prove by itself: who created the work, or that it was not created earlier by someone else. That is why you combine it with drafts, source files and early registration. How to prove you created something first →
Try it
Timestamp a file for free — certificate in seconds, Polygon record at the next run.