On March 31, 2026, Google Quantum AI published a whitepaper claiming that future quantum computers may break the elliptic curve cryptography protecting cryptocurrency with fewer resources than previously realized. Specifically, they compiled Shor's algorithm circuits for ECDLP-256 using less than 1,200 logical qubits and 90 million Toffoli gates, or less than 1,450 logical qubits and 70 million Toffoli gates, executable in minutes on a superconducting CRQC with fewer than 500,000 physical qubits.1

Rather than publishing the underlying circuits, Google shares the resource estimates through a zero-knowledge proof, allowing third parties to verify the claims without leaking sensitive attack details. This disclosure follows engagement with the U.S. government and is framed as a responsible alternative to both no-disclosure and full-disclosure positions, which the blog post discusses at length.1

The genuinely new element is the quantitative tightening of the feasibility threshold. By moving the requirement below 500,000 physical qubits and minutes of runtime, Google shifts the threat from a distant theoretical concern to a milestone that intersects with current hardware roadmaps, reinforcing the urgency of its 2029 PQC migration timeline.1

AI hypothesisIf these estimates are independently reproduced, elliptic-curve-protected cryptocurrencies could face practical quantum attacks sooner than many prior projections suggested, making wallet hygiene and policy interventions more urgent. What would change this assessment is external verification of the zero-knowledge proof or a peer-reviewed benchmark; conversely, competing estimates with higher resource requirements would lower the perceived urgency.1

Context

Google states it has led the responsible transition to post-quantum cryptography since 2016 and recently introduced a 2029 migration timeline. Most blockchain technologies and cryptocurrencies currently depend on ECDLP-256 for critical security, and the whitepaper argues that post-quantum cryptography is a well-understood path to securing them, while noting that viable solutions will take time to implement.1

Caveats

The evidence is limited to a single corporate blog post without a link to the full whitepaper or the zero-knowledge proof, and independent validation is absent. The discussion of FUD as a potential attack vector is also an argument about the social consequences of disclosure and does not by itself establish the correctness of the resource estimates.1