Proof for 2026-10-17

The chain of days

Each day has its own root. Walk the days one at a time; nothing hides between two roots you can read.

Revisions of this day

If a day’s records are recommitted, the earlier commitment stays published. Every revision below can be checked with --rev.

Check it yourself

1. Download verify.mjs (one file, no dependencies, Node 18+) and run node verify.mjs 2026-10-17. It fetches proof/2026-10-17.r1.json and proof/index.json, then recomputes everything on your machine.
2. It re-hashes every published record, rebuilds the Merkle tree from all 300 leaf hashes, and confirms it equals 501f52facb59aafe…d7e134c562. Any single changed record changes the root.
3. Prefer a browser? The Proof Ledger page checks any entry in your tab.
4. There is no on-chain anchor for this root yet, so the check above proves the file is self-consistent and unchanged since you downloaded it. It cannot prove when we committed it.

A commitment shows that a record existed in exactly this form when the commitment was made. It says nothing about whether a call turned out to be right.

Records published for this day

112 of 300 records are published in full. 188 copy-trading leaves are published as fingerprints only: they are inside the root, and their content is withheld.