How to verify a Telegram signal track 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 channel is honest. Confirm one past call end-to-end and you learn most of what matters: whether the record can be checked at all, or whether you are simply trusting whatever the sender left on screen. The four steps below go from the cheapest, fastest check to the most decisive one.
1. Start with the denominator
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 scrolled away — fails before you go further. With the pick the flagship figure is stated as 74.4% across 78 signals; the 78 is the part you are checking for, and the figure is meaningless without it. This is the test set out in full on an auditable record.
2. Demand a continuous run
Look for an unbroken period rather than a curated week. A channel that only keeps its best five days visible is hiding the other twenty-five. A genuine record states its period — here, 2026 year-to-date — and does not skip the bad stretches inside it.
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 channels cannot survive. Take a single historical call and match its published entry, target, stop and grade against its Bitcoin-anchored receipt. Because the receipt was written before the outcome was known, a match proves those fields were fixed in advance — and a deleted post cannot erase the receipt. One verified call outweighs a hundred screenshots. Here is exactly what that looks like:
The call below is a made-up illustration for the walkthrough, not a specific real trade. The procedure is exactly what you would run on a genuine published call.
- Take the published call and its five fields. Say it reads: long,
entry 184.20,target 195.30,stop 179.60,grade B,signal time 09:48:12 UTC. - Reconstruct the fingerprint. The service concatenates those exact fields in a fixed order and runs them through SHA-256 — a one-way function that turns any input into a single fixed-length fingerprint. The same five fields always produce the same fingerprint; one changed digit produces a completely different one.
- Open the on-chain receipt. The OpenTimestamps receipt published with the call points to the Bitcoin block its fingerprint was anchored in. Drop the receipt into the free OpenTimestamps verifier — an independent tool, not run by the service — and confirm the fingerprint you reconstructed matches the one in the receipt.
- Check the clock. Look up when that Bitcoin block was mined — any public block explorer (for example mempool.space) will give you the block time. If it sits before the trade resolved, the call — entry, target, stop and grade together — was provably fixed in advance. That is the whole proof.
Try to break it: imagine the stop was nudged from 179.60 to 181.00 after the move 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 screenshot — it fails loudly the instant a field is touched, and the chat-app trick of silently deleting the post cannot remove the receipt that already exists.
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 channel that passes step 4 has handed you a record you can check rather than merely believe. The mechanism behind it is set out on sealed before the outcome.