Verify this record

The first command copies the whole published record. The second re-hashes every file the chain lists, compares each hash with the chain’s record of it, and follows each portfolio’s prev_hash back to its first record. It needs only git and python.

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()})
"

This runs checks 1 and 2 below. A timestamp is checked with ots verify <file>.ots, and check 4 is a recomputation from nav.csv.

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. A timestamp shows that a file existed; the chain shows that the series is complete from its first record. Because each session commits to the one before it, a session cannot be removed later without breaking every record after it.

3. 3
   A record cannot have been written later than its proof

   Each snapshot has an OpenTimestamps proof beside it, anchored in the Bitcoin blockchain. Run ots verify <file>.ots. A proof establishes that the file existed no later than the block it is anchored in. The Recorded column in the table below is the chain’s own ts for each entry, the day the record joined the chain, printed beside the session it covers.

4. 4
   The numbers follow from the inputs

   nav.csv is the whole equity curve, and every metric is computed from it with standard definitions. The convention and the risk-free rate are published in metrics.json, so any figure can be recomputed independently.

The data is in rvbpartners-commits/rvbpartners-track-record-data and this site is in rvbpartners-commits/rvbpartners-track-record-site. Both are public. Their main branches carry a ruleset that requires signed commits and linear history, and blocks deletion and force-pushes. Each publish commit is signed with an SSH key and shown by GitHub as Verified. Publication runs on the firm’s trading server; GitHub holds no broker credential.