The ledger. Every call I record goes into an append-only log.
Each entry carries the fingerprint of the one before, and the latest fingerprint is timestamped in Bitcoin, so a later rewrite shows up against any timestamp already made.
How it works
- 1
Recorded
When I save a call, a program adds an entry with its terms, usually within minutes. The entry price is the first daily close after that day, so it can’t be picked with hindsight.
- 2
Chained
Each entry contains the SHA-256 fingerprint of the one before. Changing or removing a past entry means recomputing every fingerprint after it, and the new ones won’t match those already timestamped in Bitcoin.
- 3
Timestamped
The latest fingerprint is anchored in the Bitcoin blockchain through OpenTimestamps, which proves the ledger existed in that state no later than the Bitcoin block that confirms it.
What it can’t show: a timestamp covers only the entries written before it, so the newest entries are covered once their Bitcoin block confirms, usually within a day. The checks on this page compare the files on this site with each other. A rewrite that also replaces the anchor files is caught only against proofs saved elsewhere, so keep copies of the .ots files. The tracker refuses to add to a ledger that doesn’t verify, and the site won’t build from one.
Check it yourself. Your browser downloads the ledger, recomputes every fingerprint and checks each one against the anchor files. Check the Bitcoin proofs themselves with the files below.
Bitcoin timestamps Each anchor file holds the ledger’s fingerprint at that moment, and its .ots proof ties that file to a Bitcoin block.
To check one independently, download both files and drop them on opentimestamps.org, or run ots verify on the proof.
| Date | Covers | Ledger fingerprint | Status | Files |
|---|---|---|---|---|
| Oct 4, 2026 | Entries 0 to 2 | 33c73b88b94e64d599c6… | Confirmed in Bitcoin block 969893 Anchor file Proof (.ots) | Anchor file Proof (.ots) |
| Oct 4, 2026 | Entries 0 to 1 | 7f7ad11ee5e74ef4efe4… | Confirmed in Bitcoin block 969890 Anchor file Proof (.ots) | Anchor file Proof (.ots) |
| Oct 4, 2026 | Entry 0 | 61d6d2cf15d391110796… | Confirmed in Bitcoin block 969809 Anchor file Proof (.ots) | Anchor file Proof (.ots) |
Entries 3 entries, newest first. Times are when the tracker wrote them.
| # | Written | Event | Call | Fingerprint |
|---|---|---|---|---|
| 2 | Oct 4, 2026, 19:41 UTC | Rules recorded | — | 33c73b88b94e64d599c6… |
| 1 | Oct 4, 2026, 19:06 UTC | Rules recorded | — | 7f7ad11ee5e74ef4efe4… |
| 0 | Oct 4, 2026, 05:14 UTC | Ledger started | — | 61d6d2cf15d391110796… |
The rules, as recorded Version 3
The whole rules file, including the code that applies these rules, is fingerprinted in the ledger, so any change to it leaves a public entry. Current fingerprint 5b2b8aab70706db0757d…, recorded in entry 2.
- 1
A call counts from the day the tracker records it in the ledger. No close dated on or before that day is used for its entry, stop, target or exit. A call dated in the future is not recorded.
- 2
Entry: for "next close" calls, the first daily close after the call was recorded. For "fixed" calls, the level written in the call, filled at that level on the first daily close after recording that is at or better than it. A fixed call that never fills closes at its horizon with no result.
- 3
Every call needs a stop. When it is recorded, its target and stop must sit on either side of its fixed entry level or, for a next-close call, of the latest close.
- 4
Only daily closes count. Intraday highs and lows are ignored.
- 5
Each daily close is checked in order, starting with the close that fills the entry: at or beyond the stop closes the call as "stopped out"; at or beyond the target closes it as "hit target"; reaching the horizon, counted from the day the call was recorded, closes it as "expired". The exit level is that day's close, not the target or stop, so a call whose entry close is already at or beyond its stop or target closes on that same close, with a zero result for a next-close call.
- 6
A call I close early, or delete while it is open, is closed at the first daily close after the request.
- 7
Price calls are scored as the percentage move in the direction of the call, plus carry accrued at the stated annual rate for the days held. Yield calls are scored in basis points; long means long the bond, which gains when the yield falls.
- 8
R is the result divided by the distance from entry to the stop recorded with the call, in the same units.
- 9
Open calls are marked to the latest daily close dated before the day the tracker runs.
- 10
A call stays in the ledger even if it is deleted from the site. Once it is recorded, its opened date, price source, ticker, quote (price or yield), direction, entry, carry and confidence cannot change. Changes to its target, stop or horizon are logged as amendments, must pass the check in rule 3 against the latest close, and apply only from the next close; a horizon that has already passed is refused. Renaming it (title or instrument) is logged as an amendment too.
- 11
Calls on markets without a free daily price are marked and closed by hand. They are labelled self-reported and kept out of the headline figures.
- 12
These are paper positions, not investment advice.