Posts on this site are timestamped with OpenTimestamps. When a post is published (or later edited), the SHA-256 hash of its Markdown source is recorded in a small proof file and anchored in the Bitcoin blockchain. That proves the text existed in exactly this form by the date shown — independently of this site, and without trusting me.

To verify a proof yourself, download the .sha256 and .ots files for a post and run, with the OpenTimestamps client installed:

ots verify name.sha256.ots

This confirms the hash inside the .sha256 file was committed to Bitcoin at the stated time. The Markdown source files themselves live in a private repository, so the final step — checking that a given text matches the hash — works on disclosure: given the source file, sha256sum -c name.sha256 confirms the match. Edits are never hidden; a revised post simply gains a new proof line below, and earlier proofs are kept.

DatePostSHA-256ProofStatus
June 9, 2026 A Mill Owner Buys a Page 13e9a21daf4c… .sha256 · .ots awaiting Bitcoin confirmation