Post-quantum cryptography
Testnet
The bounded current claim is: the active release uses ML-DSA-65 for native account and independent operator signatures, and the registered transport profile uses ML-KEM-768 Noise. This is not a claim that the entire stack or every future value path is quantum-proof.
Verified application-facing facts
Section titled “Verified application-facing facts”@monolythium/[email protected]derives and verifies ML-DSA-65 keys locally.- The released constants are a 1,952-byte public key and 3,309-byte signature.
- A standard BIP-39 mnemonic can be validated and deterministically mapped to the SDK’s ML-DSA-65 backend and raw address; use the SDK’s bech32m helper for display.
- The registered development-network topology uses 7-of-10 independent operator signatures per cluster certificate; this does not assert current liveness.
- The public mempool is plaintext. It provides no encrypted, sealed, private-send, or threshold-decrypted lane.
Explicit exclusions
Section titled “Explicit exclusions”- No SLH-DSA account, backup-key, emergency-rotation, dual-acceptance, or freeze-and-claim path is released.
- No in-tree bridge or bridge verifier is available.
- No active zkML or prover-market value path should be inferred from old precompile names or SDK encoders.
- Local SDK signing is not a transaction-submission, wallet-custody, HSM, or exchange certification.
Use the compiled signing example for exact TypeScript behavior. Do not implement derivation or transaction formats from historical whitepaper prose.