Guide

How to verify a Telegram signal track record

A buyer's audit of channel history, delivery delay, fills and timestamp receipts.

A convincing Telegram feed is not yet a track record. Build your own observation log during a trial, then compare it with the provider's reported history. A single valid receipt tests one message; a complete performance claim also needs every call, including ignored, edited, cancelled and losing calls.

1. Define the period and denominator

Choose the trial dates before reading the results. Count every new actionable call in that interval, not just the ones a channel later labels completed. Keep separate totals for closed trades, still-open trades, cancelled calls, and calls you could not fill. If a provider quotes a win rate, ask for the closed-trade numerator and denominator, its treatment of open positions, and the full date range. The record criterion explains why a percentage without that inventory is weak evidence.

2. Capture the original feed

Save the channel identity, original message link or ID, UTC post time, complete text and any visible edit marker. Export the chat during the trial, not only after it ends. Telegram Desktop can export a chat as JSON or HTML; a later export alone cannot reconstruct a message that was deleted before you saved it. Keep sequential exports or an independent contemporaneous log.

3. Test subscriber execution

Record when the alert reached your device and the first price available at your broker or exchange after receipt. These are not necessarily the channel post time or the advertised entry. Note spread, fees, slippage, market hours, order type and whether the quoted entry was ever reachable. Do not score an unfilled limit order as a win or loss. A provider's model return and your achievable subscriber return are different measurements.

4. Inspect outside evidence

Request the original source record, the independent reviewer's report where an audit is claimed, and a receipt for one representative call. A competition result measures that competition entry; it does not independently audit a separate channel or model. For a cryptographic receipt, verify the actual hashed fields, the input encoding and the resulting digest. An OpenTimestamps proof can show that a digest existed by a verified attestation time, but it cannot establish profitability, a timely subscriber notification or completeness of the feed.

Worked example · illustrative

This is a fictional audit exercise, not a real provider result or an independently verified trade.

  1. Inventory the calls. Suppose a channel posts three calls during your observation window. One closes profitably, one closes at a loss and one limit entry is never reached. The third is still part of the published-call denominator, but not a completed trade.
  2. Compare clocks. For the first call, the channel post says 09:48 UTC, your notification arrived at 09:49, and the first tradable quote was outside the advertised entry range. That call may be a model win but not an executable subscriber win at the stated price.
  3. Recreate the digest. For a claimed VR2 receipt, the documented preimage is VR2|salt|family|ticker|direction|grade|entry|signal_time. Ask for the exact field values, salt and serialization rules, then calculate SHA-256 independently. The target and stop are not in that documented preimage. A matching VR2 hash alone cannot prove those two fields were unchanged.
  4. Verify the receipt. Check that the recomputed digest matches the submitted file and that its .ots proof has a verified Bitcoin attestation before the outcome being tested. A pending attestation is not the same as a verified block time. Even a valid proof covers only the hashed payload, not an entire channel history.

In this example, the fair summary is two closed calls with one winner, plus one unfilled call and one potentially unreachable subscriber entry. There is not enough information to calculate a net subscriber return. Keep those unknowns visible instead of converting them into a polished win-rate banner.

A useful trial ends with a call inventory, an execution log and an evidence column for each claim. Keep missing receipts, unavailable quotes and edits marked as unknown or disputed. A verified digest is helpful evidence for its specific fields, not a substitute for the full record. See the timestamping criterion for the separate cryptographic test.

Related
Channel preservation test

Preserve the channel before judging it

Telegram channel owners can edit and delete posts. An archive downloaded next month only shows what remains then, not necessarily what was visible when a trade was called. For a trial, save the channel history regularly and keep the notification that actually reached your device. This is a reader-side evidence log, not an audit of the provider.

Record three clocks

For each proposed trade, distinguish the time on the original channel post, the time your device received it, and the first price available at your venue after receipt. A forwarded post may preserve text but is not the original source; a pinned message may be easier to find but is not proof it existed before the move. Keep the original channel identity, message link where available, and any visible edit marker with your copy.

Reconcile the whole sequence

At the end of each session, compare new messages with the previous export or notes. Mark disappeared calls, corrected entries, moved stops and late follow-ups as separate events. Do not silently score a corrected message using the original timestamp. Include quiet days in your observation period, because a short burst of successful calls is not a continuous record.

Keep the receipt in its lane

A matching external timestamp may establish that its hashed fields existed no later than a verified attestation time. It does not establish that every channel call was included, that your phone received the message on time, or that your exchange could fill it. Ask for the exact field order and formatting used to create the hash; without them, a reader cannot independently reproduce the claimed fingerprint. A sample receipt checks one payload, while a full track-record claim needs a complete archive.

Telegram documents chat export and channel editing and deletion. The SEC social-media stock-tip alert is a separate reminder to verify who is making an investment claim.

Complete a discrepancy rather than just request records

A fictional summary says ten completed wins. The retained inventory has four positive, two negative, one zero, one cancelled and two unresolved families. Seven are resolved under this stated method; four of seven are positive. The review preserves the summary, exact population and differing outcome rule instead of silently changing the source claim.

This packet does not prove the complete expected population when the original access boundary is unavailable. Its conclusion is a discrepancy within the represented sample, not an outside audit of a named service. Keep the original screenshots, message versions and calculation together so a later reviewer can investigate period or definition differences.