What Makes a Trading Track Record Actually Verified?

The word does almost no work

"Verified" appears on signal-seller landing pages, prop-firm certificates, copy-trading profiles and Discord bios. In nearly every case it means one of three things: someone uploaded a screenshot, someone connected a read-only broker key, or someone is simply asserting it. None of those establish the thing a reader actually wants to know.

The question behind "is this track record real" is never "did these trades happen". It is "did this person know which trades to show me before they knew how they turned out". That is a question about timing, not about data authenticity, and almost no verification scheme addresses it.

Four tiers of proof

Tier	What it proves	How it fails
Screenshot	Nothing	Trivially edited; shows one position out of any number
Equity curve	A shape existed	No trade detail; start date chosen after the fact
Broker import	The trades executed	Selection: which account, which period, which trades get imported
Pre-committed record	The trades were called before the fact	Only if the record is append-only and independently checkable

The jump that matters is from the third row to the fourth. Broker import is a genuine improvement over a screenshot — the fills are real. But the trader still chooses which account to connect, when to start, and when to stop. A record assembled from data you control, after you know the results, is a curated selection no matter how authentic each individual row is.

Survivorship is the mechanism, not dishonesty

This does not require anyone to lie. Run three accounts and connect the best one. Start the verified period after a bad quarter. Trade for six months, discover the results are poor, and simply never publish. Every individual number is true and the aggregate is meaningless — and the trader frequently believes it themselves, because the discarded attempts genuinely do feel like "not really my strategy".

Sealing a commit before the fact answers this one record at a time: nothing inside a sealed capsule was chosen with the result already in hand. On its own it does not answer the account-level version of the same trick. Someone can run a hundred entirely honest sealed accounts and show you the one that worked.

What stops someone running a hundred accounts?

Not cryptography — a name. You stake your name. A kappi record is published under a handle, and the handle is the thing that gets shared: you give someone your @name, or a badge that links to it, and that is the proof. So an account is worth exactly what the name on it is worth.

Which is why the recommended handle is the one you already answer to in public — the same @name as your Instagram, your X, your Discord. Sign-up says it plainly: reuse one that identifies you to the public already. Your @name is your bond. A reader who recognises the handle is reading a record kept by someone they can already find.

That is what makes the hundred-account strategy defeat itself. A public identity does not fork. @yourhandle1 through @yourhandle100 announces what it is doing, in the name, to every single person shown one of them. And a fresh anonymous handle carries only what its own sealed history carries, which on a new account is nothing at all. Neither buys what one continuous name buys, and the only way to hold a name worth showing is to keep it through the losing stretches as well.

The seal is what makes each record honest. The name is what makes the set of them honest. Neither works alone, which is why kappi asks for both.

What a verifiable record requires

• Recorded before the fact. The commitment is made while the result is genuinely unknown.
• Immutable after the fact. Nothing can be edited, backdated or quietly removed once the result arrives.
• Complete. Every trade, including the ones the trader would rather forget. A record with a delete button is a highlight reel.
• Independently checkable. A reader can confirm the above without trusting the platform's word for it.

That last point is the one most services skip. "Trust us, we verified it" relocates the trust problem rather than solving it — now you have to trust the verifier's incentives, and the verifier is usually paid by the trader.

How kappi does it

Broker-import journals prove what you did after the fact, from data you control. kappi timestamps what you said you would do, before you knew how it would turn out, on a record you cannot edit.

Mechanically: a trade is committed from the kappi Chrome extension before the fact. The commit is timestamped and sealed for a time-capsuled delay, so it cannot be read while it would still be actionable. When the delay expires it becomes public on the trader's profile. Every sealed commit is hashed into a Merkle tree anchored to Hedera, so the log is append-only and a reader can check that nothing was inserted or altered after the fact — without taking kappi's word for it.

The public profile carries PnL, RME, correlation to SPX, mean R:R and trade count over 30, 100 and 200-day windows. Those are computed from the sealed commits, not from anything typed in afterwards.

What this cannot do

It cannot make a trader good, and it does not predict future results. A verified record of poor performance is still a record of poor performance — arguably that is the feature, since a system that only produces flattering records is not a verification system.

On its own it also cannot stop someone running several kappi accounts and publicising the best one — that is what the handle is for, and a handle is a deterrent rather than an enforcement. kappi does not verify that you are who your @name says you are; it makes a forked identity visible to every reader you show it to, which is a different and weaker thing than proof, and worth saying so. What the seal changes regardless is that each individual record is complete and unedited, so the claim being made is at least a real one.

What does a real performance standard require?

Worth knowing that one already exists, for less personal use. The CFA Institute's Global Investment Performance Standards are voluntary ethical standards for calculating and presenting investment performance, resting on two principles: fair representation and full disclosure. Performance is reported across composites — every portfolio run to a strategy — rather than the accounts that worked.^[1]

The timing half has an equally old answer. Haber and Stornetta set out in 1991 how to time-stamp a digital document so that the timestamp cannot be forged even by the service issuing it, by hashing documents and linking the hashes.^[2] Between them, those two ideas describe the whole of what a verified record needs: completeness by construction, and a time nobody can move.

kappi is a trade recorder: you commit a trade before the fact, it is sealed on your device for a time-capsuled delay you choose, and published afterwards on a Merkle-anchored log a reader can check without kappi's cooperation. $15/month, no free tier.