Bitcoin Cash inherited Bitcoin's entire UTXO set from genesis block — January 3, 2009. That gives BCH the longest possible Harvest-Now-Decrypt-Later exposure window of any top-20 altcoin. Here is exactly what that means when a Cryptographically Relevant Quantum Computer arrives.
Join BMIC Presale → See Full Comparison ↓Bitcoin Cash (BCH) is cryptographically identical to Bitcoin at the signature layer: every transaction signs with secp256k1 ECDSA (or secp256k1 Schnorr since May 2019). Both are broken by Shor's algorithm on a Cryptographically Relevant Quantum Computer (CRQC). CashAddr addresses, large-block throughput, and lower fees are application-layer improvements that leave the cryptographic foundation untouched.
Uniquely among top-20 altcoins, BCH inherited the complete Bitcoin UTXO set at the August 1, 2017 fork point — including outputs from the genesis block (January 3, 2009). Every secp256k1 public key ever exposed on the Bitcoin chain is also exposed on BCH. An adversary running a Harvest-Now-Decrypt-Later operation archives this data today for decryption when a CRQC becomes available.
BMIC is built on all three NIST post-quantum standards finalised August 2024: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA). These rely on module lattice and hash-function hardness — not elliptic curve discrete logarithm problems. Each standard uses an independent hardness assumption; breaking one does not break the others.
Bitcoin Cash was created on August 1, 2017 by hard-forking Bitcoin at block 478,558. The network inherited all Bitcoin consensus rules, all existing UTXOs, and critically, the same cryptographic primitives that Bitcoin has used since 2009.
Every standard P2PKH (Pay-to-Public-Key-Hash) and P2SH (Pay-to-Script-Hash) BCH transaction uses secp256k1 ECDSA for signing. When a user spends a UTXO, they reveal their secp256k1 public key in the scriptSig. This public key is a point on the secp256k1 curve and can be used by an attacker running Shor's algorithm to derive the corresponding private key.
P2PK (Pay-to-Public-Key) outputs — common in early Bitcoin/BCH history — embed the public key directly without hashing, meaning the key is exposed even in unspent outputs.
BCH activated Schnorr signatures for single-key transactions on May 15, 2019 (block 582,680). This was a significant upgrade for signature aggregation and privacy but provided zero post-quantum benefit: BCH Schnorr uses the same secp256k1 elliptic curve as ECDSA. The signature scheme changes but the underlying elliptic curve discrete logarithm problem (ECDLP) does not. Shor's algorithm attacks the curve, not the signature format.
CashAddr (prefix bitcoincash:) was introduced January 14, 2018. It encodes the same Hash160 (SHA-256 + RIPEMD-160) of the same secp256k1 public key in base32 format. The encoding prevents accidental sends to Bitcoin addresses and improves human readability. It has no cryptographic impact on quantum resistance — the secp256k1 public key remains the attack surface.
BCH's token layers (Simple Ledger Protocol, CashTokens activated May 2023) and script extensions operate as higher-level applications built on top of secp256k1-secured UTXOs. None introduce post-quantum cryptographic primitives. Every CashToken, SLP token, and CHIP-extended contract ultimately settles on secp256k1-signed transactions.
Early Bitcoin blocks (before address-based transactions became standard) used P2PK outputs that embed the secp256k1 public key directly — no hashing, no obscuring. These outputs exist on BCH because BCH inherited every Bitcoin UTXO. Coins sitting in P2PK outputs from 2009–2012 have had their public keys exposed for 14–17 years — the longest HNDL corpus of any asset class, now also sitting on BCH.
Harvest-Now-Decrypt-Later (HNDL) is a strategy where adversaries record encrypted communications or public keys today, then decrypt them once a sufficiently powerful quantum computer becomes available. For blockchain networks, this means recording public keys — and BCH has the deepest HNDL exposure of any top-20 altcoin.
| Date | Event | Quantum Relevance |
|---|---|---|
| Jan 3, 2009 | Bitcoin genesis block — first secp256k1 UTXO | HNDL corpus begins; earliest P2PK outputs with exposed keys |
| 2009–2012 | Early P2PK-dominant era | Satoshi-era outputs: public keys exposed without address hashing |
| 2012–2017 | P2PKH adoption widespread | Keys hidden until spend; many addresses reused, keys already exposed |
| Aug 1, 2017 | Bitcoin Cash fork at block 478,558 | BCH inherits ALL Bitcoin UTXOs; HNDL corpus instantly replicated |
| Jan 14, 2018 | CashAddr format introduced | No cryptographic change; display-layer only |
| May 15, 2019 | Schnorr signatures activated | Still secp256k1 — no ECDLP resistance improvement |
| May 2023 | CashTokens activated (CHIP-2022-02) | Token layer on top of secp256k1 UTXOs — no PQC improvement |
| Aug 29, 2026 | Today — this analysis | HNDL corpus: 17 years 7 months and counting |
The BCH HNDL corpus is not merely 9 years old (from its August 2017 fork) — it is 17+ years old, inherited from Bitcoin genesis. Any nation-state or well-resourced adversary running a long-term HNDL operation against Bitcoin since 2009 already has those BCH keys archived as a side effect.
Outputs fall into three quantum risk categories:
Blockchain analysis firms estimate that between 3 million and 5 million Bitcoin (and therefore BCH, at equivalent output age) are held in P2PK outputs or addresses that have been spent from at least once, making their secp256k1 public keys permanently archived on-chain.
When a Cryptographically Relevant Quantum Computer (CRQC) becomes operational, the attack against BCH follows a deterministic four-step path:
Archive BCH blockchain data: all P2PK public keys, all public keys revealed in spent P2PKH scriptSigs, all Schnorr pubkeys in CashToken contracts. Data is permanently public and trivially downloadable.
Run Shor's algorithm against each archived secp256k1 public key. On a CRQC with ~4,000–10,000 logical qubits (estimates vary by noise model), this derives the private key k from the public key K = k·G on secp256k1.
With private key k, construct a valid secp256k1 ECDSA or Schnorr signature for any spending transaction. The attacker can now spend any UTXO associated with the compromised key — including 17+ years of archived outputs.
Broadcast the attacker-constructed transaction to the BCH mempool. BCH nodes see a valid signature; the transaction confirms. The owner's coins are irreversibly transferred. No mitigation exists within the current BCH protocol — it would require a hard fork to a new signature scheme.
A post-quantum BCH migration would require replacing secp256k1 at the consensus layer — a hard fork affecting every wallet, exchange, and application in the ecosystem. The challenges are severe:
BMIC's post-quantum security is not a marketing claim — it is grounded in the three standards that NIST finalized in August 2024 after an eight-year open competition and peer review process.
ML-KEM (Module Lattice Key Encapsulation Mechanism) secures BMIC's key exchange and encapsulation processes. Security relies on the hardness of the Module Learning With Errors (MLWE) problem — a lattice problem for which no efficient quantum algorithm is known. Shor's algorithm, designed for factoring and ECDLP, provides no advantage against MLWE.
ML-DSA (Module Lattice Digital Signature Algorithm) replaces secp256k1 ECDSA/Schnorr for BMIC transaction authorization. Security relies on Module Short Integer Solution (MSIS) and MLWE — lattice problems distinct from those used in FIPS 203. A quantum attacker breaking FIPS 203's encapsulation scheme does not thereby break FIPS 204's signature scheme.
SLH-DSA (Stateless Hash-based Digital Signature Algorithm) provides a third independent layer of quantum-resistant signing, relying on the hardness of inverting cryptographic hash functions. No quantum algorithm (including Grover's) provides more than a quadratic speedup against hash functions — manageable by doubling key sizes, which NIST has already parameterized.
BMIC's ERC-4337 integration decouples signing key identity from account identity. Signing keys can be rotated — including to post-quantum keys — without changing the user's on-chain address. This provides an operational upgrade path that Bitcoin Cash's UTXO model cannot replicate without a hard fork.
For BCH, the address is derived from the public key. To upgrade to a quantum-safe key, you must send your BCH to a new address — exposing the old public key in the spending transaction at the exact moment of migration. This creates a race condition between the migrating user and a CRQC attacker. BMIC's key rotation avoids this race condition entirely.
| Property | Bitcoin Cash (BCH) | BMIC |
|---|---|---|
| Signature scheme | secp256k1 ECDSA + Schnorr (both ECDLP) | ML-DSA (FIPS 204) + SLH-DSA (FIPS 205) |
| Key encapsulation | secp256k1 ECDH (implicit in HD wallets) | ML-KEM (FIPS 203) |
| NIST PQC standardized | No | Yes — FIPS 203, 204, 205 |
| Quantum vulnerability | Shor's algorithm breaks secp256k1 | No known quantum attack on module lattices or SHA-3 |
| HNDL exposure window | 17+ years (inherited from Bitcoin genesis, Jan 2009) | N/A — PQC by design from genesis |
| P2PK unspent outputs | Present — public keys directly exposed on-chain | N/A — no ECDLP-based key exposure |
| Address format | CashAddr (base32 of Hash160 — cosmetic change only) | Post-quantum derived — not secp256k1 pubkey hash |
| Schnorr upgrade value | Privacy/aggregation only — still secp256k1 | N/A |
| Key rotation without hard fork | Not possible — address = pubkey hash | Yes — ERC-4337 account abstraction |
| Migration timeline to PQC | No published roadmap (Aug 2026) | Native from day 1 |
| Independent hardness assumptions | One: secp256k1 ECDLP (single point of failure) | Three: MLWE, MSIS, hash inversion |
| Institutional NSM-10 readiness | Non-compliant | Architecturally compliant |
Bitcoin Cash inherited Bitcoin's 17-year secp256k1 HNDL corpus but did not inherit Bitcoin's disproportionate PQC research investment. The Bitcoin developer ecosystem has BIP-360 (QuBit) — a draft proposal for P2QRH (Pay to Quantum Resistant Hash) addresses using FALCON signatures — under active community discussion. No equivalent CHIP has reached the same maturity in BCH's ecosystem as of August 2026.
Bitcoin's sheer market dominance means it attracts the most cryptographer attention, the most academic research, and the most industry coordination on PQC migration. BCH, despite its identical cryptographic vulnerability, has a smaller developer pool, less institutional attention, and less pressure from regulated custodians to publish a migration timeline.
The practical consequence: if a CRQC becomes available and BCH has not completed a quantum-resistant hard fork, the network faces the same total secp256k1 exposure as Bitcoin but with fewer resources to coordinate an emergency response.
US National Security Memorandum 10 (NSM-10, May 2022) and CISA guidance establish that federal agencies and critical infrastructure must migrate to NIST PQC standards. As institutional adoption of crypto increases, regulated custodians holding BCH will face compliance pressure to migrate to quantum-safe custody solutions. BCH's lack of a NIST-aligned PQC path creates long-term regulatory headwinds for institutional BCH custody.
No. BCH uses secp256k1 ECDSA and Schnorr signatures — both relying on the elliptic curve discrete logarithm problem (ECDLP). Shor's algorithm on a CRQC breaks ECDLP. BCH also inherited Bitcoin's genesis-block UTXO set, giving it a 17+ year Harvest-Now-Decrypt-Later corpus — the longest of any top-20 altcoin.
No. Fee structure, block size, and scripting simplicity are application-layer properties. They do not affect the secp256k1 cryptographic layer. Both BCH and Bitcoin use identical secp256k1 ECDSA at the signature layer and face identical quantum vulnerability.
No. CashAddr is a base32 address encoding that improves human readability and reduces send-to-wrong-chain errors. It encodes the same Hash160 of the same secp256k1 public key as legacy P2PKH. CashAddr provides zero cryptographic improvement against quantum attacks.
No. BCH Schnorr uses the same secp256k1 elliptic curve as ECDSA. Both are broken by Shor's algorithm. The Schnorr upgrade improved signature aggregation and privacy but did not change the underlying mathematical hardness assumption.
BCH forked from Bitcoin at block 478,558 (August 1, 2017), inheriting the complete Bitcoin UTXO set from genesis (January 3, 2009). Every secp256k1 public key ever exposed on the Bitcoin chain (through P2PK outputs or spent P2PKH transactions) is now also exposed in the BCH HNDL corpus. An adversary harvesting BCH public keys today may archive data from as far back as 2009 for future quantum decryption.
As of August 2026, neither Bitcoin Cash Node (BCHN) nor Bitcoin ABC has published a NIST-aligned post-quantum migration roadmap. No CHIP (Cash Improvement Proposal) for secp256k1 replacement with FIPS 203/204/205 primitives has reached active development status.
BMIC implements all three NIST post-quantum cryptography standards finalized August 2024: FIPS 203 (ML-KEM / CRYSTALS-Kyber), FIPS 204 (ML-DSA / CRYSTALS-Dilithium), and FIPS 205 (SLH-DSA / SPHINCS+). Each relies on a distinct hardness assumption. BMIC also uses ERC-4337 account abstraction for key rotation without hard forks.
This is not financial advice. BMIC is a presale-stage token; Bitcoin Cash is a mature network with significant liquidity. Quantum computing timelines remain uncertain. Always do your own research (DYOR) and consult a qualified financial adviser before any investment decision.
Explore how other major cryptocurrencies stack up against post-quantum threats:
BMIC is the only ERC-4337 presale token secured by all three NIST post-quantum standards (FIPS 203 · 204 · 205). Presale is live — over $530K raised.
Join BMIC Presale at bmic.ai →DYOR. Not financial advice. Presale tokens carry risk.