Quantum computing's threat to blockchain security is widely exaggerated — so says a16z Crypto in a new analysis that pushes back against panic-driven calls for an immediate post-quantum overhaul.
The venture firm argues that cryptographically relevant quantum computers remain decades away, making wholesale transitions unnecessary for now. However, not all cryptographic primitives are equally safe.
Encryption vs. Signatures: Different Timelines
Digital signatures — used by nearly all blockchains including Bitcoin and Ethereum for transaction authorization — are safe until a CRQC (cryptographically relevant quantum computer) exists. But encrypted data faces a different threat known as 'harvest-now-decrypt-later' (HNDL): adversaries can collect encrypted information today and decrypt it once quantum machines become powerful enough.
Hybrid encryption is already proving viable. Chrome, Cloudflare, Apple iMessage, and Signal all use schemes that combine classical and post-quantum algorithms. This approach hedges against both future quantum attacks and potential flaws in new post-quantum standards.
Bitcoin and Ethereum's Governance Hurdles
Bitcoin and Ethereum rely on signatures that won't be vulnerable until CRQCs arrive. But a16z flags unique challenges: slow governance, abandoned coins, and high-value addresses make migration planning critical. Rushing could cause irreversible damage to these networks.
Privacy Chains Face Immediate Pressure
Monero and Zcash are in a tighter spot. Their confidential transaction data, stored on-chain, could be retrospectively decrypted by a future quantum computer. a16z advises these platforms to adopt hybrid or full post-quantum encryption now, or redesign to avoid storing decryptable secrets entirely.
Developers: Post-Quantum Crypto Isn't Plug-and-Play
Implementing post-quantum cryptography brings new headaches: lattice-based and hash-based signatures are much larger than traditional ones, and bugs, side-channel leaks, and poor performance are real risks. a16z recommends a phased approach: secure encryption first with hybrid schemes, move to signatures later, and pay special attention to protecting complex data structures like zkSNARKs.