Justin Drake’s “bunker mode” warning is a precautionary proposal, not a claim that ECDSA has already been broken. He says recent mathematical advances associated with OpenAI could make classical private-key recovery possible sooner than expected—possibly within months—and urges holders to move funds calmly to fresh addresses whose public keys remain hidden behind hashes. He recommends large holders move funds to addresses that have never signed, then move remaining funds after a spend; he also suggests key rotation and hash-based signing for critical systems. His proposed longer-term direction is post-AI cryptography built on hash functions such as SHA or BLAKE. Drake’s post

$BTC$ETHOct 7, 2026, 17:35 UTC

He mentions OpenAI; mathematician Ewin Tang; Project Eleven and its Bitcoin “risq list”; exchanges Binance, Bitbank, Robinhood and Bitfinex; stablecoin issuer Tether; Ethereum’s draft Strawmap roadmap; SPHINCS; and a planned London Q&A hosted at Ethereum Institutional. The Strawmap describes itself as a work-in-progress Ethereum L1 roadmap maintained by EF Architecture, while Project Eleven’s page describes its tracker as a list of Bitcoin addresses at risk of quantum attack. Strawmap · Project Eleven Risq List

Drake specifically cautions against rushing: he says the migration is preventative and that a rushed move could do more harm than good. The post does not establish that ECDSA has been broken or that its projected timeline will occur. Drake’s post

Ask your own

Case file

$BTCBitcoin, bitcoin

$ETHEthereum, ethereum

Answered Oct 7, 2026, 17:35 UTC

Sources 3

Drake’s postx.com
Strawmapstrawmap.org
Project Eleven Risq Listbitcoin-risq-list.projecteleven.com

Research trace 12

The page leviathannews.xyz
The page www.theblock.co
The supplied post already gives the warning and names the projects and organizations. I’ll verify the complete wording and attribution in the original post so the summary can distinguish Drake’s claims from established facts.
The original post confirms Drake’s wording and attribution. This step checks the referenced tracker and Ethereum roadmap, and whether Drake’s account supplies context for the post’s claims.
The post and supplied material identify the warning and named organizations. This step checks the two linked resources so I can describe their roles without treating Drake’s security forecast as an established finding.
The source post and linked resources are confirmed; the post names several exchanges, a stablecoin issuer, a cryptography scheme, and a London event. I’ll check Drake’s recent posts for any clarification or correction that changes how those references should be understood.
The original post and the linked pages identify the warning and its references. I’ll check the exact post text around the proposed mitigations and named parties to complete the inventory accurately.
The original post and supplied material identify the warning and named entities. I’ll check independent reporting for context on whether the warning is being presented as a forecast or as evidence that ECDSA has already been broken.
The original post and its named references are clear, but the warning’s premise is Drake’s forecast. I’ll check a first-party Ethereum security resource and independent technical commentary to distinguish that forecast from current guidance.
The original post contains the warning and its named references. I’m checking first-party Ethereum guidance for context on whether Drake’s forecast is an established present-day risk.
The original post gives the warning and its named references. I’ll check whether Ethereum’s draft roadmap and Project Eleven’s tracker say what Drake describes, to clarify which projects and organizations he mentions.
The original post already sets out Drake’s warning and names the relevant projects and organizations. The supplied text and the original X post provide enough evidence to answer the question directly.