How to verify a futures 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 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 that follow climb from the quickest, cheapest check up to the one that decides it.
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 any further. With the desk pick the flagship figure is stated as 74.4% across 78 Swing Trade signals; the 78 is the part you are checking for, and the percentage is meaningless without it. This is the test set out in full on a re-runnable record.
2. Demand a continuous run
Insist on an unbroken stretch in place of a curated week. A service parading only its best five days has the other twenty-five tucked away. An honest record names its window — here, 2026 year-to-date — and leaves the rough patches inside that window on display.
3. Find the independent corroboration
Make sure a named outside party stands behind the underlying statements. A leaderboard ranking does not amount to corroboration; a happy-customer quote does not amount to a review. The externally tracked competition results live at World Cup Championships.
4. Confirm one call on-chain
Here is the step that decides it, and the one most services cannot live through. Pick one historical alert and set its published fields against its Bitcoin-anchored receipt. Since the receipt went down before the outcome was known, a match shows those fields were locked in ahead of time. A single verified call carries more weight than a hundred screenshots. What that looks like in practice:
The call below is fabricated solely to show the mechanics; it stands in for no real position. The procedure, however, is exactly what you would run on a genuine published alert.
- Pull the published call, all five of its fields. Suppose it reads: long an index contract,
entry 5,180,target 5,265,stop 5,148,grade B,signal time 13:47:00 UTC. - Rebuild the fingerprint. The desk strings those exact fields together in a set order and pushes them through SHA-256 — a one-way function that collapses any input down to one fixed-length fingerprint. Feed in the identical five fields and you get the identical fingerprint back; alter a single digit and the fingerprint comes out wholly different.
- Pull up the on-chain receipt. Published alongside the call, the OpenTimestamps receipt names the Bitcoin block the fingerprint was anchored in — the same open standard you can use to re-verify it independently. Check that the fingerprint you rebuilt is the same one the receipt carries.
- Read the clock. Find when that Bitcoin block was mined. With the block time landing before the contract settled, the call — entry, target, stop and grade as one bundle — was demonstrably set ahead of time. There is the proof, entire.
Now try to break it: say the stop got slid from 5,148 to 5,170 once the contract turned. Step 2 would now spit out a fingerprint that no longer lines up with the receipt from step 3, and the edit stands exposed. That is what puts a confirmed receipt above any screenshot — touch one field and it breaks loudly on the spot.
In sum: steps 1–3 cost a couple of minutes and weed out most of the field, while step 4 is the one nobody can counterfeit. Clear step 4 and a service has given you a record to audit rather than one to merely admire. The mechanism underneath sits on fixed before settlement. Every step is supported by the desk pick, and the published record is the thing we grade — not any claim about which markets its models trade.