A new Bitcoin Improvement Proposal, BIP-361, is taking aim at wallets still secured by legacy signature schemes that quantum computers could eventually crack. The text, surfaced this week, would block new BTC from being sent to quantum-vulnerable addresses, sunset legacy signatures after a five-year transition window, and potentially introduce a recovery mechanism for users who fail to migrate in time.
Why it matters
The proposal lands in a quieter corner of the Bitcoin conversation but addresses a long-flagged tail risk. Roughly a quarter of all BTC sits in legacy address types vulnerable to a sufficiently powerful quantum attacker, including coins tied to Satoshi-era wallets that may never move. BIP-361's architects are betting the community will treat that exposure as urgent enough to justify a coordinated, network-wide migration rather than waiting for a crisis to force one.
Market impact
A hard timeline changes user behaviour before it changes protocol. Custodians, exchanges, and wallet vendors would face a deadline to push upgrades or risk losing the ability to receive funds, and dormant legacy holders would get a finite window to act. Whether the recovery mechanism survives community review is the open question, since it cuts against Bitcoin's no-rollback ethos and will draw the loudest objection from purists. Watch the BIP editor and core developer forums for the first substantive pushback.
Frequently asked questions
-
What does BIP-361 actually propose?
BIP-361 would block new BTC from being sent to quantum-vulnerable addresses, sunset legacy signatures after a five-year transition window, and potentially introduce a recovery mechanism for users who fail to migrate in time.
-
Why is quantum security a concern for Bitcoin?
Legacy Bitcoin signature schemes could be broken by a sufficiently powerful quantum computer. Roughly a quarter of all BTC sits in address types considered vulnerable, including coins in dormant Satoshi-era wallets.
-
How long would the migration window be?
The proposal outlines a five-year transition period before legacy signatures are sunset entirely, giving custodians, wallet vendors, and individual users a hard deadline to upgrade.
-
What is the recovery mechanism in BIP-361?
The draft includes a potential recovery path for users who miss the migration deadline, though the specific design is still open and is expected to draw the heaviest community pushback.
-
Would BIP-361 require a Bitcoin hard fork?
Changing which address types can receive funds and retiring legacy signatures at the protocol level would require a network-wide upgrade, the exact form of which remains under discussion among core developers.
TheBlock
CoinDesk
CryptoSlate
WatcherGuru
Glassnode