How to verify a day-trading record
Four steps to confirm a single past intraday call yourself, no spreadsheet required.
You do not need to audit a whole history to know whether a service 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.
Verify in four steps
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 hidden — fails before you go further. With the desk pick the intraday figure is stated as 67.5% across 308 day-trade 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 re-runnable track record.
2. Demand a continuous run
Look for an unbroken period rather than a curated week. An intraday model that only shows its best five sessions is hiding the other forty-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 services cannot survive. Take a single historical Day Trade 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 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 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,signal time 14:32:05 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 — and OpenTimestamps is an open, third-party standard, so you verify the receipt there rather than on the desk's own say-so. 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 such as mempool.space will show you the block time independently of the desk. 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 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 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 service that passes step 4 has handed you a record you can test rather than just take on trust. The mechanism behind it is set out on locked before the close.