Thu., Oct. 22, 2026New York 11:06 p.m. ET · London 4:06 a.m. GMT+1 · Singapore 11:06 a.m. GMT+8NY 11:06p · LDN 4:06a · SGP 11:06a

Le Coin / Protocols & Policy / Security

A small brushed-steel vault capsule closing over a single gold coin on a mint-green surface.

Protocols & Policy · Security

Justin Drake calls for a 'bunker mode' move to fresh crypto addresses, citing AI math gains

Drake says it is now reasonable to brace for the signature scheme behind most bitcoin and ether wallets to break, in the worst case within months, citing AI's progress in math. Critics who answered him on X said he showed no evidence of a break.

Key points

  • The call: Justin Drake wrote that holders, "starting with large and sophisticated ones," should consider moving the bulk of their funds, without rushing, to addresses that have never signed a transaction [1].
  • The reason he gave: He wrote that it is "now reasonable to brace for the possibility" that ECDSA, the signature scheme behind most bitcoin and ether wallets, "breaks before qday, in the worst case in months not years" [1].
  • The pushback: Several cryptography and security voices on X said his post offers no evidence of an attack. The post does not describe one [1].

Justin Drake wants the crypto industry to start hiding its public keys.

In a long post on X at 10:14 a.m. ET on Wednesday, Drake called on "the blockchain industry to calmly begin planning for 'bunker mode'" [1]. His plan is "a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash" [1]. By 11:48 p.m. ET the post had about 2.9 million views, 11,427 likes and 1,188 quote posts [1].

In January, Drake announced the Ethereum Foundation's new post-quantum team on X, writing "We've formed a new Post Quantum (PQ) team" [2]. His X profile reads "Bitcoin security researcher" [1]. Le Coin has not confirmed his current role with the foundation.

What Drake said

His recommendation has two steps. He wrote that holders should consider moving "the bulk of their funds" to addresses that have never signed a transaction, and that after signing from one, they should move what is left to a new address, "possibly generated from the same seed phrase" [1]. He wrote that this "does not require new cryptography or new wallets" [1].

He asked for a slow pace twice. "Don't rush," he wrote, adding that "a rushed migration would do more harm than good," and later: "Again, please do not rush." [1]

His main reason is AI. He wrote that "Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us" [1]. OpenAI's public GitHub repository, created on Oct. 6, holds 722 math manuscripts produced by "an unreleased internal OpenAI model," and it says "Some of the unformalized results could have issues" [4]. Drake defined a "break" as "fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster)" [1].

He said oracles and layer-2 security councils should consider rotating keys with every signed message or adding hash-based signatures such as SPHINCS [1].

What it means in plain terms

A crypto wallet has a private key, which signs, and a public key, which anyone can use to check a signature. The danger Drake describes is someone working backward from a public key to the private key.

Many addresses don't show the public key at first. On Bitcoin, a standard P2PKH address is a hash of the public key. The full public key goes on chain only when the owner spends, alongside the signature [5]. An Ethereum address is the last 20 bytes of a Keccak-256 hash of the public key [6].

So an address that has never sent anything has only exposed a hash. Drake's bet is that hashes will hold up even if elliptic curves don't [1]. There are exceptions. Taproot outputs on Bitcoin put a 32-byte public key in the output itself, not a hash [7]. One post quoted below, from @w_s_bitcoin, told people not to use Taproot wallets.

The background

Most Bitcoin signatures use ECDSA on an elliptic curve called secp256k1 [5]. Taproot spends use a different scheme, Schnorr signatures, on the same curve [7]. Ethereum keys also come from ECDSA [6]. The long-known threat is quantum. In a paper posted in 1995, Peter Shor described a quantum method for factoring and discrete logarithms, two problems that "have been used as the basis of several proposed cryptosystems" [10]. Drake's post does not define "qday." In an interview posted on ethereum.org, asked whether Q-Day is "the day in which quantum computers can break our signature schemes like ECDSA," Drake answered, "Yeah exactly" [12]. NIST has a draft plan for moving off quantum-vulnerable algorithms [9]. In 2024 it published a hash-based signature standard, SLH-DSA, which is based on SPHINCS+ [8].

Drake's new claim is that the break might come from ordinary computers first, helped by AI. He wrote that elliptic curves "carry rich structure," while "hashes are designed to minimise algebraic structure" [1]. He pointed to recent results on integer multiplication, the 3SUM problem and the Erdős unit distance conjecture [1]. None of the three is about elliptic curves.

Ethereum's draft roadmap, maintained by the foundation's architecture team, already lists "centuries-long cryptographic security, via hash-based schemes" as a goal [3]. Drake wrote: "Those timelines must now be revisited and accelerated" [1].

What could change, and for whom

  • Exchanges and custodians. Drake urged "large, sophisticated actors to lead by example" [1]. The five firms he named, Binance, Bitbank, Robinhood, Bitfinex and Tether, would have to decide whether and how to act on his suggestion to "harden their cold storage" [1]. Two posts quoted below, from @coinjoined and @w_s_bitcoin, said exchanges and large institutions are the main offenders on address reuse.
  • Ethereum users. An Ethereum account is built to send many transactions from one address, and a counter called a nonce tracks them [6]. Following Drake's advice there means changing a habit, not flipping a setting.
  • Oracles and layer-2 security councils. Drake said they should consider rotating keys with every signed message or adding hash-based multisig [1].
  • Protocol roadmaps. If more researchers come to share Drake's view, hash-based upgrades on Ethereum and elsewhere could move up the queue [1][3].

What people said on X

These are selected replies and quote posts.

Critics:

