Toad Earthworks, go to the homepage Call (740) 729-8337

Proof of the legal texts

For each legal text on this website, the text from the heading to the version line is recorded, without navigation, header and footer, and its SHA-256 checksum anchored in the Bitcoin blockchain via OpenTimestamps. Listed per version are the checksum, the block, the Merkle root, the proof files and the independent archive copy.

Scope

The text existed in this version no later than the time of the block and has been unchanged since.

On the Merkle root

Every Bitcoin block carries a single value in its header in which its entire content is condensed: the Merkle root. It is computed in stages from pairs of all transactions in the block; a single differing transaction yields a different root. What is timestamped is the manifest of this version, which contains the checksum of the text; OpenTimestamps bundles it with further submissions, and the root of that bundle enters the block within one transaction. The proof file supplies the link: it contains the complete chain of computation from the manifest to the Merkle root of the block named above. That root is retrieved from the raw data of public block explorers, not from their web interface.

Chain of proof 1 Legal text page.txt SHA-256 2 Checksum 64 hex digits component of 3 Manifest manifest.json: URL, time, checksum SHA-256, timestamped 4 Proof file manifest.json.ots: chain of computation yields 5 Merkle root in the block header, public

Accessibility

Current version Awaiting confirmation
Date stated in the document
November 10, 2026
Checksum of the text
3c823ab80faf838145ce11db4902f3777509c535a564f774a754fff6485cd0c9
Recorded on
November 10, 2026, 16:21 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Imprint

Current version Awaiting confirmation
Date stated in the document
November 10, 2026
Checksum of the text
3f4d730ef400fef8817caf546640782257cad8614283cdf48a663dcb45fbe701
Recorded on
November 10, 2026, 16:21 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Privacy Policy

Current version Awaiting confirmation
Date stated in the document
November 10, 2026
Checksum of the text
450df404787f242dadebc0ccdb09a43881780ac0da8e871d0204b33dcb2f6db9
Recorded on
November 10, 2026, 16:21 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Terms of Use

Current version Awaiting confirmation
Date stated in the document
November 10, 2026
Checksum of the text
7bec3b4ea95da3664b04b25a2e22e599c938558a4cc8f81f9fa25c02e3fb6037
Recorded on
November 10, 2026, 16:21 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Independent verification

  1. Load the proof files of the version: page.txt, manifest.json, manifest.json.ots. Alternatively the archive copy in raw form …id_/.
  2. shasum -a 256 page.txt yields the checksum shown above; the same value appears in the manifest under sha256_text.
  3. ots verify -f manifest.json manifest.json.ots from the opentimestamps-client package confirms block and time. Without a Bitcoin node of your own, the verifier at opentimestamps.org does this.
  4. Compare the Merkle root shown above against the block header. Raw data: blockchain.info/block-height/<no>?format=json.

As of November 10, 2026, 16:21 UTC