Bitcoin Cash Proposal Seeks Path to Quantum-Resistant Transactions

Bitcoin Cash Takes a Step Toward Quantum‑Resistant Transactions

Bitcoin Cash (BCH) developers are actively discussing CHIP‑2026‑06, a Cash Improvement Proposal that introduces a new `OP_SIGHASH` opcode. The change aims to make post‑quantum (PQ) and hybrid signature schemes practical on the Bitcoin Cash network without breaking existing wallets, address formats, or consensus rules.

---

Why a New Opcode?

Current signature verification in the CashVM relies on `OP_CHECKSIG` and related opcodes, which embed the sighash calculation inside the opcode. Implementing alternative cryptographic schemes—such as SPHINCS+, Falcon‑512, or future lattice‑based algorithms—requires script authors to manually reconstruct the sighash. That process is verbose, error‑prone, and often spans hundreds of bytes of script code.

`OP_SIGHASH` solves this by exposing the 32‑byte sighash that the node already computes during signature verification. The opcode does not alter the sighash algorithm; it merely pushes the digest onto the stack, allowing scripts to use it directly. This simplification:

• Reduces contract size dramatically (from hundreds of bytes to a two‑byte opcode).
• Eliminates the need to re‑implement edge‑case logic for `SIGHASH_SINGLE`, `ANYONECANPAY`, ForkID, etc.
• Provides a reliable, audited reference for any signature scheme that builds on the standard sighash.

---

Hybrid and Post‑Quantum Signatures

The proposal defines a generic signature dispatch mechanism. A public key’s first byte selects the cryptographic scheme from a registry:

• `0x02` – secp256k1 (current ECDSA/Schnorr)
• `0x03` – SPHINCS+ (hash‑based, stateless)
• `0x04` – Falcon‑512 (lattice‑based)
• … (future schemes can be added without further consensus changes)

Hybrid keys combine two schemes with AND semantics. A transaction signed with a hybrid key (e.g., secp256k1 + SPHINCS+) is considered valid only when both components verify. This offers a migration path: users can retain the proven security of classical signatures while gaining quantum resistance from the PQ component.

Crucially, hybrid and PQ keys spend from ordinary Pay‑to‑Public‑Key‑Hash (P2PKH) outputs. No new output types or address formats are required, preserving compatibility with existing wallets and the Double‑Spend Proof (DSP) system.

---

Timeline and Community Involvement

• Lock‑in date: 15 Nov 2026 – developers will signal readiness for the change.
• Activation target: 15 May 2027 – assuming sufficient consensus, the opcode will be enabled on mainnet.
• Implementation status: A merge request adding `OP_SIGHASH` to Bitcoin Cash Node is already open, and early testing shows the opcode behaves as expected.
• Feedback loop: Stakeholders—including wallet developers, node operators, and researchers—are invited to review the specification, suggest initial scheme parameters, and test hybrid transactions on testnet.

The proposal builds on the May 2026 “Layla” upgrade, which added loops, functions, bitwise operations, and Pay‑to‑Script capabilities. Those enhancements already enable sophisticated script constructions; `OP_SIGHASH` now provides the missing cryptographic glue.

---

What This Means for BCH Users

1. Future‑proofing: By supporting PQ algorithms now, BCH positions itself to withstand the eventual emergence of large‑scale quantum computers.
2. No disruption today: Existing addresses, wallets, and transaction workflows remain unchanged. Users who do not adopt PQ or hybrid signatures continue to use secp256k1 as before.
3. Developer flexibility: Script authors can experiment with novel cryptographic patterns—covenants, oracle‑driven contracts, or quantum‑root vaults—using a compact, standardized sighash.
4. Transparent upgrade path: The CHIP process ensures a predictable, community‑driven schedule, maintaining BCH’s record of six consecutive, split‑free upgrades (2021‑2026).

---

Looking Ahead

If the lock‑in proceeds smoothly, `OP_SIGHASH` will become a foundational building block for a new generation of BCH applications that demand quantum resilience. Hybrid signatures will let the ecosystem transition gradually, preserving the security guarantees users rely on while adding a robust “bunker” against future quantum threats.

Stakeholders are encouraged to review the full CHIP‑2026‑06 text, test the opcode on testnet, and contribute feedback before the November deadline. As BCH continues to demonstrate disciplined, decentralized upgrades, this proposal could mark another milestone in the network’s evolution toward long‑term security.