Skip to payoff research
Risk Reward Ratio CalculatorLevels / Quantities / Net payoff

A timestamp covers particular bytes

A practical method note with explicit evidence limits.

Original edition: 9 October 2026. Expanded edition: 13 October 2026.

Price-level arithmetic and user-entered samples. A target ratio is neither a measured edge nor a guarantee of the stop fill.

Levels need field coverage

A digest is useful only after identifying its exact inputs. Entry coverage does not imply that a stop, target or quantity was fixed at the same time.

Payoff needs a separate record

An independent time attestation does not establish the execution path, costs or completeness of the population.

Source documents

Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.

Detailed research

Commitment scope travels with the result

The supplied commitment input is VR2|salt|family|ticker|direction|grade|entry|signal_time. It does not contain stop, target, quantity, account weights or broker fills. Declared signal time, initial submission, completed attestation bound and receiving time are separate records. No actual payload/proof pair was checked in this edition. A matching digest would not certify a complete signal population, realised exit path or net payoff.

This exact input format is supplied context, not a newly verified proof. A review needs the actual bytes, encoding, salt, digest, proof file and completed verification record before it can establish a bounded byte-time finding. Field coverage should be read literally. A target shown beside a matching entry is not thereby a target committed in the same payload. The original criterion remains useful without pretending that one verified object establishes a complete historical publication inventory.

A completed fictional field-coverage question

An invented message supplies entry-related committed fields and later displays three target labels. The reviewer can ask whether the committed bytes contain the original quantity, stop and target policy. If those fields are absent, the quantity-weighted payoff needs a separate source record. No actual payload or vendor wrongdoing is asserted in the example. A later favourable price, subscriber receipt or proof submission cannot independently fill the omitted fields. The useful finding states exactly what the narrow record could establish and what the completed exit ledger would still have to show.

Attestation is not completed execution

Declared time, first submission, a completed external attestation bound and actual subscriber arrival are not interchangeable clocks. A pending proof is not silently reported as final, and receiving the instruction does not establish a broker fill. For realised R, retain original risk, quantities, execution costs and complete position identities independently of the digest. A proof can be relevant without certifying every broader performance statement. No Bitcoin immutability claim is used here as a substitute for stop coverage, actual exit prices, complete exclusions or account equity. Missing files remain owner questions rather than a stronger machine-only endorsement.