Track Record Verification — Definition, the Verification Surface, and What Reviewers Actually Check
Track record verification is the act of confirming that a stated performance history matches an independent primary record. Definition, the steps a reviewer takes, and how cryptographic chaining changes the surface.
- Track record verification is the act of confirming a stated performance history against an independent primary record.
- A reviewer typically checks four things: source independence, methodology, completeness of the period, and reproducibility of the figure.
- Cryptographic chaining adds a fifth: a tamper-evident timeline that prevents later editing of past entries.
- Verification can be done by a human reviewer reading statements, by an algorithm re-computing the figure, or by both.
Definition
Track record verification is the act of confirming that a trader's stated performance history matches the independent primary record from which it was derived. It is a procedural concept rather than a metric: the question is not 'what did the manager earn?' but 'can a third party re-derive the stated figure from primary records, in full, without the trader's intermediation?'.
What a reviewer actually checks
- Source independence — Are the underlying records produced by the venue or broker, or only by the trader?
- Methodology — Is the calculation method documented and appropriate (typically time-weighted return per GIPS for manager skill)?
- Completeness — Does the record cover the full claimed period without gaps or missing accounts?
- Reproducibility — Can the reviewer rerun the calculation on the primary data and get the same figure?
- Timeline integrity — Is there evidence that historical entries were not edited after publication?
How verification has historically been done
In traditional asset management, verification is procedural and largely manual. An independent CPA firm conducts a GIPS verification engagement, examining the firm's policies, sampling composites, recomputing returns, and issuing a verification report. The process is rigorous but expensive — typically tens of thousands of dollars per engagement — and the report is a static document; once issued, it is not re-runnable by an outside party.
Hedge funds and managed accounts use a different procedural verification: the fund administrator performs daily NAV reconciliation against prime-broker records, and an annual external auditor opines on the financial statements. Again, the verification is procedural and document-based; an outside party reviewing the manager's pitch deck a year later relies on the auditor's reputation rather than re-running the calculation themselves.
How cryptographic chaining changes the surface
A SHA-256 hash chain over canonicalised primary records, anchored to Bitcoin, transforms verification from a one-time procedural document into a re-runnable computation. A reviewer who has the chain bundle, the published methodology, and a SHA-256 implementation can re-derive every NAV row, the chain head, and the resulting TWR figure entirely on their own machine. The OpenTimestamps anchor lets the same reviewer confirm that the chain head existed on a particular date by checking a Bitcoin block — without any cooperation from the trader, the venue, or the registry operator.
This does not replace the human-reviewer model; it complements it. A GIPS verification engagement still answers questions about firm-level policies and definitions. A cryptographically chained registry answers a narrower but easier-to-automate question: did the published figure on date X match the primary records that existed on date X? The verification methodology guide on independent third-party verification documents the full re-derivation procedure for NakedPnL.
What verification cannot prove
Verification confirms that a stated number matches its primary source. It does not prove the trader will continue to perform the same way, that the primary source itself is honest, or that the trader has not selectively disclosed only flattering accounts. A trader who connects two of their five accounts has a verified record for the connected two — and a strategically curated portfolio. Verification reduces specific failure modes; it does not eliminate the broader category of disclosure choices the trader makes.
Related terms
- Verified track record — the artefact produced by track record verification.
- Hash chain — the data structure that supports re-runnable verification.
- OpenTimestamps — the protocol that anchors a chain head to Bitcoin.
- GIPS standards — the institutional framework for verifying fund performance reporting.