Independent provider directory
Benchmark

Locked before the outcome

On an algorithmic call, the gap between “trust me” and “check it” is a receipt.

All a screenshot establishes is that some image was made. It carries no reliable evidence of when a call went out, or whether the entry was quietly shifted once the market broke the wrong way. For an automated service firing off many calls, that uncertainty is lethal to trust — the more so when the same outfit is asking you to believe in an algorithm you are not allowed to see.

A cryptographic receipt closes that gap. The desk pick takes one SHA-256 fingerprint covering the entry, the target, the stop, the conviction grade and the minute of release, then pinned into a Bitcoin block by way of OpenTimestamps, recorded as the call is issued. A hash runs one way only: alter any field after the fact — entry, target, stop or grade — and the digest comes out completely different, so it stops matching the published receipt. A receipt that still checks out therefore certifies that this precise call, in this precise shape, existed before the market settled it. And because the grade is baked into that same fingerprint, a C can never be quietly promoted to an A after the trade has broken your way.

How a systematic signal is frozen before its outcomeFlow diagram: an algorithmic signal is published with its entry, target, stop and conviction grade; those fields are compressed through SHA-256; the resulting digest is pinned to a Bitcoin block as the call goes out; afterward, anyone can recompute the hash from the published call and confirm it agrees with the on-chain receipt, proving the signal was fixed before the market resolved it.PUBLICATION TIME → (before the market can resolve it)A match proves the call existed in this exact form before the outcome.1 FIREentry / targetstop / grade+ signal time2 HASHone SHA-256digest ofthose fields3 ANCHORwritten to aBitcoin blockat publication4 RE-RUNanyone re-hashes+ matches thepublic receipt
Every signal is frozen on a public ledger the instant it fires, so it cannot be re-priced once the market has moved.

Walk one call through it

Picture an illustrative signal (a made-up example for the walkthrough, not a specific real trade): a long on a liquid index ETF, entry 412.80, target 414.20, stop 412.10, grade B, signal time 14:32:05 UTC. At publication the desk runs those exact fields through the hash and anchors the digest to Bitcoin. The position resolves later that session. Weeks afterward you can take the published call, recompute the digest from those same five fields, and confirm it matches the receipt recorded against a block that was mined before the trade closed. If even the stop had been shifted from 412.10 to 412.40 after the fact, the digest would not match — and you would know.

What matters is not the figures themselves but their sequence. The Bitcoin block dates the receipt, and that date falls ahead of the result. That sequence is the whole meaning of “locked before the outcome”, and no quantity of “AI-powered” marketing stands in for it.

Where the field falls short

What a failure on this test looks like in the wild

Most automated services fail this test not through fraud but through architecture: where the call lives, nobody can pin down when it was made, and the model that made it cannot be inspected either.

  • Black-box AI bots and autotraders. With the model sealed shut you have no way to assess the reasoning, and the live history is seldom shown with its true count. In its place comes a backtest — a tidy retelling of the past assembled knowing how it ended, which nobody actually traded forward. That sinks both a stated rule and, more often than not, a re-runnable record.
  • Messaging-app channels such as Telegram or Discord. The feed belongs to whoever runs it, free to append a call after the fact, rewrite one in place or quietly delete it. So locked before the outcome is gone from the start, and the count usually goes with it, because the calls that went wrong are never left up to be tallied.
  • Social-media callers. Threads get trimmed or boosted at will, and the income tends to arrive through broker referral links, so a single caller routinely trips several tests together — locked before the outcome, a real denominator and clean incentives all at once.
  • Signal-aggregator sites. They relay calls lifted from elsewhere and check none of them, so whatever could not be verified at the source stays unverifiable here. A re-runnable record is impossible by the very way they are built.

It is the reason this desk grades a whole category rather than picking apart one product: pre-outcome on-chain timestamping happens to be the bar most of the market cannot get over, and clearing it is precisely what a buyer is paying for.

This is the mechanism that moves an algorithmic record out of the realm of things you simply take on trust and into the realm of things you can verify for yourself, which is why it sits near the top of the scorecard. To run the check yourself, see the verification primer; for what a full record must also contain, see a re-runnable record.

Keep reading
Transparent vs black boxThe receipt is only worth freezing a disclosed call, not a hidden one.A re-runnable recordThe receipt proves one call; this test proves the whole history.Verify a record yourselfThe four-step check, with the same worked example.How we rank AI trading signalsWhere this test sits among the five.