How to Set Up Document Timestamping with Simple Proof for Government Records

In November 2025, El Salvador's environmental ministry launched a public portal where anyone can verify that government records haven't been altered since their creation. The proof doesn't rely on trusting the ministry itself. Instead, it's anchored to the Bitcoin blockchain, meaning verification works even if the government changes or the original servers go offline.

This isn't theoretical anymore. Document timestamping using Bitcoin is now operational in government settings, and the setup is more accessible than most agencies assume.

What Document Timestamping Actually Does

Document timestamping creates cryptographic proof that a specific file existed at a specific time. The process works by generating a unique fingerprint (a SHA-256 hash) of your document, then anchoring that hash to a trusted source of time.

The key insight: the hash reveals nothing about the document's contents. It simply proves that if someone later presents that exact file, it existed when the timestamp was created. Change even one character in the original, and the hash won't match.

Traditionally, governments relied on Trusted Timestamp Authorities (TSAs) operating under RFC 3161 standards. These work fine, but they require ongoing trust in the authority itself. If the TSA disappears or its keys are compromised, verification becomes problematic.

Bitcoin-anchored timestamps solve this by using the blockchain as an immutable, decentralized time source. The OpenTimestamps protocol, which has been operating since around 2016, aggregates document hashes into Merkle trees and anchors them efficiently to Bitcoin without requiring individual transactions for each file.

Setting Up OpenTimestamps for Government Records

Simple Proof provides Bitcoin-anchored timestamping specifically designed for governments and institutions. Their partnership with El Salvador's ministries demonstrates the approach at scale, with records publicly verifiable through dedicated portals.

Here's how the technical setup works:

Step 1: Compute the Document Hash Locally

Before anything leaves your systems, generate a SHA-256 hash of the document. This happens on your own infrastructure, meaning the actual file never needs to be transmitted. On most systems, this is a single command-line operation or API call.

This local-first approach matters for sensitive records. Birth certificates, property deeds, election results; none of the actual content ever touches external servers.

Step 2: Submit to Calendar Servers

The hash gets submitted to OpenTimestamps calendar servers (named Alice, Bob, and others in the public infrastructure). These servers aggregate incoming hashes and periodically anchor batches to Bitcoin using Merkle trees.

Simple Proof handles this aggregation for institutional deployments, providing reliability guarantees that public servers can't match for critical government applications.

Step 3: Download and Store the Proof File

You receive an .ots proof file that contains the cryptographic path linking your document's hash to the Bitcoin blockchain. Store this alongside your original records.

Step 4: Upgrade and Verify

Initially, the proof file is "pending" until the Bitcoin transaction confirms (typically within a few hours). Once confirmed, the proof can be verified independently by anyone using open source tools.

Verification recomputes the document hash and checks it against the blockchain proof. This works without contacting Simple Proof's servers, without internet access to anything except a Bitcoin node, and without trusting any single party.

Legal Standing and Compliance

For EU agencies, eIDAS-qualified timestamps carry specific legal presumptions about accuracy and integrity. Blockchain-based timestamps are being discussed under eIDAS 2.0 frameworks as a decentralized complement to traditional TSAs.

The practical advantage is redundancy. An agency can maintain RFC 3161 timestamps for immediate legal compliance while simultaneously anchoring to Bitcoin for long-term, authority-independent verification. The two approaches aren't mutually exclusive.

What This Costs

OpenTimestamps itself is free and open source. The protocol's efficiency means no per-document transaction fees; thousands of documents can share a single Bitcoin anchor through Merkle tree aggregation.

Simple Proof's institutional service adds reliability, support, and integration features appropriate for government deployments, but the underlying verification remains open. An agency using Simple Proof today could verify its records decades from now using nothing but open source tools and access to Bitcoin's blockchain.

Tradeoffs to Consider

Bitcoin anchoring proves a document existed at a specific time. It doesn't prove who created it, whether the content is accurate, or that proper procedures were followed. Timestamping is one layer of document integrity, not a complete records management solution.

There's also the confirmation delay. Bitcoin blocks arrive roughly every ten minutes, and most implementations wait for multiple confirmations. For records where immediate proof matters, RFC 3161 TSAs provide faster initial timestamps (though with different trust assumptions).

Finally, long-term verification depends on Bitcoin's continued operation. This seems like a safe bet given the network's track record, but it's worth acknowledging the dependency.

Getting Started

For agencies exploring this approach, the foundational work invented by Haber and Stornetta in 1991 (which predates Bitcoin by nearly two decades) established that Merkle tree timestamping creates mathematically sound proofs of document existence.

Bitcoin simply provides the most robust, publicly verifiable anchor available for those proofs. El Salvador's 2025 deployments demonstrate that this works at government scale, with public verification portals that any citizen can use.

The setup isn't complicated. The harder question is often organizational: deciding which records to timestamp, integrating with existing workflows, and establishing verification procedures. The cryptography is the easy part.