How to verify a signal record
Four steps to confirm a single past call yourself, no spreadsheet required.
You do not need to audit a whole history to know whether a source is honest. Confirm one past call end to end and you learn most of what matters: whether the record can be checked at all. The four steps below go from the cheapest, fastest check to the most decisive one — and they are exactly what the free education trains you to run.
Verify in four steps
1. Start with the count
Find the total signal count and confirm the losers are included. A win rate quoted without the number of calls behind it — or with the losses hidden — fails before you go further. With the pick the figure is stated as 67.5% across 308 signals; the 308 is the part you are checking for, and the figure is meaningless without it. This is the test set out in full on a record you can re-check.
2. Demand a continuous run
Insist on an unbroken stretch, not a flattering week. When a source parades five glorious sessions, ask about the forty-five it skipped over. An honest history pins down its window — 2026 year-to-date, in this case — and leaves the rough patches inside that window where they fell.
3. Find the independent reviewer
Check that a named outside party has reviewed the underlying statements. A leaderboard ranking is not an audit; a happy-customer quote is not a review. The externally tracked competition results sit at World Cup Championships.
4. Confirm one call on-chain
This is the decisive step, and the one most free sources cannot survive. Take a single historical alert and match its published fields against its Bitcoin-anchored receipt. Because the receipt was written before the trade resolved, a match proves those fields were fixed in advance. One verified call outweighs a hundred free screenshots. Here is exactly what that looks like:
Treat the call beneath as invented purely to demonstrate the steps; it is not a real trade anyone took. What is real is the procedure — run it exactly this way on an actual published alert.
- Take the published call and its five fields. Say it reads: long the index ETF,
entry 412.80,target 414.20,stop 412.10,grade B,sent 14:32:05 UTC. - Rebuild the fingerprint. Glue those five fields together in the order the desk specifies and pass the string through SHA-256. The useful property is determinism plus sensitivity: feed in the identical fields and you always land on the identical fingerprint, but alter a single character anywhere and the output scrambles into something unrecognisable.
- Open the on-chain receipt. The OpenTimestamps receipt published with the call points to the Bitcoin block its fingerprint was anchored in; OpenTimestamps is an independent, open-source project, so you are checking the proof at a third party rather than taking the desk's word for it. Confirm the fingerprint you rebuilt matches the one in the receipt.
- Check the clock. Find out when that Bitcoin block was actually mined. Should the block's timestamp land ahead of the moment the trade closed, then the call in full — entry, target, stop, grade and all — demonstrably predated its own result. There is the proof, start to finish.
Try to break it: imagine the stop was nudged from 412.10 to 412.40 after the candle turned. Step 2 would then produce a fingerprint that no longer matches the receipt from step 3, and the tamper is exposed. That is why a confirmed receipt is worth more than any free screenshot — it fails loudly the instant a field is touched.
Net: steps 1–3 take a couple of minutes and screen out most of the field; step 4 is the one that cannot be faked. A source that passes step 4 has handed you a record you can audit instead of admire. The mechanism behind it is set out on locked before the outcome.