Skip navigation
9Chain Docs

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

FileSize
wp-en.md205,663
SHA-256bde37a7d199448be86a48826aad1f12e4e7f9ff42bc9e3ee0f9c3bb6f8e3c297
Anchored at

A proof needs a few hours to be confirmed by a Bitcoin block. While waiting, four independent calendar servers hold the commitment; once confirmed, the verify command returns the Bitcoin block height and time.

Three steps to verify

  1. Download all three files

    The source file, the manifest, and the timestamp proof.

    Source fileManifestTimestamp proof

  2. Re-hash the source file and compare with the manifest

    sha256sum wp-en.md
# bde37a7d199448be86a48826aad1f12e4e7f9ff42bc9e3ee0f9c3bb6f8e3c297

  3. Check the timestamp proof with the OpenTimestamps tool

    Option A — nothing to install

    Open the OpenTimestamps site and drop manifest.json and manifest.json.ots into the verify box.

    opentimestamps.org

    Option B — command line

    npm install opentimestamps
node node_modules/opentimestamps/ots-cli.js verify manifest.json.ots

    Run this in the folder holding all three downloaded files. On Linux and macOS there is also the official Python client: pip install opentimestamps-client then ots 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.

Learn about OpenTimestamps