What this site said, and where the chain stood.
Each time the company passes a checkpoint, the pages change and the change is sealed: the fingerprint of every page is written into a manifest, and the manifest’s fingerprint is stamped into Bitcoin; when the version is also sealed on the chain, its receipt is listed beside it. And every morning, whether or not anything changed, the tip of the chain itself is stamped into Bitcoin. A stranger can verify both without trusting Recognitium.
Versions of this site
Earlier versions (19)
How to check a version
Download the manifest of the version. Recompute its SHA-256. If the version carries a receipt, paste its ID at /verify: the engine answers and your browser re-derives the chain tip itself. For the Bitcoin proof, run the free OpenTimestamps client against the manifest’s proof file, as described below. The manifest lists every page with its own fingerprint, so any single page can be checked against it.
This page is not part of the manifest it describes, since it lists the proofs the manifest produces.
The anchors in Bitcoin
Every day at 07:00 UTC, on our own server, the current tip of the receipt chain is written to a small file and its fingerprint is submitted to the OpenTimestamps calendars, which fold it into a Bitcoin transaction. A few hours later the proof is final and names the block. What this gives a stranger: the chain tip of a given day existed no later than that Bitcoin block. Since every receipt is committed under the tip, every receipt sealed before that day inherits the bound. Recognitium cannot move a receipt later than the block, and cannot rewrite the chain behind a tip that Bitcoin has seen without the rewrite showing. The whole mechanism costs nothing; the calendars pay the Bitcoin fee.
Verify an anchor, with no account and no trust in us
Install the free client, then verify the proof against the anchored file. The verification needs a Bitcoin node; without one, the info command still shows the attestation and, once the proof is upgraded, the block height.
pip install opentimestamps-client ots verify 2026-09-05_seq145814.tip.json.ots ots info 2026-09-05_seq145814.tip.json.ots
First anchor: 5 September 2026, sequence 145,814.