Dragonfly managing partner Haseeb Qureshi criticized Ethereum researcher Justin Drake’s recommendation to enter “bunker mode,” arguing that migrating tokens to fresh addresses is an ineffective defense against artificial intelligence breaking cryptographic signatures. In a Thursday post on X, Qureshi labeled the strategy “cryptographic doomerism,” noting that coins moved to new addresses would remain worthless if the broader network suffered mass hacks and sell-offs. Instead, he proposed a “Cryptographic Recovery Mode,” a hash-based backup signature plan allowing validators to force recovery if standard signatures are compromised.
The debate follows Drake’s Wednesday warning that rapid AI advancements could break the elliptic curve digital signature algorithm (ECDSA) securing cryptocurrency wallets sooner than expected, potentially within months rather than years. This concern cites a Tuesday OpenAI report on AI progress in mathematics. Data from Glassnode indicates that more than 31% of the Bitcoin supply, or 6.26 million BTC, sits in vulnerable addresses. Of this exposed amount, 4.33 million BTC is at risk due to address reuse, while 1.94 million BTC is exposed through its address format. Nearly 1.8 million BTC of the total exposed supply is held on cryptocurrency exchanges, where 57% of all balances are currently vulnerable. Vitalik Buterin acknowledged the seriousness of AI-accelerated math risks but advised against rushing to move funds.
The disagreement between Dragonfly’s Haseeb Qureshi and Ethereum researcher Justin Drake highlights a critical divergence in how institutional actors perceive immediate versus systemic threats to blockchain security. While Drake’s “bunker mode” focuses on individual asset preservation through address hygiene, Qureshi’s critique underscores the fragility of isolated defenses in a network-wide compromise scenario. By proposing a “Cryptographic Recovery Mode,” Qureshi shifts the burden from user behavior to protocol-level resilience, suggesting that infrastructure must adapt proactively rather than relying on reactive user migrations. This perspective aligns with institutional needs for predictable, validator-enforced safeguards rather than ad-hoc wallet management strategies.
