Test

Telegram timestamps: covered bytes and timing bounds

In a chat app, the gap between “trust me” and “check it” is a timestamp the sender does not control.

How the seal works

A screenshot proves only that an image exists. A pinned post proves only what the channel wants pinned today. Neither says anything reliable about when a call was made, or whether the entry was nudged — or the whole post deleted — after the trade went the wrong way. In a medium where the sender owns the record, that ambiguity is the entire problem.

A timestamp can establish the existence of a digest by a verified attestation time, not the truth of every field in a chat post. The documented VR2 input is SHA-256 of the documented VR2 preimage: salt, family, ticker, direction, grade, entry and signal time. Recompute the SHA-256 digest, then check the OpenTimestamps proof. Submission at publication may still be pending; only a confirmed Bitcoin attestation supplies an independently checkable block time. The target and stop are not in VR2, so a matching digest cannot show whether either was edited. Delivery, fills and outcomes need their own records.

What a VR2 receipt can and cannot establishFlow diagram: preserve the full published call; hash the documented VR2 preimage containing salt, family, ticker, direction, grade, entry and signal time; submit its digest to OpenTimestamps; then verify the Bitcoin attestation and compare its time with the outcome. Target and stop are outside the VR2 preimage.MESSAGE → VR2 DIGEST → TIMESTAMP PROOFA verified receipt covers the hashed VR2 fields, not target, stop, delivery or returns.1 ARCHIVEsave originalmessage anddelivery time2 HASHVR2 fields onlyentry + grade+ signal time3 SUBMITsend digest toOpenTimestampsretain .ots file4 VERIFYcheck confirmedblock time andrecompute hash
A submitted proof may still be pending. Compare the confirmed attestation time with the outcome, and audit the un-hashed target and stop separately.

Walk one call through it

For a hypothetical long call with entry 184.20, target 195.30, stop 179.60, grade B and signal time 09:48:12 UTC, first save the original message. To test a claimed VR2 receipt, request its salt, family, ticker, direction and exact serialization along with the entry, grade and time. Recompute the digest and verify the .ots file. Compare the confirmed attestation time with the outcome. The illustrative target and stop remain outside the VR2 digest; check their message history separately, including any revisions.

The numbers are a teaching example, not a historical trade. A valid timestamp checks the covered bytes by the attested time; it does not validate a stop, target, fill or profit.

Where the field falls short

Where a record can lose context

Most chat-app channels fail this test not through outright fraud but through architecture: where the call lives, nobody can pin down when it was made.

  • Telegram and chat channels. Export a dated window of original messages. Preserve edits, deletions and cancellations; then compare the channel history with messages actually received by a subscriber.
  • Copy-trading rooms. Compare source and follower ledgers, including rejected orders, lag, sizing and fees. The platform's source performance is not automatically a follower result.
  • Social-media callers. Preserve first-version posts and identify any broker or exchange compensation. Sample a continuous period instead of relying on selected screenshots.
  • Signal-aggregator sites. Keep both the source call and the forwarded message. Check whether a changed entry, missing stop or forwarding delay altered what a subscriber saw.

Apply the pre-outcome timestamping test to a named service and a defined sample. The app or channel type alone is not a pass or fail.

This is the one mechanism that turns a chat-app record from something you scroll into something you can audit, which is why it sits at the top of the scorecard rather than the bottom. To run the check yourself, see the verification walkthrough; for what a full record must also contain, see an auditable record.

Related

Three completed classroom timing interpretations

Packet A has retained bytes and a pending proof: independent bound unresolved. Packet B has a matching completed proof whose bound follows the claimed outcome: existence by that later bound, not pre-outcome evidence. Packet C has an earlier completed bound matching different bytes: mismatch retained. The three packets should not receive one identical verified badge.

Even a matching earlier bound concerns only the exact covered payload. It cannot establish unseen messages, stop or target fields outside that payload, subscriber display or broker acceptance. Another committed version can coexist with the first. A useful review states what matched, the bound it establishes and the remaining source-to-account questions.