Justin Drake's "bunker mode" and the Ledger CTO's pushback: what is proposed and how credible it is.

Conclusion

Drake proposes a calm, staged move of funds to addresses whose public keys are still hidden behind a hash. He argues AI-driven maths could break ECDSA "in the worst case in months not years". The threat is an unproven possibility. The precaution itself is cheap and widely accepted. A "mass migration" is what the Ledger CTO disputes, and Vitalik Buterin sits between the two.

What Drake proposes

In his post of 7 Oct 2026 Drake calls on the industry to "calmly begin planning". They recommend a "controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash".

Large and sophisticated holders go first and move the bulk of their funds to addresses that have never signed a transaction.
After signing, a holder should move the remaining funds to a new address, possibly derived from the same seed phrase.
Drake says "Don't rush" and "Don't panic". They say this needs no new cryptography or wallets.
By "break" Drake means fast private key recovery (for example in one week) on available hardware such as a large GPU cluster.

Drake's reasoning

Drake cites recent AI-linked maths results: the n log(n) integer multiplication bound, the 3SUM conjecture and May's disproof of the Erdős unit distance conjecture. They add that "yesterday's OpenAI drop" shows "mathematical superintelligence is upon us". They argue elliptic curves carry rich structure (Schoof, Frobenius, pairings), while hashes are built to minimise it. They also note that an efficient quantum algorithm sometimes foreshadows a classical one. This is a judgment about trends. No attack on secp256k1 has been shown. One summary says no evidence yet that BTC or ETH signatures are broken.

The Ledger CTO's criticism

The Ledger CTO (@P3b7_) replied with these points:

Treating a classical ECDSA break within months as a planning baseline "still looks like FUD".
A practical attack on secp256k1 would not stay confined to Bitcoin and Ethereum. It would also hit TLS, code signing, banking and much other deployed public-key infrastructure.
The same loss of mathematical intuition applies to hash-based schemes too.
Avoiding address reuse after the first signature is a reasonable hygiene step for large holders.
A call for "mass migration" would cause operational mistakes that lose funds with higher probability than the scenario it mitigates. A post-quantum migration is already due, and this adds confusion.

Vitalik's position

Vitalik Buterin wrote: "I don't recommend anyone scramble to move their funds to new wallets today." They still say AI-accelerated maths risks should be taken seriously. They add that AI and quantum are both reasons ECDSA might fall faster than expected, "hence the 'fresh address' recommendation". They flag ML-DSA, FHE and lattices as the main new area of risk. They say hashes are safer than lattices. Secondary reports say the Lean roadmap already prioritises hash-only cryptography such as SPHINCS and WOTS (as summarised here).

How credible is it?

The core risk claim is speculative. It rests on analogy from recent maths results. It offers no concrete attack, and Drake frames it as a worst case. The Ledger CTO's point that a real break would take down far more than crypto is a strong sanity check on the "months" timeline.
The mitigation is low-regret. All three people agree that not reusing addresses after signing is sensible hygiene. The dispute is over scale and urgency. Exposure of public keys matters mainly for addresses that have already signed. Hash-hidden addresses are protected only until their first spend.
The Ledger CTO's operational-risk point is the practical constraint. A hurried mass move raises the chance of lost funds, which Drake also concedes by saying "don't rush".

Reasonable reading

Large holders can quietly adopt fresh-address practice. Retail holders have no need to scramble, as Vitalik also says. The "months not years" timeline remains one researcher's worst case, disputed by Ledger's CTO.

Drake's post · Ledger CTO's reply · Vitalik's reply · The Defiant