Technical primer
Blockchain-Anchored Timestamps
How SHA-256 + on-chain anchoring creates mathematically verifiable proof that a specific file existed at a specific time — and why that turns out to be valuable for creators, claims adjusters, attorneys, and developers.
What the mechanism actually is
- A file is reduced to a 256-bit fingerprint using SHA-256 — a standard cryptographic hash function published by NIST in 2001 (FIPS 180-4). Two different files produce two different hashes; finding a collision is computationally infeasible.
- The hash is written to a public blockchain in a single transaction (or aggregated into a Merkle tree and written as a batch). Once the block is confirmed, the record is effectively immutable — rewriting it requires rewriting every subsequent block, which the blockchain's consensus mechanism makes prohibitively expensive.
- The block's timestamp is agreed upon by the network's validators. Anyone can inspect the block and see the hash + timestamp.
- Later, to verify, you compute SHA-256 of the file in question and compare it to the hash recorded on-chain. Match = the file existed at or before the block's timestamp. Mismatch = the file has been altered since anchoring.
What it proves — and what it doesn't
It proves: the specific file bytes existed at or before a specific point in time, independently verifiable by anyone with access to the file and a block explorer.
It does not prove: authorship, ownership, originality, legal rights, or intent. The person who anchored the hash controls the timestamp, but a hash by itself doesn't establish who created the bytes. In practice, the timestamp plus surrounding context (metadata, distribution history, witness testimony) is what establishes authorship. The timestamp is the anchor; the surrounding facts are the case.
Implementations
OpenTimestamps (open source)
Open standard launched 2016 by Peter Todd. Aggregates hashes into Merkle trees and anchors the roots to Bitcoin. Fully open-source clients and verifiers. Gold standard for reproducibility.
ProofAnchor
Creator-facing commercial service. Anchors SHA-256 hashes directly to Polygon (fast, cheap). Public verification URL per proof at proofanchor.com/verify/<id>. Offline verification via the free verify-proof Python package. File content never uploaded.
ProofLedger
Enterprise/legal-facing sibling service. Dual-chain anchoring to both Polygon (instant) and Bitcoin (daily batched Merkle). Positioned for claims adjudication, pre-loss documentation, and litigation evidence.
How it compares
| Method | Time | Cost | Independent verification |
|---|---|---|---|
| US Copyright Office | ~6 months | $65+ | Office records only |
| Notary | Minutes | $5-25 | Notary's journal (if retained) |
| "Poor man's copyright" | Days | Postage | None — postmark ≠ contents |
| OpenTimestamps | Minutes | Free | Bitcoin ledger |
| ProofAnchor / ProofLedger | Seconds | Cents | Polygon / Bitcoin ledger |
Verify offline with verify-proof
Anyone can verify a ProofAnchor-issued proof without trusting ProofAnchor's servers:
pip install verify-proof
verify-proof verify my-file.pdf --proof proof.jsonSource code: github.com/Fulcrum-Enterprises/verify-proof. Runnable in air-gapped environments — the verifier only needs the file + the proof JSON.