Key Takeaways
- A major cryptocurrency exchange released a technical document on October 13 calling for immediate quantum security planning for Bitcoin.
- The platform safeguards approximately 5% of Bitcoin’s total supply and has begun internal quantum-resistance preparations.
- The paper highlights BIP-360 and P2TRv2 as adaptable frameworks for integrating quantum-safe signature methods.
- Hybrid wallet architecture supporting both conventional and quantum-resistant signatures was recommended.
- The exchange emphasized that discussions about inactive or irretrievable Bitcoin should remain distinct from core security implementation.
Coinbase has issued a formal appeal to Bitcoin’s development community to initiate preparations against potential quantum computing vulnerabilities. The technical document, released on October 13, warns that implementing robust security enhancements across Bitcoin’s network will likely require multiple years.
As custodian of roughly 5% of Bitcoin’s circulating supply, the platform has already begun adapting its infrastructure for a quantum-resistant environment.
These preparatory efforts encompass collaboration with Bitcoin security researchers, active participation in open-source development initiatives, and involvement with the Bitcoin Security Consortium.
“We believe it is important to begin preparing well ahead of any CRQC (Cryptographically Relevant Quantum Computer) announcement,” Coinbase said. “Bitcoin consensus changes and ecosystem migrations can take years, so it is important that we begin this work now.”
Understanding Bitcoin’s Quantum Vulnerability
Bitcoin’s security architecture relies on elliptic-curve cryptographic methods, specifically ECDSA and Schnorr signature schemes, for transaction authorization. A sufficiently advanced quantum computer could theoretically derive private keys from publicly visible keys.
Coinbase clarified that no such machine currently exists. The company characterized the risk as a prospective challenge demanding proactive preparation rather than an immediate crisis.
According to the exchange, addressing this vulnerability extends beyond simply selecting alternative cryptographic algorithms. Engineers must evaluate numerous factors including transaction costs, blockchain capacity constraints, wallet compatibility, and the capacity for independent node verification.
Platform Endorses Modular Architecture and Dual-Signature Systems
The document identifies BIP-360 and P2TRv2 as promising architectural approaches. Both frameworks decouple transaction formatting from signature methodology, enabling future algorithm updates or replacements without fundamental restructuring.
BIP-360 introduces Pay-to-Merkle-Root (P2MR), a structure that eliminates Taproot’s key-path spending mechanism, which creates public key exposure. This proposal remains under development in draft form.
The platform recommended evaluating post-quantum cryptographic standards including ML-DSA, SLH-DSA, and FN-DSA as they reach maturity. Additionally, SHRINCS—a space-efficient hash-based signature design—was identified as worthy of consideration.
For the transition strategy, Coinbase outlined a 1-of-2 hybrid wallet model. This architecture would allow users to authorize transactions using either existing ECDSA or Schnorr credentials or an independent quantum-resistant key.
The company stressed that emerging solutions must integrate with multiparty computation (MPC) protocols, which major custodians employ for key management. It cautioned that stateful signature approaches pose forgery vulnerabilities if signing state records are improperly maintained, advocating instead for stateless alternatives.
Abandoned and inaccessible coins present an unresolved challenge. This category encompasses dormant addresses, permanently lost private keys, and Bitcoin mined during the network’s initial years.
A companion proposal, BIP-361, outlines a framework for progressively phasing out legacy signature types following the availability of quantum-resistant alternatives. This proposal also remains in draft status without network activation.
Coinbase maintained that disagreements surrounding permanently inaccessible funds should proceed through independent policy discussions and must not delay security enhancements protecting actively managed wallets.
The document deliberately avoided establishing migration timelines, endorsing specific algorithms, or proposing activation mechanisms. Coinbase indicated its ongoing engagement will continue through sustained dialogue with security researchers, protocol developers, and open-source community members.


