"Post-quantum" is becoming a badge. Autonomi's developer docs are unusually precise about where it applies, which lets you ask the better question: post-quantum where?
- Transport: ML-KEM-768 key exchange and ML-DSA-65 signatures (NIST FIPS 203/204), with no classical fallback to downgrade to.
- Stored content: self-encrypted with ChaCha20-Poly1305 and BLAKE3. Symmetric, so quantum computers threaten it far less. The weak point is the private DataMap: it's only as safe as wherever you keep it.
- Payments: an EVM wallet on Arbitrum, signed with ECDSA, which is in the class Shor's algorithm breaks. That doesn't expose your files, but it ties the payment layer to the chain's own migration plans.
- Releases: signed with ML-DSA-65, and the docs openly say the ant-node v0.20.0 signatures don't match the key in the repo. A strong signature is only as useful as the key you check it against.
Education only, not an audit or advice.
Post-Quantum Is a Layer, Not a Blanket: What Autonomi's PQC Actually Covers
Autonomi uses post-quantum cryptography for transport and release signing, symmetric ciphers for stored data, and ECDSA for payments. What each lay...
