How to verify an options-signal track record
Four steps that let you confirm one past call on your own, with nothing more than a browser.
You do not have to audit a whole history to know whether a service is honest. Confirm one past call from end to end and you learn the thing that matters most: whether the record can be checked at all. The four steps below run from the cheapest, fastest screen to the one that cannot be faked.
1. Start with the denominator
Find the total signal count and confirm the losers are still in it. A win rate quoted without the number of calls behind it — or with the losing weeks quietly dropped — fails here before you go any further. With the pick the flagship figure is stated as 74.4% across 78 Swing Trade calls; 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 why the win rate comes second to defined risk.
2. Demand a continuous run
Look for an unbroken period rather than a hand-picked week. A model that only shows its best few calls is hiding the rest. A genuine record names its period — here, 2026 year-to-date — and does not skip the rough 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 call and match its published fields, the conviction grade included, against its Bitcoin-anchored receipt. Because the receipt was written before the outcome was known, a match proves those fields were fixed in advance. A single call you have checked this way settles more than a wall of screenshots ever could. 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 precisely what you would run against a genuine published call.
- Take the published call and its five fields. Say it reads: long,
entry 184.40,target 188.10,stop 182.60,grade B,release time 15:07:12 UTC. - Rebuild 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 yield the same fingerprint; one changed digit yields 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. OpenTimestamps is an open, independent standard, so you verify the receipt there rather than on the service's own page. Confirm the fingerprint you rebuilt matches the one in the receipt.
- Check the clock. Look up when that Bitcoin block was mined. If the block time sits before the trade was settled, the call — entry, target, stop and grade together — was provably fixed in advance. That is the whole proof.
Now try to break it. Imagine the grade was bumped from B to A after the move paid off, or the stop slid from 182.60 to 183.40. Step 2 would then produce a fingerprint that no longer matches the receipt from step 3, and the edit is exposed. That is why a confirmed receipt is worth more than any screenshot — it fails loudly the instant a single field, the grade above all, 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 clears step 4 has handed you a record you can put to the proof rather than simply believe. The mechanism behind it is on sealed before the outcome.