Coinbase has urged Bitcoin developers to begin preparing for the quantum-computing threat immediately, warning that consensus changes and ecosystem migrations can take years. In a blog post published Tuesday, the exchange, which states it custodies roughly 5% of all Bitcoin, argued that waiting for the emergence of a cryptographically relevant quantum computer—capable of breaking current signatures—would leave insufficient time to respond. The company outlined specific technical requirements for hardening the network, emphasizing that a solution must protect both existing and newly created coins while remaining compatible with institutional custody methods like multi-party computation.
Coinbase backed a flexible “container” design, referencing proposals such as BIP-360, which would allow new post-quantum signature systems to be integrated over time without requiring a complete network redesign. Additionally, the exchange proposed a staged “1-of-2” spending path, enabling funds to be spent using either classical or quantum-safe keys during the transition period. This approach aims to maintain compatibility with ordinary wallets and large custodians alike. The company also highlighted that dormant, lost, or exposed coins, including those from the Satoshi era, present a distinct governance challenge that requires separate handling.
This push aligns with Coinbase’s broader efforts to address quantum risks. The exchange convened a quantum advisory board in January to study these threats and joined the Bitcoin Security Consortium in July alongside BlackRock and Strategy, committing a combined $15 million toward quantum-proofing Bitcoin. By detailing these technical preferences, Coinbase positions itself as a major stakeholder influencing the direction of Bitcoin’s security evolution.
Coinbase’s detailed technical roadmap signals a shift from general concern to actionable engineering requirements within the Bitcoin community. By advocating for specific mechanisms like BIP-360 and staged spending paths, the exchange is attempting to steer the development conversation toward solutions that preserve its operational model, particularly regarding multi-party computation custody. This move underscores the tension between maintaining backward compatibility for legacy coins and securing future transactions against theoretical but high-stakes quantum attacks.
The emphasis on starting now reflects a pragmatic assessment of blockchain governance timelines, where consensus-building often lags behind technological threats. However, treating dormant coins as a separate governance problem introduces complexity, as any rescue mechanism must itself be quantum-resistant to avoid creating new vulnerabilities. This distinction highlights the difficulty of achieving a unified security upgrade across a decentralized network with diverse asset histories and user bases.
