The only signals provider that can mathematically prove it doesn't edit its track record.
Most signal channels quietly delete their losers. We can't — and we can prove it. Here's how.
The problem we refused to ignore
Independent research into 50 Telegram signal channels found 12 outright fabricating their historical results — editing losers into winners, deleting bad calls, rewriting history after the fact. In a category built on trust, trust is exactly what's missing.
We built Meridian so that editing the past is mathematically impossible to hide.
How cryptographic proof works
- At the moment a signal is published, we compute a SHA-256 hash of its immutable details — the asset, direction, exact entry zone, stop-loss, targets, and the publication timestamp.
- That hash is stored and published. It's a fingerprint of the signal as it existed the instant it went out.
- Anyone can recompute the hash from the signal's public fields and compare it to the stored one. If even a single digit was changed after publication, the hashes won't match — and the tampering is visible to everyone.
"PROOFv1:" with the canonical JSON of the signal's fields
(symbol and direction uppercased; entry_low, entry_high, stop_loss, target1, target2 and rr coerced to numbers; timeframe as a string;
published_at as an ISO 8601 timestamp), then take SHA-256 of the result. No secret key is involved — that's the whole point.
You can reproduce this in any language with the fields returned by /api/verify/:id.
Same signals, rotated lead — by design
Every member receives the same signals with the same entry, stop, and target levels. What differs is which signal leads your feed: we assign each member to a cohort and rotate the lead by cohort, so thousands of members aren't all piling into a single entry at the same instant.
This is why your feed's top signal may differ from another member's — and why every level still matches the published, cryptographically-verified record exactly. Nothing is hidden; every signal is one scroll away.
Verify a signal yourself, right now
Every closed signal on our track record has a public verification endpoint. Here's a live one:
Take the fields, apply sha256 with the PROOFv1 prefix over the canonical JSON, and confirm matches: true. That's proof the signal you see is the signal we published.