Skip to main content
Post-Quantum Stack
// SEGMENT: NIXEON// LATTICE-NATIVE FROM GENESIS

Lattice-native primitives, post-quantum from genesis.

ML-DSA-44 spend authorization, a lattice state-commitment tree on the Frog ring, SHA3-256 hashing, 4-validator BFT. LatticeFold-style block folding is built and benchmarked but not yet on the consensus path. The cryptography is published research; the integration is ours.

BFT
4
Permissioned validators, f=1
SIGS
every
Tx signature re-verified per block
PQ
0
Pre-quantum signatures
PROOF
~2.3 MB
Folded proof, benchmarked not wired

Six PQ layers. Four integrated, one built, one planned.

NIST-standardized signatures, a lattice state commitment, SHA3-256 hashing. The cryptography is published research; the integration is ours.

LayerPrimitiveHard problemStatus
Spend authorizationML-DSA-44 (FIPS 204)Module-LWE / Module-SIS✓ integrated
Consensus + identityML-DSA-65 (FIPS 204)Module-LWE / Module-SIS✓ integrated
State commitmentLattice gadget tree / Frog ringstructural (no hardness claim)✓ integrated
Block proofLatticeFold-style foldingModule-SIS● built, not wired
HashingSHA3-256 / SHAKE-256SHA-3 preimage✓ integrated
Attestation aggregationChipmunk-PoAModule-SIS○ planned

Honest disclosures

  • 01Nixeon is a testnet. Consensus is 4-validator permissioned BFT, running today. Nothing in the stack has been externally audited, and testnet coins have no value.
  • 02HAWK was withdrawn from NIST's additional-signatures process in July 2026 after a key-recovery attack. Nixeon has since migrated off it completely: ML-DSA-44 authorizes user transactions and ML-DSA-65 signs consensus votes and peer identity, using the fips204 crate rather than a hand-port. ML-DSA is CNSA 2.0's signature, so that surface is already strict. Neither that crate nor this stack has been formally audited. Transactions carry the signer's ML-DSA-44 public key on chain; zero-knowledge spend authorization is designed, not shipped.
  • 03Payments-only by design today. No untrusted smart-contract VM. Programmability comes after the cryptographic stack reaches audit-grade.
  • 04Auditable confidentiality (viewing keys) is planned, not shipped. Anonymous-by-default privacy is intentionally out of scope; that lane is well served by Aleo, Aztec, and Namada.

Read the deep Nixeon technical reference

LatticeFold-style folding, the lattice state-commitment tree, soundness analysis, and the dependency-ordered roadmap live on the Nixeon docs site.