Verify this document yourself
The contents of this documentation are hashed with SHA-256 and anchored to Bitcoin via OpenTimestamps. You do not have to take our word for it — the three steps below let you prove it yourself, with independent tools.
What it proves
- The source file exactly as downloaded existed before the anchoring moment.
- It has not been modified since — change one character and the hash changes completely.
What it does NOT prove
- It does not prove the content is true. Anchoring guarantees integrity and time, not claims.
- It is not a signature from any authority. Nothing vouches for it except the Bitcoin blockchain itself.
Anchored file
| File | Size |
|---|---|
wp-en.md | 235,919 |
| SHA-256 | c2d077d3bd35cf30965cae320f230f3235663e09f6a1053caec4e2c3a70c4bf0 |
| Anchored at | |
| Bitcoin confirmation | awaiting a Bitcoin block — four independent calendar servers hold the commitment |
A proof passes through two stages: the commitment — four independent calendar servers hold the hash the moment it is anchored — and then confirmation, when a Bitcoin block seals it, usually within a few hours. The “Bitcoin confirmation” row above says which stage this proof has reached; the block height is something anyone can look up without trusting this page.
Three steps to verify
Download all three files
The source file, the manifest, and the timestamp proof.
Re-hash the source file and compare with the manifest
sha256sum wp-en.md # c2d077d3bd35cf30965cae320f230f3235663e09f6a1053caec4e2c3a70c4bf0Check the timestamp proof with the OpenTimestamps tool
Option A — nothing to install
Open the OpenTimestamps site and drop
manifest.jsonandmanifest.json.otsinto the verify box.Option B — command line
npm install opentimestamps node node_modules/opentimestamps/ots-cli.js verify manifest.json.otsRun this in the folder holding all three downloaded files. On Linux and macOS there is also the official Python client:
pip install opentimestamps-clientthenots verify manifest.json.ots.Either way, verification talks to no server of ours — it checks directly against the Bitcoin blockchain.
One thing to be clear about
What is anchored is the source Markdown file, not the web page you are reading. The page is rebuilt from a content management system, and that system normalises the Markdown (padding table cells, escaping certain characters). Hashing the page source will therefore not produce the same hash — hash the downloaded file above.