Verified Trading Signals

Signal serialization and format versions

Identify the byte contract before hashing JSON or delimited messages, and keep format migrations separate from old commitments.

Editorial revision: 14 October 2026

Evidence methods, not a provider certification. Authored examples and user-entered check states are not independently verified trading results.

The hash input needs a contract

A displayed record is not automatically the byte sequence that was committed. A serialization contract specifies field order, encoding, separators, escaping, number formatting and missing-value representation. It also identifies the format version. Without that contract, a reader can compute a digest correctly over the wrong representation. The first request should therefore concern the original file and declared format, not a more attractive verification badge.

Delimited text raises practical questions. Can a separator appear inside a value? Are empty values different from omitted ones? Are timestamps UTC strings or numeric values? Is a trailing line break included? Do not fill these details with a convention that happens to reproduce one example. The version that created the commitment governs the check, even when a later interface displays a richer or differently ordered object.

Equivalent JSON can have different bytes

The authored examples {"entry":"100","direction":"long"} and {"direction":"long","entry":"100"} describe equivalent property mappings but have different raw order. A raw-file hash will generally identify different bytes. Adding insignificant JSON whitespace changes a raw-byte digest too. This is not a flaw in SHA-256; it means the producer must state whether it committed the raw export or an explicitly canonical representation.

RFC 8785 describes one JSON canonicalization scheme. That document is a mechanism reference, not proof that a trading service implements it. This publication does not implement a home-made substitute or convert provider files to JCS. If a producer claims that scheme, retain its version, implementation and conformance evidence. Do not use sorting alone as a synonym for a complete canonicalization standard, particularly around number and Unicode handling.

Never upgrade old scope through a new display

Suppose an original commitment contains entry and grade, while a later product screen adds stop, target and quantity. The new display does not insert those omitted fields into the original byte object. A field can acquire evidence through a separately identified later commitment, but its timing and relationship must be assessed independently. The historical record should show which version first bound the field.

A schema migration also needs a mapping of old and new identities. Preserve the prior files rather than rewriting every archive export in the latest format. If the same semantic signal is exported twice under different byte contracts, store both file digests and the declared relation. Equality of economic interpretation is not equality of bytes, and byte equality is not proof that the interpretation is complete or correct.

Separate secrets, salts and interpretation

A salt or nonce can be part of a commitment construction, but its presence does not authenticate the author or fill missing economic fields. Ask which bytes are available to reproduce the specific digest and which are deliberately withheld. A field inventory should distinguish committed values, later-disclosed values and uncommitted display content. Do not guess proprietary formatting from a short marketing description.

The practice packet uses simple authored ASCII and UTF-8 files precisely to keep its hash examples reproducible. Those examples are not an implementation of any provider's production schema. Their labels must not be imported into a real proof register. A transparent parser failure is a software finding, while unavailable serialization is an evidence gap; neither authorizes fabricating a plausible preimage.

Document a migration without manufacturing continuity

A review record should identify source format, input digest, declared fields, parsing interpretation and unresolved questions. For an amendment, retain the parent version and new bytes. If a format migration changes message identifiers, obtain the authoritative mapping rather than joining solely by ticker or similar text. Two instructions can share a symbol and direction while being unrelated originals.

Use the exact-file checker to inspect authored variants and the ID checker to inspect declared parent links. Their outputs answer limited bookkeeping questions. They do not establish a provider's serializer, chronology or complete historical archive. A defensible statement can be that the bytes are reproducible under a supplied format while stop and quantity scope remain unresolved. Format clarity increases inspectability; it does not by itself establish profitable or timely signals.

Mechanism and source references

Mechanism references are not provider certifications. The new editorial examples are authored exercises; no independent financial review was performed.

Inspect the working packet

Eight originals, four discrepancy variants and six chronology cases