In the hush of a sideways market — the kind where patience itself becomes a currency — a warning landed that had nothing to do with charts. Samson Mow, the Jan3 CEO and former Blockstream CSO who stood beside El Salvador's president when bitcoin became legal tender, urged the network not to rush its post-quantum signature transition.
It sounds, at first, like the standard caution of a conservative developer. Another voice saying "slow down" in a culture that worships acceleration. But Mow is not a marginal figure. He has been inside the machinery of bitcoin adoption for a decade — from his work on Liquid to his role in the most daring sovereign adoption experiment in modern history. When he says "don't rush," the sentence carries the weight of someone who has watched hasty upgrades fracture communities and careful ones compound trust.
That warning deserves more than a headline. It deserves a technical excavation. Because beneath it lies a question that will define Bitcoin's next decade: how do you upgrade the mathematical signature that defines ownership on the world's oldest blockchain without breaking the trust that holds it together?
I have spent years in cryptography, and I have learned that the most dangerous decisions in this industry are rarely made too slowly. They are made too quickly, in service of momentum rather than comprehension. From code audits to community heartbeats, I have watched projects sacrifice durability at the altar of speed.
Let's establish the technical substrate before we weigh the warning.
Bitcoin transactions are secured by ECDSA — the Elliptic Curve Digital Signature Algorithm — implemented on the secp256k1 curve. It is a masterpiece of applied mathematics: compact signatures of roughly seventy bytes, verification in microseconds, robust against decades of cryptanalytic assault. It has silently guarded hundreds of billions of dollars in value since 2009.
Quantum computing changes the security calculus. In the late 1990s, Peter Shor demonstrated that a large-scale quantum computer could solve the elliptic curve discrete logarithm problem — the mathematical bedrock of ECDSA — in polynomial time. If such a machine were ever built at scale, private keys could be recovered from public keys. Bitcoin's ownership model would collapse like a house of cards in a hurricane.
But "if" is the operative word. While headlines scream about "quantum supremacy," the reality is that useful, error-corrected quantum computation at the scale required to break secp256k1 remains an estimated ten to twenty years away — and some cryptographers believe that projection is optimistic. The gap between the real threat and the media-fanned panic is the space where this entire debate breathes.
Meanwhile, NIST has spent the last decade preparing the industry's escape route. In 2024, the institute finalized post-quantum signature standards: ML-DSA, grounded in lattice cryptography, and SLH-DSA, built on hash-based constructions. These are serious, peer-reviewed primitives. But moving from NIST standardization to bitcoin's adversarial production environment is not a software update. It is a geological shift.
Here's the problem nobody wants to put on a billboard: post-quantum signatures are enormous compared to ECDSA. Lamport and Winternitz signatures — the classic hash-based schemes with the cleanest security proofs — generate signatures one to two orders of magnitude larger than ECDSA's seventy bytes. Verification costs scale accordingly. On a network where every byte of block space is contested economic territory, where fee pressure is already a live social issue, this is not an implementation detail. It is a change in the fundamental economics of transacting. A tenfold or hundredfold increase in signature size doesn't just raise fees. It shifts who can participate. The dream of a network where a grandmother in a village can transact without intermediaries gets harder to sustain if every signature consumes five kilobytes.
This is where the mathematical layer of Mow's warning becomes concrete. Post-quantum schemes exist on paper, but their behavior under adversarial conditions — under live attacks, under emergent economic incentives — is still uncharted territory. The security proofs are sound, but proofs and practice have a messy relationship. A migration to a young, imperfectly battle-tested scheme is a moment of maximum vulnerability. In bitcoin's history, the most damaging bugs have not come from the depth of the math but from the shallowness of the real-world testing.
Now consider the coordination burden. This is the dimension that the market analysis and the price charts completely miss. A signature migration touches every wallet, every exchange, every node operator, every custody provider, every hardware wallet manufacturer, every block explorer, every indexer. The number of software systems in the bitcoin world that validate ECDSA signatures runs into the tens of thousands. Each one needs to be updated, tested, audited, and deployed with the infrastructure that surrounds it.
I have lived this reality. During the 2020 DeFi Summer, I founded the Mumbai Chain Guardians — a volunteer network of 200 moderators who monitored Aave and Compound for vulnerabilities. What I learned then is that the bottleneck in any protocol migration is rarely cryptographic and almost always human. The uncertainty, the confusion, the fear that gathers when users sense the ground shifting beneath their assets — that is the storm that causes panic sell-offs, not the math. My team prevented a potential panic during the April crash not because we explained the code, but because we translated it into language people could hold onto. Trust is not a protocol; it is a practice.
There is also a governance dimension that deserves its own paragraph. Bitcoin changes only through the BIP process — a deliberately adversarial, transparent mechanism that permits the widest possible scrutiny. SegWit, the canonical upgrade, took more than two years to move from proposal to activation, and even then it sparked a civil war in 2017 that nearly tore the community apart. The truth is that bitcoin's "code is constitution" culture makes hasty upgrades structurally impossible. And that is by design. Auditing the soul behind the smart contract means understanding that the social layer is part of the architecture — not noise around it.
If SegWit took two years, how long would a post-quantum signature migration take? It is, in magnitude, far more invasive. It touches every transaction ever made, every address format, every verification path. A realistic timeline, if handled with the care the community expects, could be five to ten years. Mow's warning, read from this angle, is not merely cautionary. It is an accurate map of the governance terrain. He is saying — to those who haven't actually studied how bitcoin becomes anything — that the process will not be hurried, and anyone who thinks it can be is not paying attention.
Consider the downstream layer, which the source material illuminates most wisely. The second-layer ecosystem — Liquid, RSK, Stacks, the increasingly intricate web of BTC-backed DeFi — inherits its security assumptions from the base chain. A signature migration changes those assumptions. Bridges must be re-engineered. Institutional custodians, the Coinbase Custodies and Fidelity Digital Assets of the world, must recertify every piece of infrastructure. Regulatory opinion letters will be demanded. Insurance assessments will be run. None of that happens quickly, and none of it can be compressed. Liquidity flows, but culture remains. And in a network where the culture is the brand, the risk is not just technical failure — it is the slow erosion of confidence that happens when users cannot follow what is changing.
Now, let me steelman the other side — because a healthy ecosystem requires the debate to be genuinely joined.
The "don't rush" position, for all its wisdom, carries a hidden risk. Waiting is not the same as preparing. If the community spends the next five years arguing while no one builds the transitional infrastructure — no testnet implementations, no wallet demonstrations, no hardware prototypes — then the eventual migration will be compressed into an emergency response. And an emergency migration is exactly how catastrophic errors are made.
The technical community should be building now. Not activating, but building. Reference implementations. BIP drafts. Compatibility layers that let old and new signature schemes coexist within a block. Hardware wallet prototypes. Testnets where post-quantum signatures are verified under realistic conditions. None of this requires a single consensus decision. It only requires attention, resources, and the conviction that preparation is a form of respect for the future.
There is also a narrative time bomb. The moment a quantum milestone hits mainstream media — an IBM publication, a Google experiment, a headline about "breaking bitcoin" — the market's reaction will be emotional, not analytical. Panic does not respect careful timelines. If the community has not built the story of a measured, prepared migration, the panic will write a different story — one about an industry caught sleeping. In that scenario, the "conservative" position will not be remembered as prudent. It will be remembered as paralysis disguised as patience.
There is also a competitive dimension. Ethereum, Solana, and a dozen other L1s are exploring post-quantum migration paths. If one of them publishes a credible roadmap first and executes on it, Bitcoin could face "security migration FOMO" — the pressure to move quickly simply because a rival moved. That would be a terrible reason to change a signature scheme. But it is a real pressure, and pretending that it doesn't exist would be naive.
And I would be remiss not to name the emotional dimension. In 2022, when Terra and Luna collapsed, I organized weekly Resilience Calls for 300 female founders and community managers. We didn't discuss stop-losses or liquidation cascades. We discussed the quiet fear that settled over everyone who had put their savings on the line. What I learned is that the industry's deepest vulnerability is not technical. It is collective emotional stamina. The quantum debate, if allowed to ossify into an identity battleground — the futurists versus the minimalists — will drain exactly the energy that the migration will need.
So where does this leave us?
Samson Mow's warning is not a call to inaction. It is an invitation to rethink the relationship between security and patience. The post-quantum transition will be the most important cryptographic migration in Bitcoin's history. Its success will not be measured in activation blocks or hashrate percentages. It will be measured in whether the community emerges intact — still arguing, still building, still trusting one another.
Building bridges where DeFi once built walls means doing the patient work now: education, prototyping, layering trust before it is needed. The audit was just the beginning of the bond. The decade ahead is a chance to prove that the deepest values of this ecosystem — sovereignty, dignity, collective care — can survive a change in the very mathematics of ownership.
When the quantum era finally arrives, I want Bitcoin to greet it with the same quiet confidence that a grandmother has when she hands her life savings to a bank she has trusted for forty years. That confidence is not built by the protocol. It is built by the practice. The question is not whether Bitcoin will upgrade its signatures. The question is whether we, the community, will upgrade our capacity to care for one another as we make the journey.

