Description:
Venice's E2EE encryption currently uses ECDH (secp256k1) + AES-256-GCM. While this is secure against classical computers, secp256k1 is vulnerable to Shor's algorithm on quantum computers. This creates a "harvest now, decrypt later" risk — adversaries can capture encrypted traffic today and decrypt it when quantum capabilities become available.
The Risk:
State-level actors and advanced adversaries are already capturing encrypted communications for future decryption
Venice positions itself as the privacy-first alternative to OpenAI/Anthropic
Current encryption protects against today's threats, not tomorrow's quantum attacks
Proposed Solution:
Implement hybrid post-quantum cryptography alongside existing ECC:
ML-KEM (Kyber) for key encapsulation — NIST standardized, August 2024
ML-DSA (Dilithium) for authentication — NIST standardized
Hybrid mode: Combine existing ECDH with ML-KEM during transition period
Precedent:
Tuta (formerly Tutanota) has deployed post-quantum encryption
Signal is implementing PQC
Google has PQC roadmap for 2029
Apple has deployed PQC for iMessage
Why This Matters for Venice:
Venice serves journalists, lawyers, healthcare professionals, and privacy-conscious users who need long-term confidentiality. These users face state-level adversaries who absolutely will use quantum decryption when available. "Trustless" privacy requires cryptographic guarantees that survive the quantum transition.
Implementation Path:
Hybrid key exchange (ECDH + ML-KEM) for E2EE models
Gradual migration to pure PQC as standards mature
Optional "quantum-safe" mode for high-risk users
This is not theoretical — NIST finalized PQC standards in 2024. Venice should lead, not follow, on post-quantum privacy.