W3SEQ
← All articles
TechOctober 20, 2026 · 3 min

W3SEQ and OpenTimestamps — Bitcoin anchoring explained

How does W3SEQ anchor your proofs in the Bitcoin blockchain? What is OpenTimestamps? Technical and practical explanation.

By W3SEQ

How does W3SEQ anchor your proofs in the Bitcoin blockchain? What is OpenTimestamps? Technical and practical explanation.

When you seal a work on W3SEQ, the proof doesn't rely solely on our servers — it's also anchored in the Bitcoin blockchain, the most resilient public infrastructure in existence. But how exactly does this work?

What is OpenTimestamps?

OpenTimestamps is an open-source protocol that lets anyone anchor data in the Bitcoin blockchain — without paying transaction fees, and without revealing what's being anchored.

The principle: 1. You submit a hash (SHA-256 fingerprint) to an OpenTimestamps calendar server 2. The server aggregates thousands of hashes into a Merkle tree 3. Once per hour, the root of the tree is published in a Bitcoin transaction 4. The server returns a proof file (.ots) that lets anyone verify your hash was part of that tree

Result: your hash is now anchored in Bitcoin, without revealing the underlying data, and without paying anything.

Why is this reliable?

Bitcoin is the world's most battle-tested public blockchain (since 2009). Each block is validated by thousands of independent nodes, secured by massive mining power.

Once your hash is included in a Bitcoin block, it becomes cryptographically impossible to modify or erase. Even if W3SEQ disappeared tomorrow, your proof would remain verifiable.

How W3SEQ uses OpenTimestamps

When you seal a work, W3SEQ does the following:

1. Computes the SHA-256 hash of your file (locally, in your browser) 2. Submits this hash to an OpenTimestamps calendar server 3. Receives the .ots proof file 4. Includes this proof file in your sealed envelope (ZIP) 5. Anchors the proof in Bitcoin within the next hour

The .ots file is stored in the envelope, alongside your manifest and Ed25519 signature.

How to verify a Bitcoin anchor

Verifying an OpenTimestamps anchor requires two things:

  • The .ots file (included in your sealed envelope)
  • A Bitcoin node (or a public block explorer)
The verification: 1. Parse the .ots file → retrieve the hash and the Bitcoin block header 2. Query the Bitcoin blockchain → verify the block exists and matches 3. Compute the Merkle path → verify that your hash is part of the block

The result: your hash was anchored in Bitcoin at block height X, on date Y.

Why Bitcoin and not Ethereum?

Several reasons:

  • Longevity: Bitcoin has been operating since 2009 without interruption. Ethereum is younger and has undergone major changes (e.g. The Merge).
  • Simplicity: Bitcoin's UTXO model and Merkle tree structure are well understood, well documented, and easy to verify.
  • Cost: OpenTimestamps works without paying fees (thanks to aggregation). Ethereum anchoring would cost gas per proof.
  • Independence: OpenTimestamps is a decentralized protocol, not controlled by W3SEQ.

The verdict

Bitcoin anchoring is not marketing — it's the cryptographic foundation of your proof. Even if W3SEQ ceased operations, your sealed envelope would remain:

  • Verifiable (the hash, signature and .ots file are in the ZIP)
  • Proof of existence (the Bitcoin block confirms the anchoring date)
  • Immutable (no one can alter a Bitcoin block)
W3SEQ is not just a timestamping service. It's an anchor to a public infrastructure that will outlive any company.

Ready to try?