Key Takeaways
- Bitcoin developers debate quantum threats to ECDSA signatures.
- BIP-361 proposes a five-year deadline to migrate or freeze vulnerable coins.
- BitMEX’s quantum canary uses a bounty address as proof of attack before any freeze.
- Views split on freezing: necessary protection versus violation of coin sovereignty.
As concerns around quantum computing continue to build, Bitcoin developers are once again debating how the network should respond.
A new proposal from BitMEX Research introduces a more reactive approach, centered on what it calls a “quantum canary,” offering an alternative to earlier, more aggressive plans.
The debate is exposing a deeper divide—between those pushing for early safeguards and those wary of altering Bitcoin’s core principles.
The Quantum Threat
Bitcoin’s current signature scheme, ECDSA, is vulnerable to sufficiently powerful quantum computers capable of solving the discrete logarithm problem that underpins it.
Once such machines are in place, attackers could derive private keys from public keys exposed on-chain.
According to estimates cited in recent analyses, more than a third of all Bitcoin, roughly 34%, has already broadcast its public keys, leaving those holdings theoretically exposed.
The timeline remains uncertain. Some researchers warn a breakthrough could come sooner than expected, while others, including Galaxy Digital’s Alex Thorn, argue the risk is still manageable in the near term.
Either way, the community agrees that preparation is prudent. The question is how, and at what philosophical cost.
BIP-361: The Five-Year Ultimatum
Last week, a group of developers, including Casa CTO Jameson Lopp, published BIP-361, a Bitcoin Improvement Proposal that takes a blunt approach.
It would phase out legacy address types over a 5-year period.
After the grace period, any coins still sitting in vulnerable formats would become permanently unspendable through a soft fork.
The goal is straightforward: force migration to quantum-resistant schemes before an attack materializes.
Lopp himself has been candid about his reservations.
He describes the plan as a contingency he “doesn’t like,” and hopes will never be needed. Yet he and his co-authors see it as a necessary evil.
In their view, the existential risk to the network outweighs the sanctity of individual coin control.
Critics, however, call it a dangerous precedent, an admission that developers can rewrite property rights when the threat feels grave enough.
The backlash has been swift and fierce, highlighting Bitcoin’s cultural allergy to any form of centralized coercion.
The Quantum Canary: A Bounty-Fueled Tripwire
BitMEX Research’s counter-proposal flips the script from preemption to proof.
Their mechanism, outlined in a blog post this week, creates a special “canary” address whose private key is provably unknown—generated via a cryptographic construct (a Nothing-Up-My-Sleeve number) that ensures no one holds the secret.
A bounty of Bitcoin is placed into this address, potentially supplemented by community donations.
Because only a quantum computer capable of breaking ECDSA could spend from it, any movement of those funds would serve as undeniable, on-chain evidence of a successful attack.
At that moment, a pre-programmed soft fork would activate, freezing coins in vulnerable legacy wallets.
A built-in “safety window” would retroactively lock any transfers made in the immediate lead-up to the trigger, thwarting stealthy preemptive heists.
The design is elegant in its minimalism.
Coins remain fully spendable until an attack is proven. No arbitrary deadline forces users to move funds.
Instead, the network reacts only when the threat is no longer theoretical.
Divided Views on Freezing Assets
The core disagreement centers on whether freezing coins is ever justifiable.
Proponents of BIP-361 argue that failing to act preemptively invites catastrophe: a quantum-equipped adversary could drain exposed wallets en masse before the network has time to respond.
Freezing, in this camp, is a temporary network-level defense akin to an emergency brake, ugly but essential to preserve overall trust in Bitcoin.
Opponents, and even some BIP-361 authors themselves, recoil at the idea. Bitcoin’s value proposition has always rested on the promise that “your keys, your coins.”
Introducing any mechanism that lets developers invalidate holdings, they contend, erodes that guarantee and opens the door to future abuses.
Lopp’s own discomfort underscores this tension: even those drafting the proposal recognize it clashes with cypherpunk ideals.
The canary approach attempts to thread the needle.
By requiring empirical proof via the bounty spend, it preserves user sovereignty until the last possible moment.
Yet skeptics point out a glaring flaw: it assumes the first quantum actor will claim the relatively modest bounty rather than target far larger, unprotected wallets.
If an attacker opts for the heist instead, the canary never sings—and the freeze never triggers.
The safety window mitigates timing attacks, but it cannot eliminate the risk that a sophisticated adversary simply ignores the lure.
Implications for Bitcoin’s Long-Term Resilience
Both proposals reflect a maturing recognition that quantum computing is not science fiction.
They also expose the trade-offs inherent in Bitcoin’s decentralized governance.
A preemptive freeze risks alienating users and inviting accusations of overreach; a reactive tripwire risks being too slow or too reliant on attacker behavior.
Community donations to the canary fund could sweeten the bounty, turning the mechanism into a decentralized insurance policy.
Investors could even structure contributions via multisig arrangements, retaining the ability to withdraw their stake until the threat materializes.
Still, the proposal’s success hinges on collective buy-in and node operators’ willingness to enforce the fork once triggered.
As the debate unfolds on developer mailing lists and forums, one thing is clear: Bitcoin’s quantum migration will test the network’s ability to balance security with its founding principles.
Whether the community ultimately embraces a five-year deadline, a bounty-fueled canary, or some hybrid solution remains to be seen.
What is certain is that the conversation has moved beyond denial to pragmatic—albeit contentious—planning.
Prashant Jha is a seasoned crypto journalist based in Delhi, India, with a Bachelor’s Degree in Computer Science Engineering. Passionate about the evolving world of blockchain and cryptocurrencies, he has been a dedicated voice in the industry since 2018. Prashant’s expertise lies in regulatory reporting, where he unravels complex legal and financial developments with clarity and precision. Before joining CCN in 2024, he honed his craft at Cointelegraph, establishing himself as a trusted name in crypto journalism.
His coverage spans major industry events, including the high-profile collapses of FTX, Three Arrows Capital (3AC), and LUNA, offering readers insightful analyses of their regulatory and market implications. Prashant’s technical background enables him to bridge the gap between intricate blockchain technology and its real-world applications, making his work accessible to novices and experts.
Beyond his professional pursuits, Prashant is an avid music enthusiast, often exploring diverse genres to unwind. A sports lover, he has a particular passion for cricket and frequently engages in discussions about the game. His multifaceted interests and sharp journalistic instincts make him a valuable contributor to CCN, where he continues shaping the crypto landscape's narrative.
