Guide

How to verify a stock-signal record

Four steps to confirm a single past call yourself, no spreadsheet required.

Checking one call can show whether its documented receipt is verifiable. It cannot establish the honesty, completeness or performance of an entire service. Repeat across a predeclared consecutive sample and retain unresolved calls.

1. Start with the denominator

Request the complete expected instruction inventory and its exact period. The older Swing row lists 78 and 74.4%, but no dated original ledger was supplied here to verify that population. Keep open, cancelled, missing and unresolved records visible. A printed count is not confirmation that losing instructions survived, and a rounded percentage is not an exact win count. Related source or procedure: a re-runnable track record

2. Demand a continuous run

A representative observation should retain its complete predeclared window. A five-name example cannot prove either that forty-five others existed or that they were deliberately concealed. Identify the expected population from independent inventory evidence and keep the exact cutoff, missing dates and unresolved observations explicit rather than treating a YTD label as a current complete history.

3. Find the independent reviewer

Check that a named outside party has reviewed the underlying statements. A leaderboard ranking is not an audit; a happy-customer quote is not a review.

4. Confirm one call on-chain

Inspect one actual covered packet as a bounded timing exercise. Obtain the original preimage specification, completed receipt and independently dated outcome. A match supports only the covered fields by its verified bound; a pending request or a later bound cannot prove advance publication. This edition supplies no independently verified real receipt and does not infer how often other services fail.

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.

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.
Worked example · illustrative

The call below is a made-up illustration for the walkthrough, not a specific real trade. The procedure is exactly what you would run on a genuine published call.

  1. 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. Obtain the real receipt and its exact preimage specification; an illustrative target and stop do not become covered fields.
  2. For the VR2 reference, use the exact published format: VR2|salt|family|ticker|direction|grade|entry|signal_time. Obtain actual field values and the specified encoding; do not invent a salt or insert target and stop. A different documented provider format needs its own verifier.
  3. Retrieve the actual OpenTimestamps receipt and run the documented verifier. Distinguish an incomplete calendar submission from a confirmed Bitcoin attestation. No receipt or verified block time is supplied by this hypothetical walkthrough.
  4. 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. Compare the verified attestation time with the independently recorded outcome; a provider-declared signal time is a separate claim.

Changing a covered field such as entry or grade changes its SHA-256 fingerprint. Changing an omitted stop or target does not. A matching hash is not a full-ledger audit and does not establish a subscriber fill.

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.

Expand one packet into a population review

A covered-payload check is one bounded record. Reconcile the expected instruction inventory before calling a record complete, and attach independent outcome evidence to each resolved row. The stop and target need their own first-version documents where the proof format omits them. A completed timing bound after the outcome cannot establish that the original prediction preceded it.

Fictional sample expects ten unique instructions. Eight original packets are supplied; two are absent. Of the eight, five have complete quantity/outcome evidence and three remain unresolved. This yields ten expected, eight supplied and five resolved records, not an 80% audit pass or a 100% win rate for the favourite subset. No actual receipt was independently verified in this edition.