Hoskinson Warns Quantum Threat Could Expose 34% of Bitcoin by 2030s

Charles Hoskinson deployed what can only be described as a TED talk's worth of existential dread this week, delivering a long-overdue reality check aimed squarely at Bitcoin maximalists—and the quantum computing threat he insists is no longer science fiction dressed up as theoretical cryptography. As of March 1, 2026, over 34% of all Bitcoin has public keys exposed on-chain, either through address reuse or legacy pay-to-public-key-hash formats. We're talking roughly 8 million Bitcoin sitting ducks, ripe for the picking by whoever gets their quantum hands on a powerful enough machine. Based on current research timelines, Hoskinson sees this particular boogeyman arriving sometime in the 2030s. "Not hypothetically one magical day in the future when unicorns fart rainbows," he said. "In the 2030s. Right in front of your face."

Enter BIP-361, the Bitcoin Improvement Proposal currently making the rounds like a half-baked cure for a terminal illness. The proposal attempts to address the vulnerability by freezing quantum-vulnerable funds and forcing a migration to post-quantum addresses. Hoskinson spent a considerable portion of his video dissecting why he believes it fails spectacularly on its own terms. The proposal claims to be a soft fork. Hoskinson says that's a generous interpretation. It would require a hard fork—Bitcoin's equivalent of jumping out of a moving car—and Bitcoin has never done one, mostly because its maximalist community treats the mere suggestion as heresy. More critically, the proposed zero-knowledge proof recovery system only works for wallets built on the BIP-39 seed phrase standard, which wasn't even introduced until 2013. Approximately 1.7 million Bitcoin—including an estimated 1.1 million belonging to the perpetually missing Satoshi Nakamoto—exist in legacy wallet formats predating this standard. There is no zero-knowledge proof magic wand that can recover those coins. "1.7 million coins cannot be saved even under the steal your coins proposal," Hoskinson noted with characteristic bluntness.

Credit where it's due: Hoskinson acknowledged the proposal isn't completely useless. The developers who wrote it clearly understand the stakes, because if nothing happens, those 8 million Bitcoin will absolutely be stolen and dumped onto the market in the 2030s—think 8% to 10% of the entire supply hitting exchanges simultaneously like a crypto-themed flash crash. "I understand why they wrote it," he said. "Because if they don't do this, that money will be stolen in the 2030s. That's a fact." The real problem, as Hoskinson sees it, is Bitcoin's governance structure—or rather, the catastrophic absence of one. Cardano, Polkadot, and Tezos all have on-chain governance mechanisms that let communities vote on protocol changes in a structured way. Bitcoin does not. Every attempt to introduce meaningful upgrades has been fought off in the name of immutability dogma. "If you had on-chain governance you could solve it," Hoskinson said. "We have it at Cardano. But we're shitcoiners. We don't have good ideas."

Hoskinson closed with a scenario that should make any Bitcoin holder who celebrated institutional adoption feel distinctly uneasy. BlackRock, MicroStrategy, and the US government are now significant Bitcoin holders—some of the biggest fish in the pond, in fact. All three have fiduciary or political obligations to protect the value of their holdings. If 10% of the Bitcoin supply faces quantum theft in the 2030s, those institutions will not simply shrug and accept their losses. They have the resources and the very real incentive to push through a hard fork whether the Bitcoin community wants one or not. "Do you think BlackRock is going to have a problem stealing 1.7 million Bitcoin from people and forcing a hard fork?" he asked. "You welcomed them in with open arms." The community that spent fifteen years resisting change to protect decentralization may discover that the institutions it embraced with such enthusiasm are precisely the ones who ultimately force the change anyway—and probably file the paperwork in triplicate.