Post-Quantum Cryptography
The post-quantum cryptography described here centers on saorsa-pqc, transport documentation built around ML-KEM-768 and ML-DSA-65, and ant-keygen release-signing with ML-DSA-65.
Why it matters
If you are reasoning about security, transport identity, or release authenticity, you need to know which cryptographic primitives the stack uses.
How it works
saorsa-pqc
saorsa-pqc is a broader PQC library that includes:
ML-KEM key encapsulation variants
ML-DSA signature variants
SLH-DSA signature variants
BLAKE3, SHA3, HMAC, HKDF, AES-256-GCM, and ChaCha20-Poly1305
So the library itself is broader than any single Autonomi-facing transport choice.
saorsa-transport
saorsa-transport describes its transport layer as pure post-quantum and highlights this pair for transport use:
ML-KEM-768 for key exchange
ML-DSA-65 for signatures
The transport layer has no classical fallback.
ant-keygen
ant-keygen is the release-signing CLI that uses ML-DSA-65. It generates release-signing keypairs, signs files, verifies signatures, and supports a signing context for domain separation.
Key separation and signing contexts
saorsa-pqc provides HKDF-SHA3-256 and HKDF-SHA3-512 as key-derivation primitives.
That means the crypto library can derive new key material from shared secrets or existing key material. ant-keygen also supports a signing context so one signing domain stays separate from another. The default context is ant-node-release-v1.
Practical example
Upstream sources
Related pages
Last updated