Independent provider directory
The method Trust tests Playbooks FAQ The verified version
Test one

Proof you can check yourself

On a trading claim, the gap between “trust me” and “check it” is a timestamp committed before the outcome.

A screenshot proves only that an image exists. It says nothing reliable about when a call was made, or whether the entry was nudged after the price went the wrong way. In crypto, where a move can happen between blocks, that ambiguity is fatal to trust — which is exactly why crypto built tools to remove it.

Anchoring a call on-chain removes the ambiguity the same way a block confirmation does. The entry, target, stop and grade are folded into a single SHA-256 fingerprint. A hash is a one-way fingerprint: change any field afterward and you get an entirely different fingerprint that no longer matches the public receipt, so a confirmed receipt proves the exact call existed in that exact form before the trade resolved. Because the grade is inside the fingerprint, a call cannot be quietly re-graded upward once it has already paid off. The flow below is the whole mechanism end to end.

How a published call becomes a claim anyone can re-checkFlow diagram: a trading call is published with its entry, target, stop and conviction grade; those fields are folded into one SHA-256 fingerprint; the fingerprint is anchored to a Bitcoin block at publication; later anyone can re-hash the published call and confirm it matches the on-chain receipt, proving the call was fixed before its outcome was known.PUBLICATION TIME → (the receipt is dated before the trade can resolve)A match proves nothing in the call was touched after the outcome was known.1 PUBLISHentry / target /stop / grade+ signal time2 FINGERPRINTone SHA-256 ofthose fields —change one, all change3 ANCHORwritten to aBitcoin blockat publication4 RE-CHECKanyone re-hashesand matches thepublic receipt
Don't-trust-verify, drawn out: the call is frozen on a public ledger the instant it is published, so it cannot be quietly re-priced once the result is in.

Walk one call through it

The mechanism is easiest to trust once you have followed a single call through it. The call below is an illustrative one, invented for the walk-through — not a specific real trade — but the procedure is exactly what you would run on a genuine published call.

Walk-through · illustrative, not a recommendation
  1. Take the published call and its fields. Say it reads: a mean-reversion long, entry 2,000, target 2,130, stop 1,920, grade B, signal time 09:14:30 UTC. No instrument is needed for the proof.
  2. Reconstruct the fingerprint. Those exact fields, in a fixed order, run through one SHA-256 pass to produce a single fixed-length fingerprint. The same fields always yield the same fingerprint; one changed digit yields a completely different one.
  3. Open the on-chain receipt. The receipt published with the call points to the Bitcoin block its fingerprint was anchored in. The receipt is an OpenTimestamps proof, so you can drop it into the public verifier at opentimestamps.org — built by neither this desk nor the operator — and confirm the fingerprint you just rebuilt matches the one it certifies.
  4. Check the clock. Look up when that block was mined — paste the block height into any public explorer such as mempool.space and read the timestamp straight off the chain. If the block time sits before the trade resolved, then entry, target, stop and grade were provably fixed in advance. That is the entire proof.
Try to break it: imagine the stop was nudged from 1,920 to 1,955 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. A confirmed receipt is worth more than any screenshot because it fails loudly the instant a field is touched.

This is the one mechanism that turns a record from a picture you are shown into a receipt you can reconstruct yourself, which is why it sits at the top of the trust tests rather than the bottom. The on-chain part is the proof standard, not a statement about the asset traded. A past call proven this way is the answer to the only question that matters about any strategy — does it actually work — because it is the part a dishonest operator cannot fake.

How do you know a strategy actually works?

Test one asks the hardest question a strategy can face: not whether it looks profitable, but whether anyone but its author can confirm it. The honest answer is never “because the chart looks good.” It is “because the record can be re-checked — by you, without trusting whoever published it.” That is the whole of the don't-trust-verify standard, pointed at a track record instead of a transaction.

The verified example this desk uses is built exactly that way. Across 2026, the #1-ranked provider's four mean-reversion models have published 690 signals at a 70% win rate for +1227% combined, every call carrying an A-to-D conviction grade. At the moment each call is published, its entry, target, stop and grade are folded into a SHA-256 fingerprint of the call's entry, target, stop, conviction grade and signal time, anchored to the Bitcoin blockchain at publication. Because the receipt is dated by a Bitcoin block written before the trade resolves, and because changing any field would break the fingerprint, a confirmed receipt proves the call existed in exactly that form before its outcome was known. The grade is inside the fingerprint too, so a call cannot be quietly re-graded upward once it has already paid off.

The on-chain anchoring is the verification method, not a statement about which instruments any model trades. To run the check on a single past call yourself, see how to verify a crypto trading strategy.

Keep reading