Skip to main content
All articles

Bitcoin Cash and Post-Quantum Vaults: Current Capabilities and Limits

Understand quantum risks to Bitcoin-style signatures, BCH's opt-in post-quantum vault experiments, and what remains unreviewed or undeployed.

Published Jan 30, 2026Updated Aug 30, 20264 min read

Bitcoin Cash, like Bitcoin, normally authorizes spends with elliptic-curve signatures. A sufficiently capable fault-tolerant quantum computer running Shor's algorithm could derive a private key from a revealed public key and break that authorization model.

No publicly known computer can do this against production Bitcoin keys today. There is also no reliable date for when one will exist. Fixed countdowns such as "ten years" are speculation, not a security parameter.

Which parts are exposed

The main concern is digital signatures, not SHA-256 suddenly becoming useless. Grover's algorithm gives a quadratic speedup against ideal hash search, while Shor's algorithm attacks the discrete-logarithm problem underlying ECDSA and Schnorr much more directly.

Exposure also depends on output type and use:

  • Some address forms hide the public key until the first spend.
  • Reused addresses and output types that publish a public key expose it earlier.
  • Once a public key is known, a future attacker would race the legitimate owner or target old unspent outputs.
  • Funds already controlled by a post-quantum spending condition would have a different risk model.

Hidden public keys buy reaction time; they are not a complete migration plan.

What standards exist now

NIST has standardized several post-quantum algorithms and separately recommends stateful hash-based signatures in SP 800-208. Those standards are evidence for cryptographic primitives, not automatic approval of a blockchain wallet construction.

Blockchain integration must also solve transaction size, verification cost, key rotation, address format, recovery, multisignature, and migration of existing funds.

Why BCH can experiment in script

CashVM gained native introspection in 2022, CashTokens in 2023, high-precision arithmetic and revised VM limits in 2025, and loops, functions, P2S, and bitwise operations in 2026.

Together, those features allow developers to implement and test some alternative signature-verification logic inside opt-in contracts. This is different from replacing OP_CHECKSIG across the network. Ordinary BCH outputs remain protected by their existing signature rules unless users deliberately move funds into another construction.

Quantumroot is a developer preview

Quantumroot is a proposed BCH vault design that uses LM-OTS, a stateful hash-based one-time signature scheme described in RFC 8554 and referenced by NIST SP 800-208. The design combines CashVM contracts and CashToken-based authorization so a vault can offer both conventional and post-quantum spending paths.

The author presents specific security-strength, size, and aggregation estimates. Those are design claims from the project, not independent conclusions from this article. The original preview explicitly states that the wallet template had not yet been reviewed by anyone else.

As of this review:

  • the required CashVM features are active on mainnet;
  • prototype transactions and contract code exist;
  • the design is opt-in rather than chain-wide protection;
  • mainstream wallet integration and broad independent audit evidence are not established.

Stateful one-time signatures add operational hazards. A key or leaf that is used incorrectly more than once can lose its security assumptions, so wallet state synchronization, backup, failed broadcasts, and multi-device recovery require careful design.

Migration is the hard part

Even a sound post-quantum contract does not move existing funds automatically. A practical ecosystem plan would need:

  1. reviewed output and address standards;
  2. interoperable wallet implementations;
  3. safe key generation and state management;
  4. hardware and backup support;
  5. exchange, custody, and node compatibility;
  6. a strategy for exposed and inactive outputs;
  7. a response plan if quantum capability advances faster than deployment.

Moving too early can impose large signatures, new code risk, and immature recovery. Moving too late can leave revealed public keys exposed. The correct timing depends on evidence about both quantum hardware and deployed wallet quality.

The accurate claim

BCH's current virtual machine can host opt-in post-quantum experiments, and Quantumroot is a concrete example. That is meaningful preparedness. It is not equivalent to saying Bitcoin Cash is already quantum-resistant, that user funds are automatically protected, or that the remaining engineering and coordination work is complete.