Glossary

Track Record Portability — What Moves With a Trader, What Stays Behind

Portability is the property of a track record that lets it survive a change of platform, broker, or employer. The label is meaningful only when the underlying primary records can travel with the trader.

By NakedPnL Research·May 9, 2026·5 min read

TL;DR

Track record portability is the property of a performance history that lets a trader carry the verifiable record across platform, broker, or employer changes.
A track record is portable when the trader controls the underlying primary data — typically through direct ownership of the venue account.
Prop firm history, exchange leaderboard rankings, and most operator-rendered surfaces are not portable: the legal account, the API access, and the historical database all live with the operator.

Definition

Track record portability is the degree to which a trader can carry a verifiable performance history across a change of platform, broker, employer, or operator without losing the ability to prove the figures from primary records. A portable track record stays third-party-verifiable even after the trader has stopped using the original infrastructure. A non-portable record either survives only as screenshots and reputation, or disappears entirely when the underlying operator chooses to stop cooperating.

What makes a record portable

Trader-owned venue account — the brokerage or exchange account is in the trader's name, so historical statements name the trader as the legal counterparty.
Trader-controlled API access — read-only credentials remain valid regardless of operator goodwill, allowing fresh verification at any future date.
External archival surface — at least one independent record of the chain history exists outside the original operator's database, ideally with an external timestamp anchor.
Documented methodology — the calculation that produced the headline figure is openly published so any future reviewer can re-derive the number from the same primary data.

What makes a record non-portable

Prop firm accounts. The legal account is in the firm's name; only the firm can grant API access; the firm controls the historical database. The methodology guide on prop firm track record portability covers the structural limits in detail.
Exchange-rendered leaderboards. The data lives in the exchange's private database; the operator decides what is visible; there is no external archive a trader can carry to a new venue.
Hosted-platform copy-trading lead pages. The platform is both the venue and the publisher; departure means losing the published profile.
Influencer-tracker profiles run by third parties. The operator chooses what to retain and what to delete; a trader who falls out of favour can lose the visible record overnight.

Why portability matters for due diligence

Outside readers — allocators, fund-of-funds analysts, hiring committees, regulators — increasingly want to confirm that a trader's record exists in a form that does not depend on the trader's good standing with a single operator. A history that disappears the moment a relationship sours is a weak verification surface. A history that is anchored to an independent external surface (a programmatically verified registry, an open-protocol timestamp, a regulator-mandated retention) survives the relationship and gives the reader something durable to inspect.

How NakedPnL implements portability

A NakedPnL profile is structurally portable by design. The underlying venue accounts (Binance, Bybit, OKX, IBKR, Kalshi, Polymarket) are in the trader's name; only the trader can grant or revoke read-only API access. Every NavSnapshot row is hashed with SHA-256 and chained to the previous day; the daily Merkle root of all chain heads is committed to Bitcoin via OpenTimestamps. The chain bundle is exposed at /verify/chain/[handle] and recomputable in the browser using the Web Crypto API, so even if NakedPnL itself disappeared tomorrow, any third party who saved an earlier chain head and the bundle of NAV rows could re-derive the published figures from primary venue records.

Verified track record — the four properties that make a track record stand up to outside review.
Hash chain — the data structure that makes the historical record append-only and re-verifiable.
OpenTimestamps — the Bitcoin anchor that lets a third party confirm a record was published before a given block height.
Track record verification — the procedure for confirming a stated figure matches the primary records that produced it.

Frequently asked questions

Is a prop firm track record fully non-portable?

Partially portable. Firm-issued sealed PDF statements, MT4/MT5 history exports, and bank or stablecoin payout records all travel with the trader. What does not travel is the live API access to the underlying account or an independently-controlled append-only chain. The composite of firm-issued artefacts plus a parallel personally-held account on a verifiable registry is the strongest combined story most prop traders can produce.

Can a screenshot of a great month make a record portable?

No. A screenshot is a moment-in-time projection of an operator-rendered dashboard. It is trivially edited, has no append-only chain behind it, and cannot be re-derived from primary records by anyone other than the operator. Portability requires an underlying primary-data surface the trader controls.

Does portability require trader-side custody?

Custody and account ownership are separate questions. A trader on a non-custodial exchange and a trader at a custodial regulated broker can both have portable records, as long as the legal account is in the trader's name and the trader controls the API access used for verification. The portability question is about who controls the verification surface, not about who holds the assets.

What happens to portability if NakedPnL itself goes offline?

The chain bundle is exportable, the verification algorithm is open, and the OpenTimestamps anchors are stored on Bitcoin. A trader who has saved their chain bundle and the relevant OTS proofs can prove their historical record from the saved data alone, without NakedPnL participating in the verification.

Is GIPS verification a portable artefact?

A GIPS verification report is a portable document — the report itself is portable — but it represents a snapshot opinion, not a re-runnable computation. A reader who wants to confirm the underlying data still requires access to the original composite records. Portability of the report is necessary but not sufficient for portability of the verification surface.

References