Bitcoin Cash Post-Quantum Migration: Roadmap, Risks, and Options for Holders

Bitcoin Cash post-quantum migration is a topic that has gained serious traction as quantum computing hardware accelerates beyond most public forecasts. This article examines what BCH's development community has said on the subject, what a credible migration would technically require, how BCH compares to other UTXO chains in readiness, and what holders can do right now to reduce their quantum exposure. The goal is a clear-eyed assessment, not speculation dressed as roadmap.

The Quantum Threat to Bitcoin Cash: Why It Matters Now

Bitcoin Cash inherits its cryptographic foundations from Bitcoin. Every BCH address is secured by the Elliptic Curve Digital Signature Algorithm (ECDSA) using the secp256k1 curve. ECDSA security rests on the computational hardness of the elliptic curve discrete logarithm problem. A sufficiently powerful quantum computer running Shor's algorithm can solve that problem in polynomial time, which would allow an attacker to derive a private key from a public key.

That single vulnerability affects every standard BCH address in existence.

How Exposed Is BCH Specifically?

The exposure varies by address type and usage pattern:

• Pay-to-public-key (P2PK) addresses: The public key is directly visible on-chain. These are the most immediately vulnerable. An attacker with a capable quantum machine could derive the private key without the owner ever having signed a transaction.
• Pay-to-public-key-hash (P2PKH) addresses that have never spent: The public key is hidden behind a hash. SHA-256 and RIPEMD-160 are not broken by Shor's algorithm. These addresses enjoy a degree of protection until the first spend, at which point the public key is exposed in the transaction.
• Reused addresses: Once a P2PKH address has spent, its public key is permanently on-chain. Any coins returning to that address are, in a post-quantum world, as exposed as P2PK outputs.

A 2022 analysis by Mark Weber and colleagues (published via arXiv) estimated that roughly 4 million BTC sat in vulnerable P2PK outputs at the time. BCH shares the same UTXO history from before the August 2017 fork, so a non-trivial share of early BCH supply inherits that same exposure.

What "Q-Day" Actually Means for UTXO Chains

Q-Day is shorthand for the point at which a quantum computer achieves the qubit count, error-correction quality, and gate fidelity needed to run Shor's algorithm against secp256k1 at scale. Current public estimates from bodies such as NIST place a cryptographically relevant quantum computer (CRQC) somewhere in the 2030s, though classified and private research timelines are unknown. The window between now and that date is the migration runway.

---

Does Bitcoin Cash Have a Post-Quantum Migration Plan?

As of mid-2025, there is no public, formally adopted post-quantum migration roadmap for Bitcoin Cash.

The BCH developer community, coordinated largely through the CHIP (Cash Improvement Proposal) process, has not ratified a CHIP specifically targeting quantum-resistant signatures. The Bitcoin Cash Research forum and BCHD/Flowee/Bitcoin Verde maintainer discussions have touched on long-term cryptographic agility, but no concrete timeline, candidate algorithm, or activation height has been published.

This is not unique to BCH. Bitcoin Core has also not finalised a PQC migration plan, though the subject appears in developer mailing list threads with increasing frequency. Ethereum's roadmap includes a vague commitment to quantum resistance under the "Splurge" phase but lacks a confirmed implementation date.

In the absence of a protocol-level plan, the responsibility for managing quantum risk currently falls on individual holders and custodians.

---

What a BCH Post-Quantum Migration Would Actually Involve

If the BCH developer community were to pursue a migration, the technical lift is substantial. Understanding the mechanics helps holders appreciate why this takes years, not months.

Selecting a Post-Quantum Signature Scheme

NIST completed its first round of Post-Quantum Cryptography standardisation in 2024, finalising:

• ML-DSA (CRYSTALS-Dilithium): A lattice-based signature scheme. Signature sizes are roughly 2.4 kB for the smallest parameter set, versus 71–72 bytes for a compact ECDSA signature. This has significant implications for block size and fee economics.
• SLH-DSA (SPHINCS+): A hash-based stateless signature scheme. Extremely conservative security assumptions, but signature sizes range from 8 kB to 49 kB.
• FN-DSA (FALCON): Also lattice-based. Smaller signatures than Dilithium (~666 bytes) but more complex to implement safely due to floating-point arithmetic requirements.

For a UTXO chain like BCH, ML-DSA or FN-DSA are the realistic candidates. SLH-DSA signatures are likely too large to be practical at BCH's current block sizes without a corresponding block limit increase.

Script and Address Format Changes

BCH would need new address types (likely a new CashAddr version or a separate bech32-style encoding) and new Script opcodes to validate PQC signatures. The existing `OP_CHECKSIG` and `OP_CHECKMULTISIG` semantics would need PQC equivalents, or the script engine would need to be extended to handle variable-length signature types.

A Migration Window and Coin Sweeping Mechanism

The most contentious element of any PQC migration is handling coins that are already in vulnerable addresses. The community would need to agree on:

