Independent provider directory
The method Trust tests Playbooks FAQ The verified version
Playbook

How to verify a crypto trading strategy

Four steps to confirm a strategy's record yourself, using one past call and its on-chain receipt — don't-trust-verify, in practice.

You do not need to audit a whole history to know whether a strategy is honest. Confirm one past call end-to-end and you learn the thing that matters most: whether the record can be checked at all. This is the same instinct you already apply on-chain, pointed at a track record.

The four-step check, in order

1. Start with the count

Find the total number of signals and confirm the losers are included. A win rate with no trade count behind it — or with the losses quietly removed — fails before you go further.

2. Demand a continuous run

Look for an unbroken period rather than a hand-picked good week. A strategy that only shows its best stretch is hiding the rest.

3. Find the independent check

See whether a third party has verified the underlying record. A leaderboard is not a verification, and a happy-customer quote is not a review.

4. Confirm one call against its on-chain receipt

Take a single past call and match its published entry, target, stop and grade against its Bitcoin-anchored fingerprint. 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 fourth step looks like:

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.
Worked check · illustrative, not a recommendation

The call below is invented for the walk-through. The procedure is exactly what you would run on a genuine published call.

  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.
  2. Rebuild the fingerprint. Those exact fields, in a fixed order, run through one SHA-256 pass to give a single fixed-length fingerprint. Same fields, same fingerprint; one changed digit, a completely different one.
  3. Open the receipt and match. The on-chain receipt published with the call points to the Bitcoin block the fingerprint was anchored in. Confirm the fingerprint you rebuilt matches the one in the receipt.
  4. Check the block time. If the block was mined before the trade resolved, the call was provably fixed in advance — entry, target, stop and grade together. That is the whole proof.
Try to break it: had the stop been moved from 1,920 to 1,955 after the move turned, the fingerprint in step 2 would no longer match the receipt in step 3, and the tamper would be exposed. The check fails loudly the instant a field is touched — which is why it is worth more than any screenshot.

Steps one to three take a couple of minutes and screen out most of the field; step four is the one that cannot be faked. A strategy that passes step four has handed you a record you can reconstruct rather than one you can only nod along to. The verified method recommended here supports every step; the mechanism is laid out on the method page and taken apart on proof you can check yourself.

Keep reading
Proof you can check yourselfThe timestamp mechanism step four relies on.A record with a real denominatorWhat steps one to three are really checking for.How to build a crypto trading strategyBuild the record this check is run against.FAQStraight answers on verifying a systematic record.