Crypto is solving the wrong quantum problem. The real risk is authentication traffic, not dormant wallet keys.
Fixing dormant wallet keys is a one-time migration. Harvesting authentication traffic is ongoing, and attackers don't need quantum computers yet to collect it.
CryptoVibe Desk · quantum computing · post-quantum cryptography · exchange security
- →Gault argues crypto's quantum debate focuses on dormant wallet keys while exchange authentication traffic may already be collected for future decryption.
- →A cracked exchange signing credential is a one-to-many attack, giving access to thousands of transactions per hour rather than a single wallet.
- →Watch for a top-five exchange to commit to post-quantum authentication upgrades before Google's 2029 migration target, now three years out.
- store-now-decrypt-later → Attackers record encrypted data today and wait until quantum computers are powerful enough to break the encryption and read it later.
- post-quantum cryptography → Encryption methods designed to resist attacks from quantum computers, which can break the math behind most encryption used on the internet today.
- TLS → The encryption protocol that secures data sent between servers, including all authentication and signing traffic between exchanges, bridges and custodians.
- ML-KEM / ML-DSA → The two post-quantum cryptography standards finalized by NIST in 2024, designed to replace classical key exchange and digital signatures in internet protocols.
The quantum threat to bitcoin has a standard model. Dormant addresses with exposed public keys get cracked first. Roughly 6.9 million BTC sits in those addresses, per CoinDesk. The proposal: migrate those keys before a quantum computer arrives, or lose the coins.
That's the wrong layer to focus on first, according to Andrew Gault. The ZeroTier CEO and founding partner at 7percent Ventures made the case today. Authentication traffic between exchanges, bridges and custodians is the more urgent problem. That traffic runs on the same public-key cryptography a sufficiently powerful quantum computer would break. Unlike dormant wallet keys, that traffic is being generated continuously, right now.
Security researchers call this a store-now-decrypt-later attack. An adversary doesn't need a quantum computer today. They need network access and storage today, and quantum hardware at some point in the future. TLS handshakes, session tokens, API signing keys, withdrawal authorizations: all of it travels encrypted over the wire. Some of it is quietly being collected right now.
The engineering analogy is a cache poisoning problem with a very long TTL. The poisoned data is already in an adversary's cache. The expiry date is whenever quantum hardware gets good enough.
What makes authentication traffic more exposed than dormant wallet keys is the blast radius. A cracked wallet key gives an attacker one address. A cracked authentication credential for a hot wallet or bridge signing key gives access to a system processing thousands of transactions per hour. At the infrastructure level, this is a one-to-many problem, not one-to-one.
The Global Risk Institute puts the probability of a cryptographically relevant quantum computer at 19% to 34% by 2034, per CoinDesk. That range sounds uncertain enough to defer. But Google has set a 2029 post-quantum cryptography migration target for its own infrastructure. The team that built and maintains the web's TLS stack treats this as a three-year problem, not a decade problem.
One modeled scenario puts a quantum breach of a top-five U.S. bank at a $2 trillion to $3.3 trillion Fedwire cascade, the same report found. The same model estimates a 10% to 17% GDP decline. These numbers come from a single modeled scenario, not observed data. But the order of magnitude is the point: at the infrastructure layer, the threat model isn't someone losing their coins. It's settlement stopping.
CoinDesk notes Ethereum has begun a coordinated post-quantum migration. Bitcoin hasn't. Neither, publicly, have most major exchanges or bridge operators.
That asymmetry is where Gault's argument lands. Wallet-level migration is visible and quantifiable. Authentication stack migration is quieter, technically distinct, and apparently lower on the priority list.
Post-quantum authentication is not theoretical tooling. NIST finalized ML-KEM (key encapsulation) and ML-DSA (digital signatures) in 2024. Both work as drop-in replacements in TLS 1.3. Migrating to them requires a software update and a deployment window, not a protocol fork. The engineering lift is real but bounded.
If you're a developer at an exchange, bridge or custodian, the question isn't whether your users' keys are safe. It's whether your authentication stack is running ML-KEM or equivalent. Most aren't, and most haven't committed to a timeline.
Ethereum's migration sets a precedent. Whether the rest of the ecosystem treats this as a separate problem on a longer timeline is the open question. Right now, it looks like a longer timeline. That's the catch.
Coinbase and Binance's silence on post-quantum TLS timelines, while Google targets 2029 for its own migration, is an engineering gap that will only get harder to close the longer it runs.
Watch for a top-five CEX to commit to post-quantum authentication migration before Q4 2027, which would show the industry is treating the harvest window as active rather than theoretical.
Primary links and supporting reads used by the desk for this story.
Forward this.
