Fixed before the result
When you copy a trader, the gap between “trust me” and “check it” is a receipt.
A screenshot proves only that an image exists. It says nothing reliable about when a call was made, or whether the entry was nudged after the market went the wrong way. When the account behind it is anonymous, that ambiguity is fatal to trust — there is no one to hold to the claim.
A cryptographic receipt closes that gap. The pick folds the call's entry, target, stop, conviction grade and the minute it was sent into a fingerprint and pins it to a Bitcoin block through OpenTimestamps the instant the call leaves the desk. A fingerprint runs one way only: nudge any of those fields after the fact — the entry, the target, the stop, the grade — and the digest changes wholesale, so it stops lining up with the block that already recorded it. A receipt that still lines up is therefore proof the call read exactly that way before the market had its say. And because the conviction letter is folded into that very digest, a losing C can never be quietly rewritten as a winning A after the outcome is known.
Walk one call through it
Take an illustrative call — invented here for the walkthrough, not a real trade: long a liquid index ETF, entry 412.80, target 414.20, stop 412.10, grade B, sent 14:32:05 UTC. As the call goes out, those five values are folded into the digest and the digest is pinned to a block. The trade is done within the hour. A month on, you pull the published call, regenerate the digest from the same five values, and watch it line up with the record sitting under a block that was mined while the trade was still open. Had the stop quietly slid from 412.10 to 412.40 once the candle turned, the digest would refuse to line up — and the edit would be obvious.
What carries the proof is not the figures but their sequence. The block stamps the receipt with a time, and that time lands ahead of the result. That sequence is the whole of what “fixed before the result” buys you, and a slick profile page buys you none of it.
Who stumbles on this one, and why
Most sources fail this test not through fraud but through architecture: where the call lives, nobody can pin down when it was made or who stands behind it.
- Anonymous copy accounts. A platform may tally the leader's results, but you do not know who is behind the account, individual calls are rarely fixed in public, and conviction is never graded — so it fails fixed before the result and graded conviction even where a rough count exists.
- Influencers you mirror. Posts can be quietly removed or selectively amplified, and the money often comes from broker referral links, so a mirror-the-influencer source tends to fail nearly every test together — fixed before the result, a counted record and aligned pay at once.
- Auto-copy platform leaders. More structured than an influencer, because the platform reports the leader's equity curve — but per-call timestamps and grades are seldom there, so it fails fixed before the result and graded conviction even with a stated count.
- Tip-channel re-posters. They forward other people's calls without auditing them, so every verification gap in the original carries through unfixed. They fail a record you can re-run by inheritance.
It is the reason the desk weighs a field of source types against each other rather than profiling one account: pre-result timestamping is precisely the bar most of the field never reaches, which is what makes reaching it worth following.
This is the one mechanism that moves a follow record out of the category of things you take on someone's word and into the category of things you can check for yourself, which is why it sits at the top of the checklist rather than the bottom. To run the check yourself, see the verification playbook; for what a full record must also contain, see a counted record.