Thaler’s core argument is blunt: timelines to a cryptographically relevant quantum computer are being wildly overstated, leading to rushed calls for sweeping post-quantum migrations that may introduce more risk than protection. Based on publicly known milestones, he argues that a quantum system capable of breaking real-world cryptography remains well beyond reach, even over the next decade.
He draws a sharp distinction between encryption and digital signatures—two concepts often lumped together in online discourse. Encryption is vulnerable to so-called “harvest now, decrypt later” attacks, where encrypted data intercepted today could be cracked years down the line once quantum machines mature. For that reason, Thaler says post-quantum encryption should already be rolling out where long-term confidentiality matters.
Privacy-focused chains are a different story. Networks that encrypt transaction details could see historical activity retroactively exposed if quantum computers eventually defeat elliptic curve cryptography. For those systems, earlier transitions—or hybrid approaches—may be justified if performance costs are tolerable.
After A16z shared the research thread publicly, replies quickly filled with users championing their favorite so-called “quantum-resistant” coins—often without acknowledging the technical trade-offs or the long timelines Thaler outlines. The response pointed to his broader point: the conversation around quantum risk is moving faster than the science itself.
FAQ What is a cryptographically relevant quantum computer?A fault-tolerant quantum system capable of breaking modern public-key cryptography at scale. Is Bitcoin vulnerable to harvest-now-decrypt-later attacks?No, because Bitcoin uses signatures for authorization, not encryption. Why does encryption face more urgent quantum risk than signatures?Encrypted data can be stored today and decrypted later, while signatures cannot be retroactively forged. Should blockchains migrate to post-quantum cryptography now?Planning should start now, but rushed deployment carries serious technical risks.
