TLDR:
- Google’s whitepaper shows quantum computers can crack 256-bit ECC with fewer than 500,000 physical qubits in minutes.
- The new quantum circuits represent a 20-fold reduction in resources needed to break ECDLP-256 encryption used in crypto wallets.
- Google sets a 2029 migration deadline, urging blockchains to adopt post-quantum cryptography before quantum threats become operational.
- Google used zero-knowledge proofs to verify quantum attack results without exposing circuit details to potential bad actors.
Post-quantum cryptography has become an urgent priority after Google Quantum AI released a whitepaper revealing alarming findings.
The research shows that future quantum computers could break 256-bit elliptic curve cryptography (ECC) faster than previously thought.
With fewer than 500,000 physical qubits, these machines could crack crypto wallet security in minutes. Google is urging the cryptocurrency industry to accelerate its migration to post-quantum cryptography before 2029.
Google Revises Quantum Resource Estimates Downward
Google’s whitepaper presents two newly compiled quantum circuits targeting the 256-bit elliptic curve discrete logarithm problem (ECDLP-256). One circuit uses fewer than 1,200 logical qubits and 90 million Toffoli gates.
The other uses under 1,450 logical qubits and 70 million Toffoli gates. Both represent a roughly 20-fold reduction in physical qubit requirements compared to earlier estimates.
Ryan Babbush and Hartmut Neven of Google Quantum AI stated the research shows future quantum computers may break elliptic curve cryptography “with fewer qubits and gates than previously realized.”
This reduction changes how soon the threat becomes practical. Previously, industry timelines assumed quantum attacks were decades away. These updated figures push that window considerably closer.
Dragonfly Managing Partner Haseeb responded directly to the research on social media. He noted the new estimates “improve ECDSA cracking efficiency by ~20x,” pushing the expected PQC migration timeline forward to around 2029.
He also pointed out that Google used zero-knowledge (ZK) proofs to verify results without exposing the underlying quantum circuits.
The use of ZK proofs reflects a cautious approach to vulnerability disclosure. Google chose not to publish the actual circuits to avoid giving bad actors a roadmap. This method allows independent verification while keeping sensitive technical details private.
Cryptocurrency Security Faces a Growing Quantum Threat
Most blockchain technologies and cryptocurrencies currently rely on ECDLP-256 for core security functions. This includes wallet authentication and transaction signing.
As quantum computing advances, these protections become increasingly vulnerable. The window to address this is narrowing.
Google’s paper states that these circuits “can be executed on a superconducting qubit CRQC in a few minutes.” That timeline is no longer theoretical.
It is a near-future scenario tied to hardware already in development. The urgency to act is therefore real and immediate.
Google recommends that users refrain from exposing or reusing vulnerable wallet addresses. This is a practical short-term measure while longer-term solutions are developed. The company also raises the question of how to handle abandoned cryptocurrency tied to compromised keys.
Google is collaborating with Coinbase, the Stanford Institute for Blockchain Research, and the Ethereum Foundation.
These partnerships aim to coordinate responsible approaches to post-quantum blockchain security. Together, they are working toward solutions that protect the broader digital economy.
Responsible Disclosure Shapes How Vulnerabilities Are Shared
The debate around vulnerability disclosure has long divided the security community. The “No Disclosure” camp argues that publishing flaws arms bad actors.
The “Full Disclosure” movement counters that transparency enables public protection. Google’s approach borrows from both sides.
Google followed a coordinated disclosure model aligned with standards like ISO/IEC 29147:2018. This framework, also used by CERT/CC and Google’s Project Zero, includes an embargo period.
It gives affected systems time to prepare before details go public. This model is widely accepted in professional cybersecurity.
For cryptocurrency, disclosure carries additional risk beyond technical exposure. Google’s paper warns that “unscientific and unsubstantiated resource estimates can themselves represent an attack on the system.”
The company was careful to reduce fear, uncertainty, and doubt by clarifying where blockchains remain safe from quantum threats.
The company is calling on other research teams to adopt similar disclosure practices. By using ZK proofs to validate findings without revealing attack details, Google sets a new standard. The goal is to protect both the technology and the communities that rely on it.
