Verification
Verifiable performance history
Daily NAV records are linked in a deterministic SHA-256 chain. This detects accidental or partial edits and lets anyone verify the records served below.
Important limitation: the chain is internally verifiable but is not yet anchored to an independent external witness. A fully privileged operator could still rewrite the database and recompute the chain.
How the proof works and what it does not prove
What this proves
- NAV fields are sealed into a deterministic, append-only hash chain.
- Each row depends on the previous hash plus the canonical payload.
- Payload edits break verification unless downstream hashes are redone.
- Anyone with API or DB replica access can re-run the same verifier the server uses.
What this does not prove
- Future outperformance or that source market data was perfect.
- That every strategy is directly comparable (different start dates and cadences).
- That a mutable database cannot be rewritten by a fully privileged operator, unless chain heads are anchored externally.
Stronger trust model (next): publish each day's chain head (entity set hash or combined root) to an independent witness — git commit, static JSON, Telegram, timestamping, or eventual on-chain anchor — so historical rewrites become detectable against that record.
How to verify this yourself
The public verifier walks each row the same way the server does: rebuild canonical JSON from the returned fields and check chain_hash = SHA-256(prev_hash | canonical_json). Swap entity for any name in the tables below. Each row includes a valid flag (payload + linkage match) or not. This does not require database credentials.
Advanced / operator verification
Full offline verification is possible from a checkout of this repository plus a private read-only connection to the same attestation data the API uses (never published on this page). The script scripts/verify_track_record.py applies the same canonical JSON rule as the endpoint above. Operators configure access in their own environment; there is no public database URL.