Is Bitcoin Vulnerable to Quantum Computers?

Article

March 31, 2026 - Ferdinando Ametrano, Francesco Del Pizzo

Despite alarming headlines, the quantum computing threat to Bitcoin remains manageable. The notion that a new “super-machine” could single-handedly compromise the entire network is an oversimplification: the necessary technology does not yet exist, but the issue is concrete enough to warrant planning and work toward a post-quantum transition.

Two Pillars of Bitcoin’s Security

Quantum computing — a new form of computation that harnesses quantum mechanical phenomena to solve certain classes of mathematical problems far faster than classical computers — is attracting increasing attention. For this reason, quantum computing could undermine important parts of the cryptography used for authentication and for securing digital services (including financial ones) and critical infrastructure.

Bitcoin’s security likewise rests on two cryptographic foundations:

  • Digital signatures for transactions (asymmetric cryptography): they prove that whoever spends or transfers bitcoin has the right to do so.
  • Mining (hashing and proof-of-work): it makes rewriting the transaction history costly and difficult.

Both could, in theory, be affected by quantum computing — but with very different risks and impacts.

The Most Sensitive Point: Digital Signatures

The central concern involves digital signatures. A sufficiently powerful quantum computer could run Shor’s algorithm, a quantum algorithm that makes tractable certain mathematical problems that are intractable today thereby solving the discrete logarithm problem underlying the elliptic curve cryptography Bitcoin relies on.

In plain terms: if Shor’s algorithm were deployable at scale, it could become possible to derive a private key from its corresponding public key. At that point, bitcoin tied to already-known public keys — for example, funds associated with addresses publicly linked to Satoshi Nakamoto — would be more exposed.

This is why it is recommended to never reuse the same address: when spending, certain technical details are revealed (including, in many cases, the public key), and limiting exposure over time is good practice. That said, two facts remain:

  • there are already cases where the public key is known; and
  • during transaction propagation, anyone who sees a transaction before confirmation has access to the data needed to validate it. In a mature quantum scenario, an actor with sufficient capability could attempt to derive the private key within the confirmation time window and broadcast a competing transaction (a race attack or on-spend attack). This, however, requires both quantum capability and favorable network conditions.

What Recent Developments Say (Without the Alarmism)

Over the past several months, the technical literature and research community have made one point increasingly clear: resource estimates for a quantum attack on elliptic curve signatures are falling relative to older assessments. The most recent and authoritative example is the whitepaper published on March 31, 2026 by the Google Quantum AI team: researchers estimate that breaking ECDLP-256 — the mathematical problem underlying Bitcoin’s and Ethereum’s cryptography — could require approximately 1,200 logical qubits and fewer than 500,000 physical qubits, a roughly 20-fold reduction from prior estimates. On the same day, a parallel paper from Caltech and startup Oratomic proposed even lower figures, in the range of 10,000 physical qubits — though all of its authors are shareholders of the company, a conflict of interest worth bearing in mind when assessing the results. None of this means an attack is imminent, but it does make it reasonable to accelerate preparations.

To put these numbers in context, a distinction is necessary:

  • Logical qubits: idealized, stable qubits, as though error correction were already solved.
  • Physical qubits: actual hardware qubits. Obtaining a single logical qubit typically requires many physical qubits, because quantum error correction (fault tolerance) carries significant overhead.

Most of the more “optimistic” analyses — that is, the ones most concerning from a security standpoint — assume substantial progress in error rates, error correction, hardware architectures, and parallelism. It is therefore accurate to speak of a risk that is approaching, but not one that is immediate.

Why This Is Not an Imminent Risk

The critical constraint remains the required technological scale: what would be needed is a fault-tolerant quantum computer capable of sustaining complex computations within timeframes compatible with the attack scenarios described (such as the on-spend attack). Even with reduced estimates, the bar remains well beyond what today’s quantum hardware can reliably achieve.

This places the threat on a medium-to-long-term horizon. The exact timeline is uncertain — it depends on hardware progress — but the direction is clear: preparing now is the rational course.

