Bitcoin and quantum computing in 2026: where the proposals stand

Started by Natalie, Oct 06, 2026, 07:37 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: Bitcoin and quantum computing in 2026: where the proposals stand   Views(Read 58 times)
Active members in this topic:
Natalie(1) ExoplanetWrench(1) Olivia78(1) Mike80(1)

Natalie

Bitcoin's signatures rely on elliptic curve cryptography, which a large enough quantum computer running Shor's algorithm could break. That has been known for years, but 2026 has been the year the debate moved from blog posts to formal proposals. This thread is a sourced summary of where things stand. It covers the technology and the proposals only, not prices, trading or investment advice

The risk

1. Why Bitcoin is exposed: bitcoin is secured by ECDSA and Schnorr signatures on the secp256k1 curve. If an attacker can work out a private key from a public key, they can spend the coins
2. Which coins are at risk: P2PK outputs, bare multisig and Taproot (P2TR) addresses show the public key on the blockchain as soon as they receive funds. P2PKH, P2WPKH, P2SH and P2WSH addresses only reveal it when coins are spent, so any reused address is exposed
3. How many coins: Chaincode Labs estimated in May 2025 that around 6.26 million BTC, roughly 30 percent of supply, have exposed public keys, including about 1.72 million in P2PK outputs. Google Quantum AI's March 2026 paper puts the figure at around 6.7 to 6.9 million BTC. The BIP 361 authors say over 34 percent of all bitcoin had revealed a public key as of 1 March 2026
4. Long range and short range attacks: a long range attack targets keys that are already public. A short range attack would try to crack a key in the minutes between a transaction being broadcast and being confirmed
5. How big a quantum computer: Google Quantum AI estimated in March 2026 that breaking secp256k1 would need at most around 1,200 logical qubits and 90 million Toffoli gates, which is fewer than half a million physical qubits on superconducting hardware. It estimated a run time of roughly 18 to 23 minutes per key, or about 9 to 12 minutes with precomputation
6. Google did not publish the full attack circuit. Instead it backed its claim with a zero knowledge proof, so others can verify the result without being handed a blueprint

The proposals

7. BIP 360, Pay-to-Merkle-Root (P2MR): authored by Hunter Beast, Ethan Heilman and Isabel Foxen Duke. It started as P2QRH, was renamed P2TSH in September 2025 and became P2MR in February 2026. It works like Taproot but removes the quantum vulnerable key path, and would use SegWit version 2 addresses starting bc1z. It was merged into the BIPs repository in February 2026, which means published for consideration, not activated. It does not add a post quantum signature scheme by itself
8. BIP 361, Post Quantum Migration and Legacy Signature Sunset: authored by Jameson Lopp and others, created in February 2026. Phase A would stop new sends to vulnerable addresses about three years after activation. Phase B would make old signature types invalid two years later, which in effect freezes coins that have not moved. Phase C would allow recovery using zero knowledge proofs of seed ownership, and is still at the research stage
9. The freeze debate: critics have called BIP 361 "authoritarian and confiscatory", because it could freeze coins belonging to people who have lost keys or died, including the early coins widely attributed to Satoshi. Supporters argue that leaving millions of coins for a quantum attacker to steal would be worse. There is no activation timeline
10. Bitcoin Magazine's Quantum Issue: the September 2026 print edition called quantum computing "the concrete example of an existential threat", but argued that workable cryptographic options exist and the open question is which to use
11. Ethereum for comparison: the Ethereum Foundation launched pq.ethereum.org in March 2026, with more than ten client teams running weekly post quantum test networks. Its plan uses hash based signatures and quantum safe account designs, with no firm dates

What holders can do now

12. Avoid reusing addresses, since a reused address has an exposed public key. Google's paper describes Taproot as a regression in this respect compared with hash based address types
13. Follow the proposals. Nothing has been activated, and any change will need broad agreement across the network. I could not find any official 2026 position from Bitcoin Core as a project, only proposals from individual developers

Bitcoin upgrades take years to agree and deploy, which is why the debate is happening now even though no quantum computer can break secp256k1 today. Whatever you think of freezing coins, the technical work on new address types is worth following. Corrections and updates are welcome below

Last updated: 4 October 2026

Sources:



bips/bip-0360.mediawiki at master · bitcoin/bips
bips/bip-0361.mediawiki at master · bitcoin/bips
Bitcoin Developers Propose Bitcoin Quantum Migration Plan That Would Freeze Legacy Coins
https://www.coindesk.com/tech/2026/04/15/bitcoin-developers-are-trying-to-build-quantum-defenses-your-coins-could-pay-the-price
The Quantum Issue: Letter From The Editor
https://www.coindesk.com/tech/2026/03/25/ethereum-foundation-prepares-for-quantum-threat-with-new-cryptography-roadmap
Currently in a title match with my own code

ExoplanetWrench

The short range attack estimate is the scary part. Ten minutes or so per key is close to Bitcoin's average block time. If that ever became possible, even coins in fresh addresses could be stolen while a transaction waits to confirm

Olivia78

Good summary. The renaming of BIP 360 confused me for months, so it helps to see the history in one place. P2MR is a much clearer name than the previous two

Still no signature scheme though, which is the part that matters most in the end. Signatures are where the real work lies

Mike80

BIP 361 is going to be the most divisive proposal in Bitcoin for years. Freezing coins goes against everything many holders believe in

But letting a quantum attacker take a million of Satoshi's coins would hardly be better. There is no painless option here
Lurker since the beginning

Related Topics (6)

Browser ID: smf (possibly_robot, is_webkit)
Templates: 6: index (default), RelatedTopics (default), Block (default), Optimus (default), Display (default), GenericControls (default).
Sub templates: 14: init, html_above, Blockheaders_above, body_above, Blockindex_above, footer_counters_above, related_topics_bot_above, main, related_topics_bot_below, footer_counters_below, Blockindex_below, body_below, Blockheaders_below, html_below.
Language files: 11: index+Modifications.english (default), Turnstile.english (default), RelatedTopics.english (default), Block.english (default), Optimus/Optimus.english (default), Post.english (default), Editor.english (default), Drafts.english (default), giphy.english (default), QRCode.english (default), klipy.english (default).
Style sheets: 7: index.css, attachments.css, turnstile.css, ajaxsearchlite.css, jquery.sceditor.css, show_password.css, responsive.css.
Hooks called: 268 (show)
Instances created: 15 (show)
Files included: 140 - 1922KB. (show)
Memory used: 11077KB.
Tokens: post-login.
Cache hits: 29: 0.00658s for 50,969 bytes (show)
Cache misses: 9: (show)
Queries used: 36.

[Show Queries]