SYNX protocol claims and evidence
See what SYNX states, what primary cryptographic sources establish, and which implementation or audit claims remain unverified in this record.
What the evidence establishes
This ledger records a narrow set of SYNX cryptographic claims. A project statement, an upstream parameter table and an independently reviewed release answer different questions. The status labels below apply to the evidence recorded here, as of the source-check date.
| Claim | Evidence status | Source and scope |
|---|---|---|
| SYNX specifies Kyber-768 for key encapsulation | Project statement | SYNX whitepaper, checked 21 September 2026. It states this cryptographic role. This row does not establish the behavior of a particular release or its conformance to final ML-KEM. |
| SYNX specifies SPHINCS+-SHAKE-128s for signatures | Project statement | SYNX whitepaper and SYNX FAQ, checked 21 September 2026. The named family and parameter set are recorded as project claims; they are not a certificate for the wallet or node verifier. |
| The pinned 128s reference lists 32 / 64 / 7,856 bytes | Pinned reference data Public key / secret key / signature | Upstream parameter table, cross-checked against its SHAKE-128s header at revision 7ec789ace6874d875f4bb84cb61b81155398167e. These are raw reference sizes. They do not measure a SYNX transaction, compressed storage or runtime. |
| FIPS 203 specifies ML-KEM | Published standard | NIST FIPS 203, published 13 August 2024; page checked 21 September 2026. ML-KEM establishes shared secret material. A Kyber-768 product label alone does not establish final-standard compatibility or product validation. |
| FIPS 205 specifies SLH-DSA, based on SPHINCS+ | Published standard | NIST FIPS 205, published 13 August 2024; page checked 21 September 2026. SLH-DSA is a stateless hash-based signature algorithm. Its relationship to SPHINCS+ does not by itself validate a named product or binary. |
| An independent audit is planned for the first halving | Project plan Completion not independently verified | The SYNX FAQ and About page, checked 21 September 2026, describe that plan and state that no external audit has been completed. No completed independent audit report is part of this ledger’s evidence. The plan is not recorded as a completed review. |
| The current release implements the stated scheme correctly | Not independently verified here | The published size-analysis record explicitly excludes SYNX binary validation. This ledger contains no release-specific conformance certificate or independently reproduced signing, verification and recovery results. Reference sizes cannot fill that gap. |
How to read a status
Project statement means a cited SYNX page makes the claim. Published standard identifies what a standards document specifies. Pinned reference data identifies reproducible values in a fixed upstream revision. Not independently verified here means this ledger does not contain evidence sufficient to establish that result; it is not a finding that the implementation fails.
Algorithm selection, standards conformance, deployed verification rules and an external audit are separate claims. The research method and evidence labels explain this separation.
What would support a release or audit finding?
A release finding needs an identified build and source revision, the signing and node-verification paths, the tested inputs and results, and the scope of recovery checks. An audit finding needs the dated report, reviewer, covered version, findings and remediation status. These are evidence requirements, not claims that those checks have been completed.
Use the pinned parameter source card for byte-size provenance, the wallet role guide for key establishment versus signatures, and the source register for related article citations.
Record status
: initial ledger. Project claims, standards and reference values are labeled separately. Audit completion and release correctness remain unverified within this record.
For a correction, identify the public page, claim and supporting source through the existing correction route.