1. A deadline block height after which P2PK outputs, and optionally reused P2PKH outputs, can no longer be spent with ECDSA.
2. A migration transaction format allowing owners to prove ECDSA ownership and simultaneously register a PQC public key.
3. What happens to coins not migrated before the deadline: burned, frozen, or moved to a recovery fund. Each option is politically contentious.

The Bitcoin research community has proposed various "quantum-safe migration" schemes. One approach, sometimes called "graceful deprecation," sets a long sunset window (5+ years), broadcasts migration tooling well in advance, and accepts that some coins will be unrecoverable. Another approach uses a "hash-locked migration" mechanism where the owner commits to a PQC key before revealing the ECDSA public key in the final spend.

Hard Fork vs. Soft Fork

A PQC signature scheme cannot realistically be introduced as a soft fork on Bitcoin-derived chains. Old nodes would not understand the new signature type and would reject the transactions as invalid. A hard fork with a scheduled activation height is the only viable path, which means achieving broad node and miner consensus before activation. Given BCH's history of contentious forks, this is a non-trivial governance challenge.

---

Comparison: PQC Readiness Across Major Cryptocurrencies

*QRL and BMIC are purpose-built quantum-resistant chains. All major legacy chains remain in the research or silent phase as of mid-2025.*

---

Interim Options for BCH Holders Right Now

In the absence of a protocol-level solution, holders can take practical steps to reduce their quantum exposure window.

1. Avoid Address Reuse

The single most impactful habit change is never reusing a BCH address. When an address has never signed a transaction, the public key remains hidden behind a hash. This does not eliminate quantum risk entirely but raises the bar significantly, because an attacker would need to break SHA-256/RIPEMD-160 (which Grover's algorithm weakens only quadratically, not exponentially) rather than directly deriving a private key from an exposed public key.

Most modern BCH wallets (Electron Cash, Bitcoin.com Wallet) generate a new change address automatically. Confirm your wallet does this and avoid manually specifying a return address that you have used before.

2. Move Coins from P2PK Outputs

If you hold any BCH in legacy P2PK addresses (identifiable because the scriptPubKey starts with a compressed or uncompressed public key rather than a hash), sweep those funds to a fresh P2PKH address immediately. This does expose the public key once during the sweep transaction, but the resulting output is better protected than the original.

3. Monitor the BCH CHIP Process

The CHIP repository at `gitlab.com/bitcoin.cash/chips` is the authoritative place to track protocol proposals. Subscribe to the BCH Research forum (read.cash and the dedicated research forum) for early-stage discussions. A PQC-related CHIP would likely appear there months before any activation.

4. Evaluate Quantum-Native Alternatives for Long-Term Storage

For holdings intended as multi-year or generational stores of value, some holders are diversifying into wallets and chains that have already implemented post-quantum cryptography at the protocol level. This is a personal risk-management decision rather than a statement about BCH's future, but the option exists.

5. Hardware Wallet Considerations

No major hardware wallet (Ledger, Trezor, Coldcard) currently supports PQC signature schemes for BCH or any other legacy chain. Secure element constraints and firmware complexity mean hardware PQC support is likely years away. For now, hardware wallets protect against classical attack vectors but offer no additional quantum protection beyond what the underlying chain provides.

---

What Would Catalyse BCH Action on PQC?

Several triggers could accelerate BCH's move toward a formal PQC roadmap:

• A credible public demonstration of a CRQC breaking a small ECDSA key: Even a proof-of-concept against a 256-bit curve would create immediate pressure on all ECDSA chains to accelerate timelines.
• Bitcoin Core publishing a formal PQC proposal: BCH has historically responded to BTC-level developments. A BIP (Bitcoin Improvement Proposal) targeting PQC migration would likely prompt parallel CHIP discussions.
• A major custodian or exchange disclosing PQC preparedness requirements: If Coinbase, Kraken, or a similar entity announced that they were moving BCH holdings to PQC-secured cold storage, the protocol conversation would follow.
• NIST or a government body issuing a deprecation timeline for ECDSA: Regulators in the EU and US have begun issuing post-quantum migration guidance for financial infrastructure. A hard deadline for legacy cryptography in financial systems would be a powerful forcing function.

---

The Bottom Line on BCH Post-Quantum Readiness

Bitcoin Cash currently has no public post-quantum migration plan. The underlying cryptographic exposure is real, material, and shared with every other ECDSA-based chain. A credible migration would require choosing a NIST-standardised signature scheme, redesigning address formats and script validation, navigating a hard fork, and managing the politically difficult question of unmigrated coins.

The timeline for practical quantum computers capable of breaking secp256k1 remains uncertain, but the engineering and governance work required for a migration is measured in years. The gap between the runway available and the work needed is one of the more underappreciated risks in the BCH ecosystem.

Holders who treat the current period as a preparation window, rather than waiting for a confirmed threat, are in a structurally better position than those who do not.