Verify a signal record
Four steps to confirm a single past call — stop included — before you trust a source with your evaluation.
Auditing an entire history is not the price of admission. Run one historical call from start to finish and you have learned the thing that counts most: whether the record — and the risk it says it committed to — is open to checking at all. The four steps run from the quickest and cheapest up to the one that settles it.
Verify in four steps
1. Start with the count
Locate the total number of signals and make sure the losing calls are in it. A win rate with no call count attached — or with the losses swept aside — is dead on arrival. With the pick the figure is stated as a 70% win rate across 690 signals; the 690 is the part you are checking for. This is the check set out in full on a counted record.
2. Demand a continuous run
Insist on a continuous stretch, not a hand-chosen week. A source flaunting only its top five days is concealing the other forty-five. An honest record names its span — 2026 to date, here — and leaves the rough patches in. Those rough patches are precisely what you must size against in an evaluation.
3. Find the independent reviewer
Confirm that a named third party has examined the underlying statements. A spot on a leaderboard is not an audit; a satisfied-customer line 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 sources cannot survive. Pull one past call and line its published fields — entry, target, stop and grade — up against the receipt anchored to Bitcoin. Since the receipt predates the result, a match witnesses that those fields, the stop included, were set beforehand. A single verified call is worth more than a hundred screenshots. This is what the procedure looks like:
The call here is a fabricated illustration for the walkthrough, not an actual trade. The procedure is identical to the one you would run against a real published call.
- Grab the published call and the five values on it. Suppose it says: long the index ETF,
entry 412.80,target 414.20,stop 412.10,grade B,sent 14:32:05 UTC. - Rebuild the fingerprint. The source joins those exact values in a set order and feeds them to SHA-256 — a one-way function that maps any input to a single fixed-length fingerprint. Identical values always yield an identical fingerprint; flip a single digit and the fingerprint is wholly different.
- Pull up the on-chain receipt. The OpenTimestamps receipt shipped with the call references the Bitcoin block its fingerprint was committed to; the receipt is verified with the free, open OpenTimestamps tooling, not against anything the desk hosts. Check that the fingerprint you rebuilt agrees with the one the receipt carries.
- Read the clock. Establish the moment that Bitcoin block was mined. If its timestamp falls before the trade closed, the call — entry, target, stop and grade as one — was demonstrably set ahead of time. That is the entire proof.
Try to defeat it: say the stop drifted from 412.10 to 412.40 after price turned — the precise slip that breaches a drawdown rule. Step 2 would now yield a fingerprint that no longer agrees with the step-3 receipt, and the edit is laid bare. That is why a matching receipt beats any screenshot — it breaks loudly the moment a field is altered.