AI Math Breakthroughs Spark 'Bunker Mode' Warnings Over Bitcoin/Ethereum ECDSA Security

Bitcoin and Ethereum addresses are derived from public keys by hashing them, so as long as a wallet has never spent from an address, its public key stays hidden behind that hash. The moment a transaction is signed, the public key is published on-chain and becomes a fixed target for anyone who can solve the elliptic curve discrete logarithm problem underlying ECDSA. Justin Drake's 'bunker mode' proposal is built entirely around this exposure gap: his specific recommendation was 'to set in motion a controlled mass migration of assets to fresh addresses' ^[1]that have never signed a transaction, keeping their public keys off-chain and unreachable until the owner chooses to spend. The scale of what's already exposed is the real motivator - research firm Project Eleven's 'Bitcoin Risq List' put the amount of BTC sitting in addresses with visible public keys at over 8.17 million coins as of mid-September 2026, with an earlier estimate putting it at 6.04 million BTC, roughly 30% of circulating supply ^[2]. That's the pool of funds bunker mode is trying to shrink before any theoretical break happens, not after.

The event that triggered the entire scare wasn't a cryptography paper at all. On October 6, 2026, OpenAI published 722 new mathematical manuscripts, representing 372 distinct result families, produced by an internal frontier model without any math-specific tooling ^[3]. Drake's own framing leaned hard on that moment, describing 'mathematical superintelligence' and arguing that 'recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen.' But as CryptoSlate's coverage of the same announcement noted plainly, 'OpenAI's announcement does not report a practical attack on ECDSA or RSA' ^[4]. Nothing in the release claims to have found a faster algorithm for the elliptic curve discrete logarithm problem, broken a hardness assumption, or recovered a single private key. The entire 'break ECDSA in months' scenario is Drake's extrapolation from general-purpose mathematical progress to a specific, undemonstrated cryptanalytic capability - a distinction that becomes the crux of the industry fight that follows.

The response split the industry almost immediately. Coinbase's head of cryptography, Yehuda Lindell, rejected the warning outright: 'Making such statements without any evidence is the opposite of responsible behavior. It is the very definition of FUD,' arguing that AI solving open conjectures says nothing about whether the specific hardness assumptions behind elliptic-curve cryptography have actually weakened ^[5]. Dragonfly Capital's Haseeb Qureshi took the opposite position, framing Drake's call as a reasonable precaution rather than fear-mongering ^[1]. Vitalik Buterin landed in between: he explicitly validated the underlying risk - 'we should take the risks to cryptography from AI-accelerated math seriously' - while opposing Drake's urgency on process grounds, not substance, noting 'I personally have lost more money in botched migrations than I have lost in all hacks combined' ^[9]. That same tension - credible researchers agreeing the risk is real while disagreeing sharply on whether to act now - also showed up across the community reaction to the story. Crypto-native audiences were openly skeptical of the 'months' timeline, repeatedly pointing back to Lindell's rebuttal as the more credible read and framing the deeper takeaway as a long-term risk worth tracking rather than an emergency, while it was mainly secondary media amplification and retail-facing commentary that pushed the framing toward something closer to panic.

Buterin's response didn't just soften Drake's urgency - it widened the threat model. He warned that AI-accelerated mathematical progress could threaten the lattice-based schemes (ML-DSA, Falcon) that the Ethereum research community had been treating as the safe post-quantum successor to ECDSA: 'So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe,"' ^[1]he wrote, concluding that hash-based signature schemes should be preferred wherever practical, since their security rests on far more conservative assumptions than lattice problems. That reframing landed just before Ethereum's second annual post-quantum research retreat, scheduled for October 9-12, 2026 ^[4]- timing that turned an X thread into an agenda item. It also lines up with unease already voiced by Bitcoin-ecosystem cryptographer Jonas Nick, who said plainly: 'We know the elliptic curve is broken. This makes me uneasy' ^[2]- a reminder that ECDSA's eventual obsolescence was never really in dispute, only its timeline and what should replace it.

Strip away the rhetoric and the quantitative case rests on two separate curves converging, not one single breakthrough. On the quantum side, a March 2026 analysis from Caltech and Google Quantum AI found that breaking 256-bit elliptic curve cryptography could require roughly 20 times fewer quantum resources than a 2019 estimate - under 500,000 physical qubits instead of the prior benchmark ^[6]. Security researchers were already warning by May 2026 that AI itself was accelerating that quantum research, with Project Eleven's CEO Alex Pruden noting that 'AI is definitely being used to accelerate the development of quantum computing,' and NEAR co-founder Illia Polosukhin arguing that any sensitive data put online today should be assumed decryptable within a couple of years ^[7]. Drake's own estimate, cited separately, puts at least a 10% chance that a quantum computer recovers a secp256k1 private key from an exposed public key by 2032 ^[8]. None of those figures involve a demonstrated classical break of ECDSA via AI - they are quantum-timeline estimates that predate this week's math-breakthrough scare by months. What Drake's October 7 warning actually did was graft a new, faster-moving AI risk onto an already-shortening quantum clock, which is why the reaction felt urgent even though the evidence for an imminent classical break is, by multiple accounts, still exactly zero.