Bitcoin Cash

Bitcoin Cash's Quantum Proposal: Does It Affect You?

A Bitcoin Cash proposal to add quantum-resistant signatures faces a possible Nov. 15, 2026 lock-in. Here is what it does, and doesn't, mean for you.

A new signature waits at a gate not yet open: a green tile passes an open window on the teal route, a gray tile stops at a closed gate. Tess stands calm at lower right, watching.

On November 5, 2026, a technical proposal called CHIP-2026-06 drew fresh attention to Bitcoin Cash's quantum-resistant signature plans, the question of what happens to coins secured by today's signature scheme if a quantum computer capable of breaking it is ever actually built. The proposal, formally titled "Post-Quantum and Hybrid Signatures," is moving through Bitcoin Cash's standard CHIP process right now, with developers discussing a possible lock-in decision as early as November 15, 2026, and a mainnet activation targeted for May 15, 2027, if that lock-in happens on schedule.

None of those dates are guaranteed yet. A contributor to the proposal's own discussion thread on Bitcoin Cash Research's CHIP-2026-06 forum has said the first target signature scheme is SPHINCS+ and a hybrid variant of it, with lattice-based alternatives deliberately deferred to a later stage. That's a narrower, more cautious scope than some outside coverage has implied, and it's worth reading from the source rather than a summary if the mechanics actually matter to you.

Whether any of this changes what you do this week depends less on the calendar and more on what you actually do with Bitcoin Cash. Use the checklist below to find out.

The Checklist: Does Bitcoin Cash's Quantum-Resistant Plan Change Anything This Week?

  • Do you hold Bitcoin Cash in an address whose signature scheme you've never checked, meaning you don't know whether it uses the standard signatures CHIP-2026-06 is designed to eventually supplement?
  • Do you run software, a wallet, or a mining payout path that would need an update to recognize a new signature type once one actually exists on the network?
  • Are you making any decision today, about custody, about mining, about holding BCH long term, based on an assumption that quantum computers capable of breaking current signatures already exist or are imminent?
  • Have you confirmed, from the CHIP's own text rather than a secondhand summary, which specific signature scheme is actually being proposed and what stage of review it's at?
  • Does your current setup depend on a specific lock-in or activation date that hasn't actually been confirmed yet by the project itself?

If you answered no to all five, which is true for the overwhelming majority of Bitcoin Cash users today, the honest answer is that this changes nothing about what you do this week. CHIP-2026-06 is a proposal under live discussion, not a shipped feature, and no current Bitcoin Cash signature is broken today by any known attack, quantum or otherwise.

What "Lock-In" Actually Means, and What It Doesn't

A CHIP lock-in is a decision point in Bitcoin Cash's upgrade process, not a switch being flipped on mainnet. Locking in a proposal on a date like November 15 means the specification is considered settled enough that node and wallet developers can start building against it with confidence it won't change underneath them. Activation, the point where the new rule actually takes effect on the live network, is a separate, later date, here targeted for May 15, 2027. Between those two dates sits months of implementation, testing, and the ordinary process by which miners, exchanges, and wallet developers upgrade their software before a rule goes live anywhere. A reader who assumes "locked in" means "live" is working from the wrong model, and a reader who assumes a CHIP still under forum discussion is already decided is working from an even further wrong one.

It's also worth being honest about what triggered this proposal in the first place. The discussion around it describes a threat that researchers consider worth designing for now, precisely because a transition like this takes years, not days, to build, test, and roll out safely. That's different from a claim that the threat has already arrived. Treating a multi-year engineering runway as proof of urgency, and treating that same runway as proof there's nothing to think about, are both overreactions to the same set of facts.

Where NexusPool Fits, and Where It Doesn't

NexusPool supports solo mining on Bitcoin Cash alongside Bitcoin, Litecoin, and Dogecoin, which makes a protocol-level change like CHIP-2026-06 relevant to how the pool builds blocks on that chain. It isn't something NexusPool has any role in deciding. The pool doesn't write BIPs or CHIPs, and nothing here should be read as NexusPool taking a position on whether this specific proposal should lock in on November 15 or any other date. What NexusPool can speak to honestly is the question this whole story is really about: whether a claim can be verified directly instead of taken on trust.

That's the same logic behind the pool's own signed accounting. Each hour, NexusPool signs a receipt for the shares it counted from your rig, using BIP340, against a key it publishes, so you can check it with any BIP340 library rather than trusting a dashboard. That's the Glass Ledger, and it exists for the same reason a CHIP's actual text matters more than a press release summarizing it: a claim you can check yourself is worth more than one you're asked to simply believe. On the payout side, a 0% pool fee and a coinbase built to pay your own address directly mean there's no pool-held balance sitting between a found block and your wallet. The Payout Preflight tool shows the exact coinbase that would pay you on the current block, before any block is actually found. The whole reward goes to your address. Check it before you mine.

To be clear about what this post isn't claiming: it isn't saying quantum computers can break Bitcoin Cash signatures today, it isn't predicting whether CHIP-2026-06 locks in on November 15 or any other date, it isn't investment advice, it isn't a claim that any pool changes your odds of finding a block (network difficulty sets the odds on each hash, and no pool can change them), and it isn't a claim that NexusPool's own source code is open for public review, which it is not. It's one proposal, moving through one open technical process, that most users can safely watch rather than act on this week.

If None of the Boxes Applied to You

If you checked no across the board, keep doing what you were already doing, and bookmark the CHIP thread if you want to watch the actual decision rather than a summary of it. If you checked yes to even one box, specifically the one about running software that would need updating for a new signature type, treat that as a note to revisit once, and if, CHIP-2026-06 actually locks in, not as something to act on today.

Trust nothing. Verify what a lock-in decision actually changes before you decide it changes anything for you.