← Back to Blog

Why We Anchor to the Blockchain

2026-04-03by Provelio Team

Why We Anchor to the Blockchain

Provelio uses RFC 3161 timestamps for instant proof, but we go further by anchoring every hash to a public blockchain via OpenTimestamps. Here's why.

The Problem with Centralized Trust

RFC 3161 Time Stamp Authorities are trusted third parties. They're reliable, standardized, and legally recognized. But they're also centralized — if a TSA is compromised, shuts down, or is pressured to alter records, the timestamps could be questioned.

Blockchain as an Immutable Ledger

A public blockchain is a battle-tested immutable ledger secured by a global network of participants. With continuous operation and an enormous network securing it, altering a confirmed block is practically impossible.

When we anchor a hash to the blockchain via OpenTimestamps:

  1. Your hash is aggregated with others into a Merkle tree
  2. The Merkle root is embedded in a blockchain transaction
  3. Once the block is confirmed, the proof is permanent

How Verification Works

To verify a blockchain-anchored timestamp:

  1. Take the original file and compute its SHA-256 hash
  2. Follow the Merkle path from the hash to the anchored block
  3. Confirm the block exists on the blockchain

This is entirely self-verifiable — no need to contact Provelio, no API calls, no trust in any single party.

The Belt-and-Suspenders Approach

We don't rely on the blockchain alone. RFC 3161 timestamps provide instant proof (within seconds), while blockchain confirmation takes minutes. Together, they give you:

  • Immediate legal-grade proof (RFC 3161)
  • Permanent decentralized proof (blockchain)

This dual-anchor approach means your proof survives even if Provelio itself ceases to exist.