Yehuda Lindell (@LindellYehuda), who lists himself as head of cryptography at Coinbase, at 9:01 p.m. ET: "To my understanding, there is no evidence whatsoever pointing to a break of decades old hardness assumptions like elliptic curve cryptography." link

Coinjoined Chris (@coinjoined), who lists himself as co-founder and CEO of Seedor and Bitsurance, at 2:35 p.m. ET: "No new attack is presented here. No complexity bound has changed." He added that "address reuse is bad practice regardless" and that "Exchanges are probably the most conspicuous offenders" link

Chris Ries (@chrisries), who works on post-quantum at Circle per his profile, at 8:26 p.m. ET: "The quantum threat is very real, but must be met with methodical planning and coordination (certainly not 'bunker mode')." link

Dankrad Feist (@dankrad), whose profile lists him as a researcher at Tempo and formerly at the Ethereum Foundation, at 10:29 p.m. ET: "If elliptic curves are broken so that any exposed public key leads to compromise ... your coins are going to zero. Having them in bunker mode is not going to help you." link

@mert, CEO of Helius per his profile, at 8:49 p.m. ET, pitched Zcash and added: "no, do not move your funds no matter what chain youre on" link

Support and middle ground:

@Raullen, who lists himself as a co-founder of IoTeX, at 12:15 p.m. ET: "Fully support Justin's call to action." link

@w_s_bitcoin at 3:31 p.m. ET: "Don't reuse addresses. Most individuals already avoid this; it's mostly large institutions that still do it." The post added: "don't use taproot wallets." link

Both sides agreed on one point: don't reuse addresses. @coinjoined called reuse "bad practice regardless," and @Raullen listed "Stop Reusing Addresses" among his takeaways.

Some answered with jokes.

@GwartyGwart wrote at 5:34 p.m. ET: "I thought bunker mode was when you log off for a year after bullposting eigenlayer" link

These are statements made on X. Le Coin has not verified the claims in them.

What we don't know

  • Whether any of OpenAI's results bear on the math behind wallet signatures. The repository's overview lists number-theory results about elliptic curves and a quantum factoring result, but no entry mentions cryptography, signatures or discrete logarithms [4]. Drake noted the "striking under-representation of cryptographic breakthroughs" among the results and wrote, "Backroom interventionism is my base case" [1].
  • What backs Drake's claim that he has "witnessed first-hand the US government censoring academic quantum cryptanalysis results." He gave no details [1].
  • Whether any of the firms he named will respond, or move funds.
  • Drake's current role. His X profile reads "Bitcoin security researcher," and Le Coin has not confirmed his role with the Ethereum Foundation [1].

Questions and answers

Did Drake say ECDSA is broken? No. He said it is "reasonable to brace for the possibility" [1].

Sources (12)

  1. Justin Drake, X post, Oct. 7, 2026, 10:14 a.m. ET. https://x.com/drakefjustin/status/2107837081313505768 (accessed 11:46 p.m. ET; metrics at 11:48 p.m. ET)
  2. Justin Drake, X post, Jan. 23, 2026, 3:05 p.m. ET. https://x.com/drakefjustin/status/2014791629408784816 (accessed 11:49 p.m. ET)
  3. L1 Strawmap, EF Architecture. https://strawmap.org/ (accessed 11:48 p.m. ET)
  4. OpenAI, openai/math README. https://github.com/openai/math (accessed 11:49 p.m. ET)
  5. Bitcoin Developer Guide, Transactions. https://developer.bitcoin.org/devguide/transactions.html (accessed 11:48 p.m. ET)
  6. ethereum.org, Ethereum accounts. https://ethereum.org/en/developers/docs/accounts/ (accessed 11:48 p.m. ET)
  7. BIP 341, Taproot. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki (accessed 11:48 p.m. ET)
  8. NIST FIPS 205. https://csrc.nist.gov/pubs/fips/205/final (accessed 11:48 p.m. ET)
  9. NIST IR 8547 (draft). https://csrc.nist.gov/pubs/ir/8547/ipd (accessed 11:48 p.m. ET)
  10. Shor, arXiv:quant-ph/9508027. https://arxiv.org/abs/quant-ph/9508027 (accessed 11:49 p.m. ET)
  11. X reactions as linked above (accessed 11:47–11:49 p.m. ET, Oct. 7, 2026).
  12. ethereum.org, "Ethereum's quantum plan Before Q-Day with Justin Drake," interview transcript. https://ethereum.org/videos/ethereums-quantum-plan-justin-drake/ (accessed 11:53 p.m. ET)

Holding the Corner.

Not financial advice.

PublishedOct. 8, 2026, 12:24 a.m. ET

Corrections: none. A correction is a new version with its own hash; the old proof stays up.

Proof slipLe Coin · Protocols & Policy · Oct. 7, 2026
Version
v2 · published
Credits
Checked by Maddox, Copy & Fact AI agent
Published HTML hash
9bf294077167eb52912c81be39e37a1a64db24749075d9b5079e7ef8d82eaa86 On the Proof page
OpenTimestamps
Confirmed in Bitcoin block 971056
Bitcoin tx
b3766b71d5b92d5159366e398b30ac47bd404650ecce77ac77bd01cda830c562

The published HTML hash is the SHA-256 of the article element as served on this page. Proof page

Verify this article

  1. Download both files.

    Article file (.html)Proof file (.ots)

  2. Go to opentimestamps.org. Drop the proof file (.ots) in the box first, then drop the article file (.html) in the second box that appears.

Recorded in Bitcoin block 971056, mined Oct. 12, 2026, 2:54 a.m. ET. See the block on mempool.space

How verification works

Version history (1)

  • v2 · Oct. 8, 2026, 12:24 a.m. ET · published. No earlier version.