Security & Audits
The crypto exchange is calling for flexible signature designs, staged protections and a migration path for Bitcoin holders as developers prepare for future quantum threats.
Share
Coinbase published a blog post on October 13 outlining technical priorities for Bitcoin's post-quantum transition, covering signature design flexibility, institutional custody compatibility, and the unresolved question of migrating legacy funds.
Coinbase has outlined a set of technical priorities for preparing Bitcoin for the potential threat posed by quantum computing, arguing that the transition will require more than adopting a new digital-signature algorithm.
In a blog post published on October 13, Coinbase said a post-quantum transition should account for Bitcoin’s limited block space, the ability of independent nodes to validate transactions, institutional custody requirements and the needs of ordinary wallet users.
The company also highlighted a difficult question for the network: how to handle Bitcoin held in wallets that cannot or do not migrate to quantum-resistant cryptography.
Coinbase presented the recommendations as a contribution to an ongoing technical discussion, rather than a finalized proposal or an official Bitcoin development decision.
One of Coinbase’s priorities is a transaction structure that could accommodate different post-quantum signature schemes without requiring Bitcoin to redesign its transaction architecture every time cryptographic standards evolve.
The company pointed to BIP-360, which proposes a Pay-to-Merkle-Root output structure designed with future post-quantum integration in mind, and P2TRv2, another design being discussed by Bitcoin developers.
Coinbase said a flexible design could allow new signature algorithms to be introduced, replaced or supplemented as research advances.
The company also called for a Bitcoin-specific process to evaluate potential cryptographic schemes. Its proposed criteria include signature and key sizes, verification speed, transaction fees, full-node performance, hardware-wallet compatibility and the feasibility of institutional signing systems.
These considerations matter because post-quantum signatures can require more data than conventional signatures. Integrating them into Bitcoin without accounting for block capacity, transaction costs and validation requirements could create new trade-offs for the network.
Coinbase did not endorse a single final signature scheme in the post.
Coinbase also proposed examining ways to introduce post-quantum protection gradually, rather than waiting for a single network-wide transition.
One option discussed in the post is a hybrid spending arrangement that provides two alternative authorization paths for the same funds: one using conventional ECDSA or Schnorr signatures and another using a post-quantum signature.
Such an approach could allow users to begin adopting quantum-resistant protection while the wider Bitcoin ecosystem continues to evaluate its long-term migration strategy.
Coinbase also called for careful consideration of stateful and stateless signature schemes. Stateful schemes may offer advantages in signature size or speed, but they require reliable management of signing state. Reusing state incorrectly can compromise security.
The company said the evaluation process should therefore account for implementation reliability, recovery procedures and the availability of stateless alternatives.
The proposals remain technical considerations for developers to evaluate. They do not mean Bitcoin has adopted a new signature standard or that a transition date has been set.
For Coinbase, the choice of cryptographic technology must also account for how digital assets are secured in practice.
The exchange highlighted compatibility with multi-party computation (MPC), a method used to distribute signing operations across multiple parties or systems without reconstructing a complete private key in one place.
Coinbase said MPC compatibility is an important consideration for institutional custodians that manage assets across distributed infrastructure and require strong controls against key theft.
The wider challenge is that a signature scheme must work not only at the protocol level but also with exchanges, custody platforms, hardware wallets and self-custody software.
A technically secure scheme could still be difficult to adopt if it creates operational bottlenecks or complicates recovery and key management.
Coinbase therefore called for post-quantum designs to be assessed against real-world custody and wallet requirements, alongside their cryptographic security.
One of the most difficult questions concerns Bitcoin that remains in legacy wallets if the network eventually changes its signature rules.
Some funds may belong to active holders who have not completed a migration. Others may be inaccessible because their private keys or recovery information have been lost. Certain older outputs also have public keys exposed on-chain.
Coinbase said developers should consider how such funds would be handled if Bitcoin eventually restricts or ends spending through conventional ECDSA and Schnorr signatures.
Potential approaches discussed in the post include staged restrictions on legacy signatures, rate limits or recovery mechanisms. Each would involve difficult trade-offs, particularly around protecting vulnerable funds without undermining legitimate ownership.
The company did not propose a settled policy for dormant or inaccessible Bitcoin. It argued that the question should be examined alongside the technical work on post-quantum signature support, rather than used as a reason to delay that work.
The issue connects to the broader concerns raised in Unlock Blockchain’s earlier coverage, Coinbase Advisory Board Flags Quantum Risk to 6.9 Million BTC, which examined potential exposure linked to public-key visibility and the challenge of migrating funds at scale.
Coinbase’s recommendations reflect a wider industry effort to prepare blockchain infrastructure for cryptographic risks that could emerge as quantum computing advances.
The company stressed that preparing early is important because Bitcoin consensus changes and ecosystem-wide migrations can take years. However, the post does not suggest that quantum computers can currently break Bitcoin’s cryptography.
Other blockchain networks are also working on potential responses. Ethereum developers, for example, have explored changes intended to accommodate post-quantum cryptographic schemes, as discussed in Unlock Blockchain’s report on Ethereum’s efforts to protect staked ETH against future quantum attacks.
For Bitcoin, the challenge is particularly complex because no single organization can compel every user, wallet provider, custodian and node operator to upgrade at once.
Coinbase’s position is that technical research, implementation planning and discussion of difficult migration questions should advance in parallel. The next steps will depend on continued work by Bitcoin developers and the wider community, with no single approach yet established as the definitive solution.
Disclaimer of Warranty
The information provided in this article is for general informational purposes only. We make no warranties about the completeness, reliability, and accuracy of this information. Read full disclaimer
Editor's Picks
In the Same Space

Who Gets the $5B Bitcoin Fortune? UK Ruling Complicates Victims’ Fight
News Desk
Oct 13, 2026
6 min

Bitcoin Reclaims $83,000 Amid Global Tech Sell-Off
News Desk
Oct 13, 2026
6 min

FTX’s ‘Reckless’ Bitcoin-Mining Assets Find a Second Life in the AI Boom
News Desk
Oct 12, 2026
8 min

3iQ Secures In-Principle ADGM Approval for UAE Expansion
News Desk
Oct 12, 2026
3 min