Imagine owning bitcoin without knowing it has already been stolen. That scenario is what makes the quantum threat different from any other, and it's why a single remark from Changpeng Zhao has ignited the deepest debate Bitcoin has seen in years.
The question that follows is uncomfortable, and it isn't really about Satoshi. It's about what Bitcoin is willing to sacrifice of itself to survive.
What CZ said
On June 18, appearing on the Galaxy Brains podcast, the Binance founder floated the idea of freezing Satoshi Nakamoto's 1.1 million bitcoin, worth roughly $68 billion, if they remained untouched once quantum computers threaten the network's cryptography.
The idea: give a six-to-twelve-month window to move them after any upgrade, then let the community decide whether to lock the vulnerable addresses. CZ quickly clarified that he has no power to do this alone: it would take a fork approved by the network. His point remains sharp, though: "If we do nothing, we're effectively handing them to whoever hacks them."
Why the quantum threat is real
The vulnerability is technical and precise. Bitcoin's earliest addresses, including Satoshi's, use a format that exposes the public key on the blockchain. A sufficiently powerful quantum computer could, in theory, derive the private key from it and empty the wallets. In March 2026, a paper from Google Quantum AI, co-authored by a researcher from the Ethereum Foundation, cut the estimated computing power needed to pull it off by a factor of twenty.
Today, roughly a third of Bitcoin's supply is potentially exposed. And here's the chilling detail: an attacker would never announce their capability. They would compute the keys and drain the wallets slowly, silently, to avoid giving themselves away. The so-called Q-Day might only become clear months later. You might never know your bitcoin is already gone. It's the same reason controlling your own keys remains the most sensitive issue of all.
Four responses, no consensus
How the community is splitting over the problem. Source: CoinDesk and expert statements, July 2026
1. Freeze, the CZ approach and BIP-361
Mandatory migration, then vulnerable coins that haven't moved get locked. Priority: network security.
2. Do nothing, Terpin's position
A one-off crash is survivable, a precedent that allows coins to be seized is not. Priority: inviolable ownership.
3. The legal trust, Carter's proposal backed by Hougan
Put Satoshi's coins in a trust until ownership is proven. Priority: compromise.
4. Migrate everyone, Lopp's point
The real issue isn't Satoshi, it's moving the whole ecosystem to post-quantum cryptography before Q-Day. Priority: preparedness.
The real dilemma: two promises that no longer hold together
This is the point that goes beyond the headlines. Bitcoin was built on two promises: it's yours, no one can take it from you, and it's secure. The quantum threat puts those promises on a collision course. Freezing the vulnerable coins betrays the first. Doing nothing betrays the second. For the first time, Bitcoin may have to choose which of its foundations to sacrifice.
Michael Terpin puts it bluntly: if the coins were sold, the market would absorb a one-off shock, but it wouldn't survive a precedent that allows someone else's property to be locked away. Matt Hougan of Bitwise adds the more cynical, and perhaps truer, observation: the market already treats Satoshi's coins as frozen forever, so any intervention is riskier than doing nothing. It's a choice that goes to the heart of decentralized governance.
What happens now
The good news is that it's still theoretical. Ark places the current moment at "Stage 0": quantum computers exist, but none has meaningful capability yet. The formal proposal on the table is BIP-361, which lays out a three-phase migration with legacy signatures locked out after five years. But there's no consensus, and no date.
It's also the first real stress test of Bitcoin's governance since SegWit, which took several years to resolve. And it comes in an already fragile year, with the price under pressure. This time, the hardest test may not be writing the code, but deciding which promise to keep. The documents remain available in the official Bitcoin Improvement Proposal repository and in the post-quantum standards from NIST.
