Certificate
Certificate of Commitment
Status: Anchored via OpenTimestamps · Bitcoin confirmation pending
This is the certificate for the proof-of-concept commitment: the body of the book was frozen as a PDF, hashed with SHA-256, and the digests logged into OpenTimestamps calendars that anchor them periodically into Bitcoin. One edition per language; one hash per edition; one .ots proof per edition. The chain is the authority. If the hash of your file does not match the one below, the file has been altered.
English edition
- SHA-256
9d52300c6c201a9bc75cd2def80e745cb01a5f8b7195ef815c13f0dc18ef811b- OTS proof
- was-never-about-money_original.pdf.ots
- Pages
- 277
Spanish edition
- SHA-256
9e06fd3f7994037cd1c5e4debfe711a42486208020c2f664effac60032a4fe7d- OTS proof
- nunca-fue-sobre-el-dinero_original.pdf.ots
- Pages
- 298
OpenTimestamps anchor
- Method
- OpenTimestamps (opentimestamps.org)
- Network
- Bitcoin mainnet
- Inscribed
- 2026-05-04 (calendars logged the digests)
- Calendars
alice.btc.calendar.opentimestamps.org
bob.btc.calendar.opentimestamps.org
finney.calendar.eternitywall.com- Bitcoin transaction
- Pending
- Block height
- Pending
How to verify
Step 1 — verify the PDF is unaltered. Download the PDF from this site. Compute its SHA-256 hash from your system’s command line:
shasum -a 256 was-never-about-money_original.pdf
shasum -a 256 nunca-fue-sobre-el-dinero_original.pdf
Compare the result to the hash listed above for that edition. If they match, the file has not been altered. If they do not match, it has.
Step 2 — verify the Bitcoin anchor via OpenTimestamps. Download the .ots proof listed for each edition and place it next to the corresponding PDF. Then use the OpenTimestamps client (pip install opentimestamps-client) to verify:
ots verify was-never-about-money_original.pdf.ots
ots verify nunca-fue-sobre-el-dinero_original.pdf.ots
The command walks the proof down to the Bitcoin block that anchors it and reports the exact moment of commitment. If the proof has not yet been upgraded with the full Bitcoin anchor, run ots upgrade <file>.ots first — that pulls the Merkle path down from the calendar and completes the proof.
You can also verify by dragging the PDF and its .ots into opentimestamps.org — the web verifier does the same without installing anything.
What the certificate does not vouch for
This certificate covers only the byte-for-byte file commitment. It does not vouch for the content of the book, the author’s identity, or any claim made in the text. The commitment is to the artifact, not to its truth.
A book that is committed cannot be silently revised; that is the entire point. A polished version, committed later, is a different leaf.
— The Keymaker