Bitcoin Faces 5%+ Existential Risk from Quantum Computing by 2030, Says Neha Narula

Available in: 中文
2026-04-08T01:57:05.531Z·1 min read
Neha Narula, Director of MIT's Digital Currency Initiative, published a detailed analysis of Bitcoin's vulnerability to cryptographically-relevant quantum computers (CRQC), arguing that there is a ...

Bitcoin's Quantum Computing Problem Is Real and Urgent

Neha Narula, Director of MIT's Digital Currency Initiative, published a detailed analysis of Bitcoin's vulnerability to cryptographically-relevant quantum computers (CRQC), arguing that there is a non-trivial probability Bitcoin could fail.

The Math

Using reasonable estimates: Google's PQC migration timeline targets 2029, and a Google Quantum co-author suggested a 10% chance of CRQC existing by 2030. The last Bitcoin soft fork (Taproot) took 3 years and 10 months. Combining these: at least 5% probability Bitcoin breaks by 2030 (0.1 × 0.5 = 0.05).

Key Uncertainties

  1. Timeline: When will a CRQC actually appear?
  2. Upgrade path: Can Bitcoin community agree on a post-quantum soft fork?
  3. Wallet migration: Can users move coins to quantum-safe addresses in time?

Investment Implications

Narula frames the CRQC risk as a floor for Bitcoin's probability of reaching $0 — it should combine additively with all other risks (key theft, regulatory bans, competing narratives).

Critical Analysis

The analysis is notable for its specificity. While many quantum threat assessments remain vague, Narula provides concrete probability estimates. The comparison with Google's internal PQC timeline adds institutional credibility.

"It is not 100% clear that Bitcoin will successfully upgrade before a CRQC appears."

The post has gained significant attention on Hacker News, sparking debate about whether Bitcoin's governance structure can handle the required coordination.

← Previous: Scion: New Open-Source Multi-Agent Orchestration Framework for LLM DevelopmentNext: China's Foreign Tourism Boom: Visitor Numbers Surge as Visa Policies Ease →
Comments0