Verify this record

Every number on this site comes from a file in a public repository. Each file hashes its own content, carries the hash of the previous session, and has a third-party timestamp proving when it existed. You do not have to take any of it on trust, and you do not need our cooperation to check it.

What the proofs do and do not establish

This proves: no published number has been edited after the fact; no session has been quietly dropped; each record existed when it claims to; and every metric follows from the published equity curve by open code.
This does not prove: that the trading was skilful, that these paper fills would have happened in a real market, or that no other book exists unpublished. Git history can be rewritten by whoever controls a repository — which is exactly why the hash chain, the timestamps and branch protection are used together rather than relying on any one of them.

The four checks

  1. 1
    Each record hashes its own content

    Every snapshot carries a hash: the SHA-256 of its canonical JSON with the hash field removed. Change any published number and it stops matching.

  2. 2
    The records are chained

    Each snapshot’s prev_hash is the previous session’s hash. This is what a timestamp alone cannot give you: a timestamp proves a file existed, but says nothing about whether the series is complete. Because each session commits to the one before it, a day cannot be removed later without breaking every record after it — so publishing only the good days leaves evidence.

  3. 3
    The records were not back-dated

    Each snapshot has an OpenTimestamps proof beside it, anchored in the Bitcoin blockchain. Run ots verify <file>.ots. A fresh proof reads “pending confirmation” for a few hours until the aggregating transaction confirms — that means not yet confirmed, not invalid.

  4. 4
    The numbers follow from the inputs

    nav.csv is the whole equity curve. Every metric is computed from it by one function in the firm’s metrics module, with the risk-free rate echoed in metrics.json. Nothing is computed in your browser — this page renders numbers it was handed.

Checks 1 and 2, end to end, on a clone:

git clone https://github.com/rvbpartners-commits/rvbpartners-track-record-data.git
cd rvbpartners-track-record-data
python -c "
import json,hashlib,pathlib
prev={}
for line in open('CHAIN.jsonl',encoding='utf-8'):
    e=json.loads(line); p=pathlib.Path(e['file']); raw=p.read_bytes()
    assert hashlib.sha256(raw).hexdigest()==e['sha256'], p
    rec=json.loads(raw.decode())
    assert rec['prev_hash']==prev.get(e['book'],'0'*64), p
    prev[e['book']]=rec['hash']
print('chain ok:', {k:v[:12] for k,v in prev.items()})
"

Every published snapshot

12 records · published 13 Aug 2026, 11:25 UTC
SessionBookRecord hashChains toFiles
12 Aug 2026best_composite57421ac0f0c4…f508f0126fde…JSON·.ots·commits
11 Aug 2026best_compositef508f0126fde…da4a5e28df69…JSON·.ots·commits
08 Aug 2026best_compositeda4a5e28df69…genesisJSON·.ots·commits
12 Aug 2026best_mddeb6b442d264d…dea057a5db66…JSON·.ots·commits
11 Aug 2026best_mdddea057a5db66…4818db06f919…JSON·.ots·commits
08 Aug 2026best_mdd4818db06f919…genesisJSON·.ots·commits
12 Aug 2026best_sharpe2e27d9b43821…404247516474…JSON·.ots·commits
11 Aug 2026best_sharpe404247516474…4e2e187cc0d0…JSON·.ots·commits
08 Aug 2026best_sharpe4e2e187cc0d0…genesisJSON·.ots·commits
12 Aug 2026best_cagrfac3221524e3…e4ab5d6cae1a…JSON·.ots·commits
11 Aug 2026best_cagre4ab5d6cae1a…edc06e3bc9ac…JSON·.ots·commits
08 Aug 2026best_cagredc06e3bc9ac…genesisJSON·.ots·commits

Where everything lives

The data repository is rvbpartners-commits/rvbpartners-track-record-data. Its main branch is protected against force-push and deletion, so the append-only history cannot be rewritten without leaving a trace. Publication runs on the trading box itself — GitHub Actions is not involved in producing this data and holds no broker credential.