Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDragonfly managing partner Haseeb Qureshi argues that moving crypto assets to fresh addresses would not be enough to handle a network-wide failure of digital signatures. He is calling for proactive protocol recovery planning, including a concept he calls “Cryptographic Recovery Mode.” It remains a proposal in the coverage available—not a deployed feature or a plan users can activate.
Why Qureshi says “bunker mode” is incomplete
“Bunker mode” refers here to protecting holdings by moving them to fresh wallets whose public keys are not exposed on-chain. Ethereum researcher Justin Drake recommended gradual migration as preparation for the possibility that ECDSA could break. ECDSA is a digital-signature algorithm; Drake’s warning concerns a potential future failure, not a break that has been demonstrated.
As an Amazon Associate I earn from qualifying purchases.
Qureshi’s objection is about the limits of relying on individual holders to move funds. In a Thursday post on X, as quoted by Cointelegraph, he said “bunker mode” would only protect investors’ coins as long as they were not moved from the fresh address. His broader concern is that a large-scale cryptographic failure could create problems for the network even if some holders successfully migrate—for example, if assets need to be moved again or widespread theft and selling harms the system.
Recommended Free Tools
That is why he is arguing for a network-level recovery plan alongside any steps individual holders might take. The two approaches address different parts of the risk; one is not a substitute for the other.
#1 Best Overall
How the three positions differ
| Position | Scope | What it means for holders |
|---|---|---|
| Justin Drake’s warning | Individual exposure | He said it was reasonable to prepare for a possibility that ECDSA could break before “qday,” with a worst-case timeline of “months, not years,” and recommended gradual migration to fresh wallets with public keys not exposed on-chain. |
| Haseeb Qureshi’s response | Network recovery | He considers address migration an incomplete response to systemic consequences and wants protocols to plan for recovery if conventional signatures fail. |
| Vitalik Buterin’s caution | Migration risk | The Block reported that Buterin agreed the risk merits attention but cautioned against rushed migrations, since mistakes during upgrades can cause losses. |
Drake’s phrase “months, not years” describes a worst-case warning, not a prediction that a break is imminent. CoinDesk reported on October 8, 2026, that no practical attack had been demonstrated at the time. The coverage does not establish that AI has broken ECDSA or crypto wallets.
What “Cryptographic Recovery Mode” would involve
Cointelegraph describes Qureshi’s idea as a hash-based backup-signature plan: users would map a backup to their addresses, and validators could force recovery if ordinary signatures were broken. In principle, that shifts some response from each wallet holder to the protocol itself.
The description is not a technical specification. The coverage does not establish the proposal’s security assumptions, governance rules, deployment path, or how it would handle failure. Without those details, it is not possible to assess how recovery would be authorized or what trade-offs it might create. Treat the name as a reported concept, not a setting in a wallet or an available safety feature.
What the reported Bitcoin exposure figures do—and do not—show
Cointelegraph reported these 2026 estimates, attributing them to Glassnode:
| Reported estimate | Exposure category described | Attribution and qualification |
|---|---|---|
| 6.26 million BTC | Addresses described as potentially vulnerable | Cointelegraph attributed the estimate to Glassnode; it is a reported estimate, not an independently verified count. |
| 4.33 million BTC | Address-reuse exposure | Cointelegraph attributed the estimate to Glassnode and reported that moving these coins to a fresh address would end this particular exposure. |
| 1.94 million BTC | Exposure associated with address format | Cointelegraph attributed the estimate to Glassnode; the coverage does not establish more detail about this category here. |
These are exposure estimates, not evidence that the coins have been stolen or that an attack is imminent. The categories should not be added together as though they were independent counts; the reporting does not establish that they are mutually exclusive.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What holders should take from the warnings
- Do not confuse a warning with an incident. Drake described a possible future cryptographic failure, and the cited coverage reported no practical attack at the time.
- Do not treat an address move as a system-wide fix. Migration aims to reduce exposure for particular holdings; Qureshi’s proposal concerns recovery if ordinary signatures fail.
- Avoid panic-driven transfers. Buterin’s reported caution matters because mistakes during rushed wallet moves can themselves cause losses.
- Do not rely on an unimplemented proposal. Cryptographic Recovery Mode is not shown as available, and the details needed to judge its safety and governance have not been established.
The practical distinction is between preparing carefully at the holder level and building a recovery process at the protocol level. The current coverage describes a debate over those approaches—not a confirmed cryptographic break or an urgent instruction to move funds.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
