Bitcoin Cash Proposes Quantum-Resistant Transactions
Bitcoin Cash is exploring quantum-resistant transactions. This careful phrasing is key, as what Bitcoin Cash developers currently have is a proposal, not a protected blockchain. The distinction between these two points determines whether this represents true progress or merely a publicity effort.
The Claim and Its Origin
In June 2026, Bitcoin Cash contributor mainnet_pat published CHIP-2026-06: Post-Quantum and Hybrid Signatures. This proposal introduces an OP_SIGHASH opcode and a signature dispatch mechanism, enabling the virtual machine to select a signature scheme from a registry. Currently, Secp256k1 handles ECDSA and Schnorr signatures, with plans to add post-quantum schemes like SPHINCS+ and Falcon-512 over time. The proposal is under review for potential lock-in on November 15, 2026, with a target mainnet activation date of May 15, 2027.
Here’s the strongest argument for the proposal: BCH is a UTXO chain, and migrating transaction authorization on such a chain is inherently difficult. This is because a signature linked to a specific output authorizes each spend.
The CHIP doesn’t introduce new cryptography; instead, it exposes the sighash digest that the node already computes. This reduces the need for manual reconstruction in alternative-scheme contracts from hundreds of bytes to just two.
Hybrid keys, which combine two schemes using “AND” logic, necessitate that both the classical and post-quantum checks pass for a spend to be valid. This design maintains existing P2PKH address formats and wallet tools. It’s a genuine migration concept, building on the May 2026 Layla upgrade, and it treats quantum readiness as a critical infrastructure component to be addressed now.
It’s important to give credit where it’s due. This approach is more disciplined than what most other chains have managed. StarkWare, in a different context, aptly argues that quantum security should rely on public evidence, not promises. The BCH proposal strives to meet this standard, though it hasn’t fully reached it yet.
What the Proposal Actually Changes, and What It Doesn’t
Let’s precisely define the current stage. CHIP-2026-06 is a proposal currently undergoing active review; it’s not yet activated. Though Bitcoin Cash Node developers have opened a merge request to implement the opcode, this is a development step, not a deployed consensus rule. Both lock-in and activation are future dates contingent on the CHIP process successfully completing its review.
The scope of the proposal is narrower than headlines might suggest. The CHIP adds a new path at the signature verification layer, but it doesn’t migrate the entire chain. Coins held in existing outputs with exposed or reused public keys will remain vulnerable under the current scheme until their owners move them. Though supporting signature verification in the virtual machine is one aspect, the proposal doesn’t inherently address separate challenges like wallet support, miner enforcement, exchange handling, or custodial integration.
The specific claims of the proposal include:
- An
OP_SIGHASHopcode that pushes the already-computed 32-byte sighash digest onto the stack, without introducing new sighash semantics. - A generic dispatch registry where a public key’s first byte determines the signature scheme.
- Hybrid keys that require both a classical and a post-quantum verification to succeed.
- Preservation of P2PKH outputs, address formats, and Double-Spend Proof coverage.
Each of these points represents a design assertion, none of which has been measured on the BCH mainnet or testnet.
The Evidence Needed to Validate the Proposal
Crucially, the data required to evaluate the design is missing. No BCH-specific figures have been provided for signature size, block or weight impact, fee changes, or verification latency. SPHINCS+ signatures can be tens of kilobytes, depending on the parameter set.
Falcon-512 is smaller but presents its own implementation risks related to floating-point signing. On a blockchain where block space is priced, signature size affects fees and throughput. The proposal’s own text favors the stateless hash-based SLH-DSA as a long-term goal but doesn’t specify its transaction cost on BCH.
Furthermore, there’s the question of worst-case scenarios. Signature verification is an area where an attacker could provide invalid inputs, forcing the network to waste computation. The provided documentation does not include a worst-case invalid-input rejection cost. This kind of metering detail is essential for determining if a scheme is safe to run within the consensus mechanism. The Bitcoin Cash Research discussion highlights that the complete CHIP text, supported schemes, fork path, and activation mechanics should be verified against the primary document, not just secondary summaries.
No independent audit or testnet benchmark has been cited. Though community feedback has been constructive, with several stakeholders calling the opcode “low-hanging fruit,” stakeholder enthusiasm doesn’t equate to performance measurement.
Comparison with Other Chains
Account-abstraction chains offer a simpler migration path. For instance, Instanodes announced post-quantum accounts for Ethereum and Solana, where account logic can switch verification methods without affecting every output. BCH can’t directly adopt this approach because UTXO authorization is tied to specific outputs, not to mutable account contracts.
The hybrid P2PKH design is BCH’s response to this constraint, and it’s a reasonable one. However, it also means BCH faces a migration burden that account-abstraction chains do not, as exposed legacy outputs cannot be upgraded in place.
The perceived threat is credible across the industry. Coinbase CEO Brian Armstrong called quantum computing a greater threat to crypto than AI, expressing hope that the Bitcoin community would find a solution in the coming quarters. This accurately reflects the urgency but doesn’t validate any specific design.
A point on terminology: Post-quantum schemes like SLH-DSA and Falcon are believed to be secure against known quantum attacks, and SLH-DSA aligns with NIST’s FIPS 205. “Believed” is the crucial word, as these schemes are not unbreakable, and confusing standardization with permanence is a common error.
Conclusion
CHIP-2026-06 represents a serious proposed migration design for a UTXO chain, authored by a recognized contributor, currently under active review, with an implementation underway and activation targeted for May 2027. This is the most favorable interpretation.
However, the available record supports a proposed path, not a demonstrated or deployed quantum-resistant transaction system. Though the design intent is commendable, the absence of performance data, an independent audit, testnet results, and clear rules for rescuing legacy outputs creates a significant gap between intent and verified implementation.
Before considering BCH “quantum-ready,” three key developments should be observed: confirmation of lock-in and activation through the review process, published signature-size and fee measurements on a testnet, and a stated plan for exposed and lost outputs.
For more information on UTXO chains and signature tradeoffs, continue reading QNews coverage of post-quantum migration.