Public audit
At month-end we publish a canonical CSV of every tip we sent — wins, losses, walked tips, no exclusions. We hash it with SHA-256 and anchor that hash on the Bitcoin blockchain via OpenTimestamps. Anyone with the CSV and the proof file can verify independently that we haven't edited the record.
This is the technical underpinning of the “we don't edit our losers” promise. It costs nothing to verify. That's the point.
The April 2026 tip ledger is sealed and ready to anchor on Bitcoin via OpenTimestamps. The proof file plus SHA-256 hash will appear here as soon as the calendar submission upgrades — typically within a day. Subsequent months will anchor on the first of the following month going forward. Until then the full tip record is on the results page.
How to verify
No part of this requires trusting us. Every tool is open source; every number is independently checkable.
The canonical CSV (every tip in that month) and its .ots proof file.
Run shasum -a 256 tips.csv. The output should match the SHA-256 string on the audit page exactly. A single byte differing means the record was edited.
Drag the .ots file into opentimestamps.org, or run ots verify tips.csv.ots from the CLI. It returns the Bitcoin block height that anchored the hash.
Why this matters. If we ever quietly edited a past month's CSV — to bury a bad pick, restate an outcome, anything — the new hash wouldn't match the one anchored on Bitcoin. The discrepancy would be permanent and visible to anyone who cared to check. Most tipsters operate on trust. We operate on cryptography.