Bitcoin has long been considered the gold standard of cryptographic security, thanks to the robustness of the ECDSA and Schnorr digital‑signature algorithms. Yet today, discussions in the crypto community are shifting toward a once‑theoretical scenario that now looks increasingly realistic: old BTC addresses are under threat from future quantum computers, and the network may need to undergo a radical upgrade — BIP‑361 — to prepare for post‑quantum cryptography. The conversation is no longer limited to labs and white papers; it directly affects millions of wallets, bursaries, and long‑term holders of BTC.
Current Bitcoin cryptography relies on mathematical operations that are easy in one direction but hard to reverse. A private key generates a public key, which in turn generates an address; yet deriving the private key from the public key remains computationally infeasible for classical computers. However, quantum algorithms like Shor’s algorithm fundamentally change this balance: they can, in theory, recover the private key from a public key in a time that is orders of magnitude less than the current lifetime of the universe.
This is why researchers increasingly warn that any address tied to a visible public key is potentially vulnerable if sufficiently powerful quantum hardware appears. Analysts estimate that around 33–34 % of all issued BTC may be considered “at risk” because their public keys have already been exposed on‑chain. Such coins are typically associated with older address formats (P2PK, certain P2PKH transactions, and legacy wallets) whose public data sits exposed in the blockchain ledger. The risk is not just hypothetical; it implies that under a successful quantum attack, a portion of BTC could be quietly drained over time, with the impact only becoming visible after the fact.
Post‑Quantum Threats and the BIP‑361 Proposal
At the center of the discussion is BIP‑361, a Bitcoin improvement proposal designed to move the network toward post‑quantum cryptography. The document outlines a multi‑phase transition plan aimed at protecting Bitcoin’s value and accessibility against future quantum breakthroughs. Importantly, BIP‑361 is not a finalized standard; it is a proposal that the community is debating, testing, and scrutinizing in depth.
Developers propose a three‑phase approach:
- Phase A — “Freezing” vulnerable outputs: In the first phase, the network may introduce rules that prevent new BTC from being sent to older, potentially vulnerable address formats. This is primarily a warning mechanism: anyone attempting to send BTC to a legacy scheme would encounter a hard warning that the target address may be at risk. The suggested timeline for this phase begins approximately three years into the future, giving users, exchanges, and wallet developers time to prepare.
- Phase B — replacing legacy signatures: In the second phase, Bitcoin may disable ECDSA and Schnorr signatures in favor of post‑quantum‑compatible alternatives. After this change, only transactions using the new signature schemes would be valid, rendering older formats incapable of participating in the network unless they are migrated. The interval between Phase A and Phase B is estimated at around two years, allowing for updates, audits, and ecosystem‑wide readiness.
- Phase C — options for recovery: The third phase remains the most speculative and contentious. It concerns how holders of old addresses will regain access to their coins if they possess the corresponding seed phrases or keys but cannot use legacy formats. Possible approaches include requiring proof of ownership through a new post‑quantum‑based key derivation scheme, temporary “bridge” mechanisms, or special recovery transactions. The exact design, timing, and incentive structure for this phase have not yet been finalized — the BIP remains under discussion, and its implementation is far from guaranteed.
How Many BTC Are Actually Vulnerable?
The 33–34 % figure commonly cited in media stems from academic and industry‑led analyses of the Bitcoin ledger. These estimates indicate that roughly 6–7 million BTC belong to addresses whose public keys are exposed on‑chain, making them theoretically vulnerable if a practical quantum attack becomes feasible. Many of these coins are associated with early Bitcoin history, including early adopters, Satoshi‑era wallets, and legacy contracts. What makes this particularly worrying is that such addresses are often considered “lost” or “dormant,” yet an attacker capable of quantum decryption could unlock them silently and gradually move funds without an immediate market‑shaking crash.
It is important to emphasize that not all vulnerable addresses contain substantial value, and many are already effectively frozen by poor key hygiene or physical loss of hardware. But the volume of coins at potential risk makes the issue tangible for network security rather than a niche corner case.
Why the Community Is Debating Now
Developers and researchers are raising the alarm now for several reasons:
- Quantum computing is advancing faster than expected. While fully fault‑tolerant, large‑scale quantum machines are still years away, the pace of progress in qubit counts, error correction, and specialized algorithms continues to surprise experts.
- Classic cryptography is not quantum‑ready. Bitcoin’s current signature schemes rely on cryptographic assumptions that quantum algorithms can break, which means that proactive migration is safer than reactive panic after a breakthrough.
- Network upgrades require time and consensus. If the community waits until a real quantum threat materializes, it may be too late to coordinate a smooth transition without disrupting wallets, exchanges, and DeFi protocols. A predefined roadmap, like that proposed in BIP‑361, creates a timeline for migration before the situation becomes critical.
- Stealth attacks are possible. Unlike a traditional hack, a quantum attack might not trigger immediate visible alarms; coins can be siphoned off slowly, across many addresses, making the theft harder to detect and attribute. This increases the importance of pre‑emptive protective measures.
How This Affects Ordinary BTC Holders
For average users, the threat may appear distant, but the BIP‑361 framework already has practical implications:
- Legacy wallets need review. Anyone holding long‑term BTC in early‑generation wallets, P2PKH addresses generated by old software, or any address linked to a visible public key should consider migrating funds to modern, SegWit‑ or Bech32‑style addresses that are compatible with future post‑quantum mechanisms.
- Exchanges and custodians must adapt. Major platforms are likely to start internal audits, updating their key‑management systems, and preparing for possible restrictions on legacy formats. Users who keep BTC with custodians should pay attention to their security roadmaps.
- Timeline awareness matters. If the BIP‑361 phases are implemented as proposed, there will be clear windows between phases during which old formats remain operational but are discouraged. Missing these windows could mean inability to spend coins in the new regime, at least until recovery mechanisms are deployed.
Is Protection or Risk Driving the Debate?
BIP‑361’s proposal is far from universally welcomed. Some analysts and community members argue that the measures are too radical for a network that values decentralization, censorship resistance, and minimal intervention. They warn that freezing coins, introducing complex migration rules, and mandating recovery processes might:
- Disrupt users’ expectations of unchangeable ledger history.
- Benefit attackers in edge cases, if the transition is mismanaged.
- Complicate development and reduce the network’s resilience to unforeseen risks.
On the other hand, proponents insist that ignoring quantum threats is a greater risk. The potential exposure of millions of BTC and the possibility of stealthy, systematic theft justify a proactive, multi‑phase plan like BIP‑361. The debate is, in essence, a tension between Bitcoin’s core principles and the practical need for long‑term security against a fundamentally new class of threats.
Practical Steps for Protection
Regardless of whether BIP‑361 becomes fully implemented, several actionable steps can help users protect their BTC:
- Audit your address formats. Identify which BTC‑holding addresses are old‑style P2PKH with visible public keys; preferably migrate those to modern, SegWit, or Bech32 formats.
- Use reputable, up‑to‑date wallet software that participates in discussions of post‑quantum readiness and regularly updates its cryptographic stack.
- Keep backups secure. Seed phrases and hardware wallets should be stored safely; the effectiveness of any future recovery mechanism depends on reliably proving ownership.
- Stay informed about Bitcoin development. Following BIP‑361’s progress, community feedback, and testnet experiments gives a clearer picture of when legacy formats might be restricted and what transitional tools are available.
In summary, the narrative that “old BTC addresses are under threat” is not hyperbole; it reflects a serious, technically grounded concern backed by measurable data and concrete proposals like BIP‑361. The threat is not imminent, but the vulnerability is real, and the community is now in the crucial phase of preparation rather than denial. The coming years will likely determine whether Bitcoin can successfully transition from current cryptographic assumptions to post‑quantum resilience — and whether the holders of early BTC will be protected or left behind.
Publication author
