Quantum

Core

would

<p><strong>The Bitcoin Core quantum hackers debate has reached a harder question: whether freezing 5.6 million BTC, according to unconfirmed reports, is preferable to leaving quantum-vulnerable coins open to a future theft event. The proposal behind the controversy would create a phased migration path for outputs tied to exposed public keys rather than impose an immediate network rule.</strong></p>
<h2 id="what-the-draft-proposal-actually-does">What the Draft Proposal Actually Does</h2>
<p><a href="https://raw.githubusercontent.com/bitcoin/bips/master/bip-0361.mediawiki" rel="noopener noreferrer nofollow">BIP-361</a>, titled "Post Quantum Migration and Legacy Signature Sunset," is listed as Draft in the official bitcoin/bips repository. That status means Bitcoin has not adopted it and no activation process is under way.</p>
<p>In three phases, the draft would add post-quantum signature support, tighten treatment of legacy spends, and then begin a five-year flag-day timeline toward a legacy-signature sunset for quantum-vulnerable outputs. That is why critics describe the plan as a freeze mechanism even though the document frames it as a migration path.</p>
<p>The target is narrower than the headline suggests. BIP-361 applies the sunset to UTXOs whose public keys are already exposed on-chain, not to every bitcoin in circulation.</p>
<p>If that sunset were ever activated, holders who failed to move affected coins before the deadline would lose the ability to spend them with legacy ECDSA or Schnorr signatures. The policy question is whether that outcome is preferable to leaving the same outputs available for a future quantum theft scenario described in the Draft proposal.</p>
<h2 id="why-the-exact-coin-count-needs-caution">Why the Exact Coin Count Needs Caution</h2>
<p>The official draft does not give a fixed BTC total. Instead, it says that as of March 1, 2026, over 34% of all bitcoin had exposed public keys on-chain and could be stolen by a sufficiently powerful quantum attacker.</p>
<figure>
 <div>
  Quantum-Vulnerable Share
 </div>
 <div>
  34%+
 </div>
 <figcaption>
  Verified in the Draft BIP-361 proposal as the on-chain share with revealed public keys as of March 1, 2026.
 </figcaption>
</figure>
<p>That wording is materially different from a headline-style absolute number. The 34% share is the metric written into the proposal, while any translated coin count depends on assumptions about circulating supply and how exposed-key outputs are measured.</p>
<p>Using the verified percentage and the unverified absolute figure as if they were interchangeable blurs the central policy debate in BIP-361. The stronger reading is narrower: the document supports an exposure ratio, not a confirmed total of coins that would be frozen.</p>
<h2 id="why-quantum-risk-has-moved-from-theory-to-migration-planning">Why Quantum Risk Has Moved From Theory to Migration Planning</h2>
<p><a href="https://raw.githubusercontent.com/bitcoin/bips/master/bip-0360.mediawiki" rel="noopener noreferrer nofollow">BIP-360</a>, also Draft, frames quantum key recovery from exposed public keys as the main long-exposure threat and says post-quantum signatures may also be needed for short-exposure cases. In plain terms, coins are more exposed once the public key is already visible on-chain.</p>
<p>Developers' urgency case rests on two data points: the 34% exposure estimate in BIP-361 and Google's finding that some quantum factoring resource estimates fell by <a href="https://security.googleblog.com/2025/05/tracking-cost-of-quantum-factori.html" rel="noopener noreferrer nofollow">up to 20x</a>. Those figures explain why the discussion has shifted from abstract research to concrete migration planning.</p>
<p>The 34% estimate and the 20x reduction do not prove a practical attack exists today. They do show why some Bitcoin developers think waiting for a live exploit would leave too little time to coordinate a network-wide response.</p>
<h3 id="what-long-exposure-means">What Long-Exposure Means</h3>
<p>Under BIP-360's threat model, long-exposure risk affects UTXOs whose public keys are already on-chain, while short-exposure risk concerns transactions visible before confirmation. The proposed freeze logic in BIP-361 is aimed at the permanently exposed category.</p>
<p>That distinction is why the draft does not treat every holder the same way. A wallet whose public key has not yet been revealed is outside the specific exposure bucket identified by the 34% estimate.</p>
<h3 id="why-external-timelines-matter">Why External Timelines Matter</h3>
<p>BIP-360 also points to institutional migration pressure, citing CNSA 2.0 milestones around 2030 and planning that would retire ECC for most U.S. federal use after 2035. Those dates do not govern Bitcoin, but they show the broader cryptography timetable the proposal is reacting to.</p>
<p>Against those 2030 and 2035 markers, a five-year migration period looks less like panic and more like an attempt to start a slow coordination process early. That timing question is one reason the debate now sits alongside wider industry discussions about infrastructure trust and resilience, including remarks from <a rel="noopener noreferrer nofollow">Ben Zhou at Paris Blockchain Week 2026</a>.</p>
<h2 id="how-the-market-and-the-community-are-reacting">How the Market and the Community Are Reacting</h2>
<p>For market context only, BTC was trading around <a href="https://www.coingecko.com/en/coins/bitcoin" rel="noopener noreferrer nofollow">$74,019</a>, with a -1.65% 24-hour move, a $1.48 trillion market cap, and roughly $42.8 billion in 24-hour volume during the research window.</p>
<figure>
 <div>
  BTC Price Baseline
 </div>
 <div>
  $74,019
 </div>
 <figcaption>
  Public market reference page used in place of the raw API endpoint for a reader-safe source link.
 </figcaption>
