Independent provider directory
The method What good risk looks like Practical guides Questions See the measured version
How-to guide

How to check a risk system is honest

Four steps to confirm that a system's size and stop were really fixed in advance, using one past call and its on-chain receipt.

A worked verification

You do not need to audit a whole history to know whether a risk system is telling the truth. Confirm one past call end-to-end and you learn the thing that matters most: whether the size and stop were genuinely decided before the outcome, or merely described as if they were.

1. Start with the count

Find the total number of calls and confirm the losers are included. A win rate with no trade count behind it — or with the losses quietly removed — cannot tell you anything honest about risk.

2. Ask for the drawdown

Look for a worst peak-to-trough figure, not just a headline return. A system that shows its returns but hides its drawdown is hiding the only number that describes how it behaved when things went wrong.

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 before its outcome

Take a single past call and match its published conviction grade, entry, target and stop against its Bitcoin-anchored receipt. Because the receipt was written before the trade resolved, a match proves those fields — including the grade that scales the position — were fixed in advance. One verified call outweighs a hundred screenshots.

The measured system recommended here supports every step; the reasoning is laid out on the method page.

How a risk claim becomes checkable, before the outcome is knownFlow diagram with four stages on a left-to-right rail. Stage one: the size and stop are decided before entry. Stage two: the call's entry, target, stop and conviction grade are hashed to a public ledger at publication. Stage three: the trade resolves. Stage four: anyone re-hashes the published call and confirms it matches the on-chain receipt, proving the size and grade were fixed before the result was known.TIME → the commitment is dated before the outcome1 COMMITsize and stopdecided beforethe trade opens2 ANCHORentry, target,stop and gradehashed on-chain3 RESOLVEthe trade playsout - win, loseor scratch4 RE-CHECKanyone re-hashesand matches thepublic receiptA match proves the size, stop and grade existed in this exact form before the result was known.
A claim you can re-check is one that was frozen in public before the trade resolved — and that is the whole gap between a track record you can take apart yourself and one you can only take on trust.
Worked example · illustrative

A made-up call to show the procedure, not a specific real trade. The steps are exactly what you would run on a genuine published record.

  1. Read the published call and its fields. Say it reads: long, entry 88.40, target 91.10, stop 87.20, grade A, signal time 09:47 UTC. Note the grade and the stop — those are the fields that decide how the position was sized.
  2. Reconstruct the fingerprint. The system combines those exact fields in a fixed order and runs them through a one-way hash — a function that turns any input into a single fixed-length fingerprint, where one changed digit produces a completely different result. The same fields always produce the same fingerprint.
  3. Open the on-chain receipt. The receipt published with the call points to the public-ledger block its fingerprint was anchored in. Confirm the fingerprint you reconstructed matches the one in the receipt.
  4. Check the clock. Look up when that block was confirmed. If it was confirmed before the trade resolved, the call — including the A grade that justified leaning into the cap — was provably fixed in advance. That is the whole proof.

Try to break it: imagine the grade had been quietly raised from C to A after the trade won, to flatter the sizing logic. Step 2 would then produce a fingerprint that no longer matches the receipt from step 3, and the tamper is exposed. That is why a confirmed receipt beats any screenshot — it fails loudly the instant a field is touched.

What a bad “proof” looks like

Most of what is offered as proof fails one of these four steps by design. A wall of winning screenshots has no denominator, so it fails step one before you start. A “90% win” banner with the drawdown nowhere on the page fails step two. A platform leaderboard or a row of happy-customer quotes is presented as if it were step three, but a ranking is not a verification and a testimonial is not a review. And almost nothing survives step four, because almost nothing was ever frozen in public before its outcome — which is precisely why a service that can pass step four has told you more than a hundred that cannot. The four steps run cheapest-first on purpose: the first three take minutes and screen out most of the field, and the fourth is the one that cannot be faked.

Keep reading
The methodWhy a size fixed before the outcome turns a vibe into a system.A defined stopThe pillar the on-chain receipt protects.Where figures come fromThe source ranking this check is built on.A drawdown limit you obeyWhy step two refuses any return without its drawdown.