A consistent signal from the industry: major technology players are planning post-quantum migrations on multi-year roadmaps, not because the risk is “tomorrow,” but because the transition requires years of work and coordination. Google, which commands the world’s most advanced quantum research resources, has set 2029 as its internal deadline to migrate authentication services to post-quantum cryptography — a benchmark that the broader sector, crypto included, would do well to treat as a reference point.

Mining: A Far More Limited Impact

On the mining side, the picture is less alarming. The relevant quantum algorithm is Grover’s, which speeds up hash function searches but only provides a quadratic advantage: it reduces the number of required attempts without turning a hard problem into a trivial one.

Intuitively: even with Grover’s help, mining would remain an activity requiring enormous hardware capacity, energy, and infrastructure. Furthermore, the network can respond by adjusting difficulty, partially offsetting any competitive advantage.

Countermeasures Already Exist (and Are Maturing)

The good news is that research has been active for years. Post-quantum cryptography standards and candidates already exist, including signature schemes and operational guidelines such as the NIST standards ML-DSA/Dilithium and SLH-DSA/SPHINCS+, designed precisely to replace elliptic curve cryptography in high-risk scenarios.

Much as happened with Schnorr/Taproot — the Bitcoin upgrade that introduced more efficient and privacy-friendly signatures and scripts — it is plausible that the Bitcoin community will make significant contributions to the selection, implementation, and standardization of quantum-resistant solutions. The economic incentives are substantial.

What Bitcoin Is Discussing Today

Bitcoin has not yet activated any quantum-resistant changes at the consensus layer, but the most pragmatic direction currently under discussion is a gradual transition:

  • reducing key exposure over time (for example, the BIP-360 proposal, which in essence aims to avoid exposing the key-path spend, shifting toward a “script-spend only” approach); as of March 31, 2026, BIP-360 already has an experimental testnet running — not a definitive solution, but a concrete signal that the ecosystem is moving in the right direction;
  • integrating genuinely post-quantum signatures (e.g. ML-DSA/Dilithium, SLH-DSA/SPHINCS+) through new script rules;
  • introducing new output/address types compatible with these signatures (the SegWit v3 area).

The most delicate challenge is not purely technical but one of coordination: how to migrate existing funds without coercing users, over a very long time horizon. Proposals for “mandatory” migration (hard forks or deadlines) remain highly contentious.

A Manageable Transition: Two Useful Analogies (Y2K + China’s Mining Ban)

The situation is more reminiscent of the Y2K bug than of a sudden collapse: a potentially serious risk, but one with a time horizon long enough to allow for audits, standards, upgrades, and migration — provided the work starts in time. Recent developments do not change the substance of this assessment: they bring the horizon closer, but they do not make it immediate.

At the same time, Bitcoin has already demonstrated remarkable resilience in the face of concrete shocks. One example is the 2021 China mining ban: within weeks, an enormous share of global hashrate went dark, and countless headlines declared the end of Bitcoin. In reality, the network adapted automatically — mining difficulty dropped, miners relocated to other countries, and within months the hashrate returned to high levels. What appeared to be a fatal blow turned out to be a demonstration of the system’s robustness.

The point is that quantum computing, however deeper a challenge on the cryptographic plane, is a slower and more predictable threat than a sudden government ban: it does not arrive overnight and leaves time to plan a post-quantum transition. If Bitcoin absorbed a fast and brutal exogenous shock to its mining infrastructure, it also has the time and the tools to navigate a cryptographic migration announced years in advance — as long as the work begins in earnest, and with method.

Conclusion

Concerns about quantum computing as an “immediate” threat to Bitcoin remain overblown relative to the actual state of the technology. The latest technical work — including Google’s March 31, 2026 whitepaper — represents a meaningful update to resource estimates and a legitimate call to accelerate preparations, but not an announcement of imminent danger.

The necessary hardware does not yet exist. The vulnerability, though closer than before, remains theoretical. Post-quantum solutions are already standardized and deployable. Quantum computing is the next great test for modern cryptography: not a cause for panic, but an invitation to prepare early and prepare methodically.

Open an account

Your account gives access to all CheckSig services. Impeccable services on extremely favorable terms.

View costs

Contact us

Need clarification? Have specific needs? Contact our support team, always available.

Share logoShare logoShare logoShare logoShare logoShare logoShare logoShare logoShare logo