Pre-committed risk
On a funded evaluation, the gap between “trust me” and “check it” is a stop you fixed before the trade.
An image of a trade proves the image exists and nothing else. It cannot tell you the hour the call actually went out, nor whether the stop was nudged out once price turned against the position. In an evaluation, where a single drawdown breach is terminal, that uncertainty is ruinous — loosening a stop mid-trade is the classic way a month that was on track ends in a blown account.
A cryptographic timestamp closes that uncertainty off. The pick takes a SHA-256 fingerprint of the call's entry, target, stop, conviction grade and the minute it was sent and commits the resulting fingerprint to a Bitcoin block through OpenTimestamps at the second the call leaves the desk. Hashing runs one way only: alter any field after the fact — the entry, the target, the stop, the grade — and the fingerprint changes completely and stops matching the receipt on chain. A receipt that still matches therefore witnesses that the precise call, its risk already locked, stood in that form ahead of the result. Since the stop is folded into the hash, there is no widening it once the candle has moved.
Walk one call through it
Take an invented call for the sake of the walkthrough (not a real trade): a long in a liquid index ETF, entry 412.80, target 414.20, stop 412.10, grade B, sent 14:32:05 UTC. As it goes out, the desk pushes those exact values through the hash and pins the fingerprint to Bitcoin. The position closes some time later. A month afterward you can lift the published call, regenerate the fingerprint from the identical five values, and watch it line up with the receipt logged against a block dug before the position closed. Had the stop crept from 412.10 to 412.40 once the trade was live — the very slip that silently busts a drawdown limit — the fingerprint would diverge, and the change would be exposed.
What a miss looks like in the wild
For most sources the failure is architectural rather than dishonest: given where the call is stored, no one can establish when it appeared or what stop it carried.
- Messaging-app channels (Telegram, Discord). Whoever runs the channel controls the timeline. An alert can be dropped in after the move has already happened, quietly reworded, or wiped entirely, so the stop was never nailed down anywhere public — that breaks pre-committed risk straight away, and usually the counted record alongside it, because the calls that went wrong are simply not there to count.
- Copy-trading rooms. A notch more transparent than a chat, since the platform keeps tallies of how participants did — but individual calls almost never carry a per-signal timestamp or a grade, so even with a rough tally they miss pre-committed risk and a per-clock grade.
- Social-media callers. A post can be quietly removed or selectively amplified, and the income frequently flows from broker referral links, so a lone caller usually trips most of what an evaluation cares about in one go — pre-committed risk, a counted record and a named operator.
- Signal-aggregator sites. These rebroadcast calls lifted from elsewhere without checking any of them, so whatever was unverifiable in the source travels downstream untouched. They miss a counted record purely by passing the problem along.
It is the reason this guide grades a category instead of writing up a single product: pinning the stop before the outcome happens to be the habit the bulk of the market is structurally unable to demonstrate, which is precisely what makes a source that can demonstrate it worth paying for once an evaluation is on the line.
This is the one mechanism that turns a record from something you admire into something you can audit, which is why it sits at the top of the checklist. To run the check yourself, see the verification walkthrough; for what a full record must also contain, see a counted record.