Issued before the outcome
On any trade, the gap between “trust me” and “check it” is a timestamp written before the move resolved.
A screenshot proves an image exists. It says nothing reliable about when a reversion call was made, or whether the entry was nudged after the price went the wrong way. For a strategy whose whole claim is “I caught the stretch before it closed,” that ambiguity is fatal — without proof of timing, “I called the bottom” and “I noticed the bottom afterward” look identical.
A cryptographic timestamp closes that gap. The worked example takes a one-way SHA-256 digest computed over the trade's entry, its target, its stop, its conviction grade and the clock-minute of issue, and the instant it publishes it commits that digest into a Bitcoin block via OpenTimestamps. A hash is a one-way fingerprint: change any field afterward — entry, target, stop or grade — and the fingerprint changes completely and no longer matches the public receipt. So a confirmed receipt proves the exact trade existed in that exact form before the move resolved. And since the grade is one of the fields folded into that digest, a call cannot be nudged from a C up to an A once the outcome is in.
The trade below is invented for the walkthrough, not a specific real call. The procedure is exactly what you would run on a genuine issued trade.
- Take the issued trade and its five fields. Say it reads: long a stretched index,
entry 198.40,target 201.10,stop 197.20,grade B,issued 13:48 UTC. - Rebuild the fingerprint. The model concatenates those exact fields in a fixed order and runs them through SHA-256 — a one-way function turning any input into one fixed-length fingerprint. The same fields always give the same fingerprint; one changed digit gives a completely different one.
- Open the on-chain receipt. The OpenTimestamps receipt published with the trade points to the Bitcoin block its fingerprint was anchored in. Confirm the fingerprint you rebuilt matches the one in the receipt.
- Check the clock. Look up when that block was mined. If the block time sits before the reversion played out, the trade — entry, target, stop and grade together — was provably fixed in advance. That is the entire proof.
Try to break it: imagine the stop was moved from 197.20 to 197.90 after the price dipped further. Step 2 would then produce a fingerprint that no longer matches the receipt from step 3, and the change is exposed. That is why a confirmed receipt outweighs any screenshot — it fails loudly the instant a field is touched.
What a record looks like when it cannot answer this
Most reversion records fail this test through architecture rather than fraud: of the place the call lives, nobody can pin down when it was actually made.
- Chat-room call lists (Telegram, Discord). The person posting decides what appears and when. A reversion call can be added after the bounce, edited where it stands, or deleted with no trace — so it cannot be issued before its outcome, and usually the count goes too, because the trades that failed simply never get posted.
- Mirror-trading rooms. More checkable than a chat, since a platform logs participant results — but individual calls are rarely timestamped and rarely graded, so the record still misses issued before its outcome and graded by measurement even where a rough count exists.
- Influencer callers. Posts can be quietly removed or selectively amplified, and the income often arrives through broker referral links, so a caller tends to miss almost every column at once — issued before its outcome, the full trade count and aligned revenue together.
- Bare backtest screenshots. A curve fitted to history is not a live record. It may show a count and a tidy equity line, but no one issued those trades in real time and no person owns the result, so it cannot prove the central thing — that the strategy worked forward, not just in the rear-view mirror.
This is why the site teaches a method rather than rating a single product: issued before the outcome is precisely the question most reversion records cannot answer, which is what makes a record that can answer it worth seeking out.
This single mechanism is what moves a reversion record out of the realm of things you simply believe and into the realm of things a stranger can re-derive, which is why it sits at the head of the tests. To run the check yourself, see the verification walkthrough; for what a full record must also contain, see a re-runnable record.