Disclaimer: Information found on CryptoreNews is those of writers quoted. It does not represent the opinions of CryptoreNews on whether to sell, buy or hold any investments. You are advised to conduct your own research before making any investment decisions. Use provided information at your own risk.
CryptoreNews covers fintech, blockchain and Bitcoin bringing you the latest crypto news and analyses on the future of money.
Bitcoin is expected to face hacking threats in two years, along with other claims regarding quantum resistance.
A newly launched quantum countdown website estimates a two- to three-year timeframe for quantum computers to compromise widely utilized public key cryptography, which includes Bitcoin.
<p Websites such as The Quantum Doom Clock, managed by Postquant Labs and Hadamard Gate Inc., incorporate bold assumptions regarding qubit scaling and error rates into a timeline that extends from the late 2020s to the early 2030s for a quantum computer capable of cryptographic relevance.
This presentation also serves as product promotion for post-quantum tools, though one must examine the details to recognize that disclosure.
The Quantum Doom Clock indicates that recent resource assessments, which condense logical-qubit counts, along with optimistic trends in hardware error rates, imply that the necessary physical-qubit class for breaking ECC falls within the few-million range under favorable conditions.
The clock’s settings depend on exponential growth in hardware and enhanced fidelity with scale, while runtime and error-correction overheads are considered manageable in the short term.
Government standards organizations do not regard a 2027 to 2031 breach as a baseline scenario.
The U.S. National Security Agency’s CNSA 2.0 guidance advises that National Security Systems should finalize their transition to post-quantum algorithms by 2035, with incremental milestones leading up to that date, a sentiment echoed by the UK National Cyber Security Centre.
This necessitates the identification of quantum-sensitive services by 2028, prioritizing critical migrations by 2031, and completing them by 2035.
The policy timeline acts as a practical risk guide for organizations that need to plan capital budgets, vendor dependencies, and compliance initiatives, suggesting a multi-year migration process rather than an abrupt two-year deadline.
While laboratory advancements are significant and pertinent, they do not demonstrate the necessary combination of scale, coherence, logical gate quality, and T-gate factory throughput that Shor’s algorithm would require to compromise Bitcoin.
As per Caltech, a neutral-atom array with 6,100 qubits has achieved 12.6 seconds of coherence with high-fidelity transport, marking an engineering milestone toward fault tolerance rather than showcasing low-error logical gates at appropriate code distances.
Google’s Willow chip development emphasizes algorithmic and hardware improvements on 105 qubits, claiming exponential error suppression with scale for specific tasks. Meanwhile, IBM has showcased a real-time error-correction control loop operating on standard AMD hardware, representing progress toward systems achieving fault tolerance.
None of these developments eliminate the significant overheads that previous resource studies identified for classical targets like RSA and ECC under surface code assumptions.
A frequently referenced 2021 analysis by Gidney and Ekerå estimated that factoring RSA-2048 in approximately eight hours would require around 20 million noisy physical qubits at about 10⁻³ physical error rates, highlighting how distillation factories and code distance influence totals more than mere device counts.
For Bitcoin, the earliest significant risk arises from key exposure on-chain rather than harvest-now-decrypt-later attacks against SHA-256. According to Bitcoin Optech, outputs that already disclose public keys, such as legacy P2PK, reused P2PKH after spending, and certain Taproot paths, would become targets once a cryptographically relevant machine is available.
Simultaneously, typical P2PKH remains safeguarded by hashing until it is spent. Core contributors and researchers are monitoring various containment and upgrade strategies, including Lamport or Winternitz one-time signatures, P2QRH address formats, and proposals to quarantine or enforce the rotation of insecure UTXOs.
Advocates of BIP-360 assert that over 6 million BTC are held in quantum-exposed outputs across P2PK, reused SegWit, and Taproot, which is best understood as an upper limit from proponents rather than a consensus figure.
The economics of migration are as crucial as the physics.
With NIST currently finalizing FIPS-203 for key encapsulation and FIPS-204 for signatures, wallets and exchanges can implement the selected family immediately.
According to NIST FIPS-204, ML-DSA-44 features a 1,312-byte public key and a 2,420-byte signature, which are significantly larger than those of secp256k1.
Under existing block constraints, substituting a typical P2WPKH input witness with a post-quantum signature and public key would elevate the per-input size from tens of virtual bytes to several kilobytes. This would reduce throughput and increase fees unless paired with aggregation, batch-verification-friendly constructs, or commit-reveal patterns that transfer bulk data off critical paths.
Organizations with numerous exposed public key UTXOs have a financial incentive to methodically de-expose and rotate before a rush concentrates demand into a single fee spike period.
The differences between a marketing-driven clock and institutional roadmaps can be summarized as a set of input assumptions.
Recent studies that lower logical-qubit counts for factoring and discrete log problems can make a few-million physical qubit target seem nearer, but only under assumed physical error rates and code distances that remain beyond what laboratories demonstrate at scale.
The prevailing laboratory perspective reflects incremental device scaling where adding qubits can diminish quality, with a trajectory toward 10⁻⁴ to 10⁻⁵ error rates as code distance increases.
A cautious interpretation places material limits, control complexity, and T-factory throughput as rate limiters that extend timelines into the 2040s and beyond, barring breakthroughs.
The policy momentum to complete migrations by 2035 aligns more closely with the stepwise and conservative scenarios than with exponential hardware growth.
| Case | Hardware and error path | Physical qubits for ECC-256* | Earliest window | Primary sources |
|---|---|---|---|---|
| Marketing-aggressive | Exponential qubit growth, ≤10⁻³ errors improving with scale | Few million | Late-2020s to early-2030s | Quantum Doom Clock |
| Mainstream lab | Stepwise scaling, error reduction with code distance | Many millions | Mid-2030s to 2040s | CNSA 2.0, UK NCSC |
| Conservative | Logistic growth, slower fidelity gains, factory bottlenecks | Tens of millions+ | 2040s to 2050s+ | Quantum Doom Clock |
*Totals depend on surface code distance, logical gate error targets, and T-gate distillation throughput. See Gidney and Ekerå (2021).
Concrete forward-looking markers to monitor.
- Peer-reviewed demonstrations of long-lived logical gates, not solely memory, at code distance around 25 with sub-10⁻⁶ logical error rates.
- Operational T-gate distillation factories that provide throughput for algorithms with over 10⁶ logical qubits.
- Bitcoin Improvement Proposals that advance post-quantum signature pathways from prototype to deployable standard, including formats that keep bulk artifacts off critical paths.
- Public commitments from major exchanges and custodians to rotate exposed outputs, which would distribute fee pressure over time.
The Doom Clock’s function is narrative, condensing uncertainty into urgency that channels toward a vendor solution.
The risk compass that is significant for engineering and capital planning is anchored by finalized NIST standards, government migration deadlines around 2035, and laboratory milestones that would signify genuine inflection points for fault tolerance.
According to NIST’s FIPS-203 and FIPS-204, the tooling path is accessible today, allowing wallets and services to begin de-exposing keys and testing larger signatures without adhering to a two-year doomsday scenario.
Bitcoin’s hash-then-reveal design choices already postpone exposure until spending time on common paths, and the network’s strategy includes various rotation and containment options when credible signals, rather than vendor clocks, indicate it is time to act.
However, it is important to note that when quantum computers render Bitcoin’s cryptography vulnerable, other legacy systems will also be at risk. Banks, social media, finance applications, and many more will have vulnerabilities left wide open.
Societal collapse poses a greater risk than the loss of some cryptocurrency if legacy systems are not updated.
For those who contend that Bitcoin upgrades will lag behind those of banks and similar entities, it is worth remembering that some ATMs and other banking infrastructure globally still operate on Windows XP.
The post Bitcoin will be hacked in 2 years… and other quantum resistant marketing lies appeared first on CryptoSlate.