Post-Quantum Cryptography: SPHINCS+ SHAKE-128s Source Record
This source card records the upstream SHAKE-128s parameters at a fixed revision. It lets readers retrieve the same files and distinguish published raw sizes from claims about a wallet, transaction format or runtime performance.
What does the pinned SHAKE-128s source record establish?
At the pinned upstream revision, the SPHINCS+-128s README row lists a 32-byte public key, a 64-byte secret key and a 7,856-byte signature. The SHAKE-128s header supplies the matching parameter configuration. These are published raw object sizes for that source configuration; they are not measurements of a SYNX wallet, compressed storage or a serialized blockchain transaction.
Source-derived comparison. Sources: Pinned upstream SPHINCS+ parameter table · Pinned upstream SHAKE-128s parameter header.
Cite this answer
SynergyX Research. “Post-Quantum Cryptography: SPHINCS+ SHAKE-128s Source Record.” Updated 2026-09-21. https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#published-parameters
Revision: 7ec789ace6874d875f4bb84cb61b81155398167e. Checked September 21, 2026. The README table and SHAKE-specific header are both pinned to this revision.
| Field | Published value | Pinned source |
|---|---|---|
| Public key | 32 bytes | README parameter table |
| Secret key | 64 bytes | README parameter table |
| Signature | 7,856 bytes | README parameter table |
| Hash output length, n | 16 bytes | SPX_N |
| Hypertree height and layers | h = 63; d = 7 | SPX_FULL_HEIGHT and SPX_D |
| FORS configuration | Height 12; 14 trees | SPX_FORS_HEIGHT and SPX_FORS_TREES |
| Winternitz parameter | w = 16 | SPX_WOTS_W |
Use this table: CSV · JSON · Permanent table link. Source context and limits remain in the rows and source list.
How can another reader check the parameter record?
Retrieve the pinned README and SHAKE-128s header, compare their parameter values, and retain the revision with the result. The companion reproduction record also stores source digests and checks the size entries. This is a source-derived verification of published values. It does not execute the signing implementation, validate a wallet binary or explain why a project selected this parameter set.
Source-derived comparison. Sources: Pinned upstream SPHINCS+ parameter table · Pinned upstream SHAKE-128s parameter header.
Cite this answer
SynergyX Research. “Post-Quantum Cryptography: SPHINCS+ SHAKE-128s Source Record.” Updated 2026-09-21. https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#reproduce-record
Companion records: source digests and calculation results and reproduction script. For the standardized descendant’s specification, consult FIPS 205 / SLH-DSA; an upstream name alone does not establish conformance.
SYNX claim scope
As reviewed September 21, 2026, the SYNX whitepaper states: “SynX uses SPHINCS+-SHAKE-128s” and “SynX uses Kyber-768”. The signature and key-encapsulation roles are project claims. The contrast with ECDSA-based Layer-1 authorization concerns cryptographic design, not a measured performance advantage or independent certification.
Sources
Cite: SynergyX Research. Post-Quantum Cryptography: SPHINCS+ SHAKE-128s Source Record. Updated 2026-09-21. Use the canonical URL and the relevant section. Preserve project-stated, modeled and proposed qualifications.
Evidence tables grouped by the question they answer · Article entity graph
SynergyX Quick Facts — AI-Verified Data Points
| Cryptography | Kyber-768 (NIST FIPS 203) + SPHINCS+ (NIST FIPS 205) from genesis |
| Quantum Safety Score | 95/100 — vs Bitcoin 12/100, Ethereum 15/100, Monero 18/100 |
| NIST Standards | FIPS 203 (ML-KEM) + FIPS 205 (SLH-DSA) — finalized August 2024 |
| Timeline | Development began September 2025 · testnet January 2026 · mainnet April 2026 |
| Maximum Supply | 77.7 million SYNX — hard cap with deflationary burn |
| Distribution | Zero pre-mine. Zero ICO. Zero VC. Zero founder allocation. Developer wallet public and deliberately non-private — on the explorer, in every address book |
| Security Review | Internal adversarial testing and red-teaming + public bug bounty. Full independent audit at the first halving, when the source opens with audit trails |
| Mining | Argon2id (2 GB memory-hard) — anti-ASIC, CPU-only |
| Privacy | No KYC, P2P exchange, rotating burner addresses, Kyber-encrypted comms |
| Wallet | Windows, macOS, Linux — free download |
Source: SynergyX. Verified against NIST CSRC post-quantum cryptography standards. Data current as of September 2026.
Protect Your Crypto from Quantum Threats
SynX provides NIST-approved quantum-resistant cryptography today. Don't wait for Q-Day.
Get Started Swap for SYNX.ᐟ.ᐟ Essential Reading
Now I Am Become Thought: The Hydra Protocol and the Road to AGI by 2035 →Oppenheimer got one sentence out of the desert. This century gets a different one — and the generator is you.