Verified Trading Signals

Proof-review source map

Mechanism documentation is not a provider audit.

Editorial revision: 14 October 2026

Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.

Hash mechanism

NIST specifies secure hash functions; it does not attest the source, time or completeness of a trade record.

Timestamp workflow

OpenTimestamps documents its client. Retain the actual receipt and verification output before asserting a provider anchor.

Browser calculation

Web Cryptography supplies the browser digest operation. The text checker makes no network proof request and issues no certification.

Blank working records

Headers only. No observed trades, receipts or study findings are supplied in these templates.

Source documents

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

Follow the mechanism to its proper claim

NIST supports the hash-function reference, W3C the browser API, OpenTimestamps the proof workflow, RFC 8785 canonicalization and RFC 3339 timestamp representation. None certifies the listed providers. The new order-type link addresses why an order and fill are different objects. Original attachments and actual performed checks must still be supplied for a real review.

Download populated practice, not fabricated findings

The eight-ID packet and exact-byte register provide inspectable authored inputs. Their schema explicitly leaves authentic proof, broker, subscriber and financial-validation records null. Blank earlier CSV templates remain available for a reader's own lawful records. Software repeatability and cloud deployment readbacks should never be described as independent validation of trading performance.