Community Trust ScoreVerified
What happened
Changpeng Zhao — better known as CZ — floated a pretty provocative idea recently. Speaking on the Galaxy Brains podcast, he raised the possibility of freezing Satoshi Nakamoto’s Bitcoin, along with other dormant coins sitting in addresses considered vulnerable to quantum computing attacks. He didn’t call for an immediate seizure. He didn’t claim Binance would act unilaterally. But he put the idea squarely in front of the Bitcoin community: a potential network upgrade that would lock coins in quantum-vulnerable addresses if those coins stay inactive past a set deadline. The proposal landed like a grenade in a community that’s spent fifteen years treating immutability as sacred.
Quantum computing is the backdrop here. The concern isn’t abstract anymore — advances in the field have been rapid enough that cryptographers are genuinely worried about the timeline for breaking elliptic curve cryptography, the math that secures Bitcoin private keys. If a sufficiently powerful quantum machine can derive a private key from a public key, coins sitting in exposed addresses become targets. Satoshi’s estimated holdings, unmoved since the early days, sit in exactly those kinds of addresses.
No one’s cracked Bitcoin yet. But the direction of travel is clear enough to make people nervous.
The historical context
Bitcoin has faced existential-feeling moments before. Back in 2013, a software bug caused a blockchain fork — the ledger briefly split, and the community had to coordinate fast to resolve it. Developers and miners moved quickly, and the crisis passed. It wasn’t elegant, but it worked, and it showed that consensus-driven emergency response was possible on a decentralized network.
The more uncomfortable parallel is Ethereum’s DAO hack in 2016. A vulnerability in a smart contract let an attacker drain roughly a third of The DAO’s funds. Ethereum’s community faced a brutal choice: let the theft stand in the name of immutability, or execute a hard fork to reverse it. They forked. A minority refused, kept the original chain alive, and Ethereum Classic was born. The split never fully healed.
CZ’s proposal echoes that same fault line. It’s not just a technical question about quantum resistance. It’s a values question about whether the network can — or should — intervene in the fate of coins that haven’t moved in years. The DAO debate was messy and divisive. This one probably will be too.
Why it matters
The stakes aren’t small. Satoshi’s coins alone represent billions in value at current prices, and the broader pool of dormant, quantum-exposed addresses is larger still. A preemptive freeze could, in theory, protect that value from an attacker who cracks the cryptography before the network upgrades its defenses. That’s the case for acting.
But the case against is just as serious. Bitcoin’s appeal has always rested partly on the idea that no one can touch your coins without your keys. A network-level decision to lock addresses based on inactivity or vulnerability cuts against that directly. It doesn’t matter if the intent is protective — the precedent is what people are worried about. If the community agrees to freeze dormant coins once, what stops a future majority from doing it again under different circumstances?
CZ himself acknowledged the technical difficulty here. Distinguishing Satoshi’s coins from those of other early miners isn’t straightforward. The cryptographic signatures that secure Bitcoin transactions don’t come with labels. Any mechanism that targets long-inactive addresses could catch legitimate long-term holders who simply haven’t moved their coins in years, people who chose cold storage and haven’t touched their wallets since 2012. That’s not a minor edge case. That’s potentially a lot of people.
The fairness problem is real, and it’s probably the hardest part of the whole debate.
What to watch
A few things will determine where this goes.
Quantum computing progress is the most important variable. Specifically, if Google’s quantum hardware crosses the 500,000 qubit threshold, the pressure on Bitcoin developers to act will become much harder to ignore. That number has circulated as a rough benchmark for when the threat becomes acute, and it’s worth tracking closely.
On the Bitcoin side, watch the Bitcoin Improvement Proposal process. If something like BIP-361 gains serious traction in developer forums, that’s a sign the technical community is moving toward formalizing a response. BIPs that attract sustained attention from core developers tend to eventually find their way into implementation, even if the path is long and contentious.
Legal developments matter too. There’s an ongoing lawsuit in New York where plaintiffs are seeking to claim ownership of dormant Bitcoin addresses. If a court rules in favor of the plaintiff, it could reshape how the community thinks about idle coins — and potentially add legal pressure on top of the technical and philosophical pressure already building. A ruling like that wouldn’t force a network change, but it would change the conversation significantly.
The community’s reaction to Zhao’s comments has already been mixed, which is probably the expected outcome. Some developers see quantum resistance as an urgent engineering problem that the network needs to solve proactively. Others see any proposal to lock or freeze coins as a fundamental betrayal of what Bitcoin is supposed to be. Both camps have serious people in them.
Satoshi’s own writing touched on this indirectly. The idea that lost coins benefit the network by making remaining coins more scarce reflects a hands-off philosophy that’s been baked into Bitcoin culture from the start. CZ’s proposal challenges that directly. And the community hasn’t found consensus on much harder questions than this one.
Hub: Bitcoin price, news, and analysis
BIP-361 hasn’t formally passed any threshold of adoption.
