Stock timestamps: covered bytes and timing
On a stock call, the whole distance between “trust me” and “check it” is a timestamp.
A screenshot can preserve a useful representation, but by itself does not authenticate the original instruction, covered fields or publication time. An editable record can still be investigated through independent version and delivery records. The question is which evidence survives, not whether the interface format automatically makes all information worthless.
The supplied format is VR2|salt|family|ticker|direction|grade|entry|signal_time; stop and target are omitted. Only a matched completed proof supports its actual covered-byte timing bound. Pending status and provider-declared signal time are different objects. Neither a match nor a founder credential establishes full instruction inventory, subscriber delivery, share fills or account economics. No actual receipt was independently verified for this edition. Changing a covered entry or grade changes the input; changing an omitted stop or target does not. An independent bound must actually be verified and compared with the outcome rather than assumed to exist at release.
Equity evidence starts with the security, original instruction and executable quote. A confirmed hash receipt establishes only its covered bytes by the attestation time. For VR2, target and stop are not covered; its existence does not establish stock-product suitability or an account outcome.
Walk one call through it
Retain the fictional call: a long mid-cap industrial, entry 58.40, target 62.10, stop 56.90, grade B and declared time 13:48:00 UTC. It is not an actual trade or supplied receipt. For the documented format, obtain the real salt, family, ticker and encoding; the target and stop are not covered fields. Changing the stop to 57.60 would not alter this documented preimage. An eleven-session outcome can be a teaching assumption, but no verified block date or pre-outcome ordering is established by the illustration.
Equity evidence starts with the security, original instruction and executable quote. A confirmed hash receipt establishes only its covered bytes by the attestation time. For VR2, target and stop are not covered; its existence does not establish stock-product suitability or an account outcome. In a worked example, the claimed ordering of events remains hypothetical unless an actual receipt and independently dated outcome are supplied.
What failing this test looks like
No representative survey of stock services or their architectures was performed. Ask the actual publisher for first versions and independent timing evidence. An absent proof format is not proof of fraud, while an advertised proof format is not proof that every original record was already confirmed.
- Messaging-app channels (Telegram, Discord). Identify the original publisher, security and quote convention. A stock-channel label says nothing by itself about retained losing calls, execution quality or conflicts.
- Copy-trading rooms. Identify the original publisher, security and quote convention. A stock-channel label says nothing by itself about retained losing calls, execution quality or conflicts.
- Social-media callers. Identify the original publisher, security and quote convention. A stock-channel label says nothing by itself about retained losing calls, execution quality or conflicts.
- Signal-aggregator sites. They re-post other desks' calls without auditing a single one, so every verification hole in the original travels downstream untouched. They miss a re-runnable record by inheritance rather than by intent.
The criterion is an investigation question for the named product, not a blanket failure for channels or an automatic pass for an algorithmic desk. Preserve the original record, chronology and evidence gaps. A useful result identifies the specific object supported, rather than treating a field label or publication format as a financial endorsement.
This is the single mechanism that turns a record from something you admire into something you can audit, which is why it sits at the head of the scorecard and not the foot. To run the check yourself, see the verification walkthrough; for what a full record must also carry, see a re-runnable track record.
What survives a payload match
A completed proof can support the covered-byte timing bound actually verified. Reconstruct the specified encoding and distinguish a provider-declared signal time from independent attestation time. A later completion does not establish pre-outcome chronology. Pending status is not a completed independent Bitcoin bound.
Fictional covered entry changes from 58.40 to 58.50 and its SHA-256 input changes. An omitted stop changes from 56.90 to 57.60 without changing that input. The exercise explains coverage, not an actual receipt validation. Stop amendments still need their original documents and dates; the verifier cannot authenticate bytes it never received.