</figure>
<p>That $74,019 print is best read as a baseline, not proof that the draft moved price. The same linked market page only shows a broad 24-hour change, not a direct event study tied to BIP-361.</p>
<p>On the governance side, <a href="https://decrypt.co/364450/new-bitcoin-proposal-would-freeze-coins-to-counter-quantum-threat" rel="noopener noreferrer nofollow">Decrypt's reporting on Jameson Lopp</a> said he does not like BIP-361 but sees leaving quantum-vulnerable coins exposed as the worse alternative. That captures the split between security-first pragmatists and critics who view any protocol-level freeze as confiscatory.</p>
<p>The controversy also lands in a market already sensitive to confidence and infrastructure narratives. That makes the debate a natural extension of recent coverage on <a rel="noopener noreferrer nofollow">crypto VC comeback and market-bottom signals</a> and on <a rel="noopener noreferrer nofollow">AI, trust and financial infrastructure</a>, even if the proposal itself remains at the Draft stage.</p>
<h2 id="what-happens-next-if-bitcoin-moves-toward-post-quantum-rules">What Happens Next if Bitcoin Moves Toward Post-Quantum Rules</h2>
<h3 id="has-bitcoin-adopted-this-change">Has Bitcoin adopted this change?</h3>
<p>BIP-361 is still Draft, so Bitcoin has not adopted the proposal and no activation schedule exists. No coins have been frozen under this framework.</p>
<h3 id="who-would-be-affected-first">Who would be affected first?</h3>
<p>Holders of outputs with exposed public keys would face the first migration pressure if the draft ever advanced. The 34% exposure estimate suggests the affected share is large, but the trigger is address structure rather than wallet size.</p>
<h3 id="why-does-it-matter-now">Why does it matter now?</h3>
<p>The timing matters because a five-year sunset period would start only after activation, while the external milestones discussed in BIP-360 arrive in 2030 and 2035.</p>
<p>Those 2030 and 2035 markers, together with the draft's five-year timeline, explain why developers are arguing now over a trade-off between individual coin access and network-wide security. For now, the narrow verified takeaway is that BIP-361 supports an over 34% exposure estimate, while the precise headline-style coin total remains unverified.</p>
<p>Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.</p>
<p>The post <a href="https://coincu.com/?p=400369" rel="noopener noreferrer nofollow">Bitcoin Core Developers Weigh BTC Freeze to Stop Quantum Hackers</a> was initially published on <a href="https://coincu.com/" rel="noopener noreferrer nofollow">Coincu</a>.</p>

Bitcoin Core Developers Weigh BTC Freeze to Stop Quantum Hackers

Table of Contents

Coincu

Other articles published on Apr 15, 2026

Join our free newsletter for daily crypto updates!