Bitcoin's Aug. 8 Test: BIP-110 Could Split Hashrate at Block 961,632

Block 961,632 Is a Market Risk, Not Just a Developer Debate

This is a low-probability, high-damage scenario for BTC liquidity and sentiment, not a routine developer dispute. Bitcoin's last consensus change was Taproot in November 2021, and nothing has altered the rules since, leaving the network in an unusually calm stretch. After a period like that, even a narrow activation dispute can push traders from fundamentals into split-risk mode.

At block 961,632, the mechanics change. Under BIP-110, blocks without miner signaling could become invalid to BIP-110-enforcing nodes if mandatory signaling begins. If support stays thin, that is not a smooth backward-compatible path. It is the kind of situation where exchanges, custodians, and liquidity providers may need to respond before the outcome is fully clear.

BIP-110 backers argue the bigger risk is doing nothing. The proposal's author has warned that Bitcoin Core could become insecure once mandatory signaling begins and that blocks without signaling would become invalid to BIP-110 nodes. Saylor sees it differently: with only 2.6% miner signaling, he argues BIP-110 will stall or fork into irrelevance while Bitcoin continues normally. That is why the debate matters now. Bulls see noise; bears see split risk.

The Real Question at Block 961,632 Is What Hashrate Does

After the longest quiet stretch in Bitcoin's history, the issue at block 961,632 is straightforward: if BIP-110 activates, blocks without versionbit 4 become invalid to BIP-110 nodes. That turns a spam debate into a hashrate math problem.

Scenario 1: The no-op

Most miners ignore versionbit 4, BIP-110 never meaningfully activates, and Bitcoin keeps going. That would be the cleanest split-risk exit. Critics already lean that way because Bitcoin Core - still by far the most-used Bitcoin implementation - has not adopted BIP-110, and Saylor argues the proposed cure is more dangerous than the condition.

Even so, "no activation" would not mean BIP-110's premise won credibility. It would only mean the network avoided a live split event.

Scenario 2: Full activation

Miners signal strongly, BIP-110 enforces, and the new rule set takes hold. Proponents are pushing that direction, telling miners to upgrade to a BIP110-enforcing node and warning that delay increases disruption once mandatory signaling begins.

Still, clean activation would not automatically be bullish. A forceful soft-fork battle can clarify rules, but it can also strain confidence in Bitcoin's upgrade process.

Scenario 3: The thin split

This is the middle path neither camp wants to advertise: a split, two chains with no hard fork and no clean resolution. Right now, signaling is variously reported around 1% miner support and 2.6% miner signaling. At that level of support, the mechanical result could be roughly one block every 17 hours on a minority chain.

That is the dangerous zone: not dead, not dominant, but weak enough to persist.

Why a thin chain matters

A thin split is not just a headline event. It can create a slow feedback loop in which a weakly supported chain lingers long enough to complicate finality, node behavior, audits, and custody. For investors, that matters more than the underlying spam debate.

What Traders, Custodians, and Miners Should Watch

That thin-chain setup stops being theoretical the moment the signaling window closes.

The signposts that matter

The best-case signpost is simple: wallets, exchanges, and custodians see no rule divergence, no surprise forked asset, and no lasting uncertainty around chain separation.

The worse signpost is more concerning. A minority chain starts producing blocks at about one block every 17 hours. That would not look like a clean fork event. It would look more like a slow-moving liquidity and operations problem, because two chains with no hard fork and no clean resolution is exactly the kind of split that can complicate nodes, audits, and custody controls.

Replay risk is the user issue

This is not only a market story. It is also a user-safety issue. If the network splits, holders can initially end up with coins on both chains. The danger rises if someone tries to sell the forked coin and the same signed transaction is still accepted on the main chain. That is why developers have warned users to avoid moving coins until the chains can be safely separated.

That matters even more for institutions. Custodians are not just watching price. They are tracking potential client entitlements across incompatible histories.

What would prove the split risk is fading?

A few practical watchpoints matter more than rhetoric: - whether a minority chain keeps producing blocks at roughly one block every 17 hours - whether BIP-110 nodes are actually treating blocks as invalid after block 961,632 - whether users face the risk that the same signed transaction could potentially be used on the main Bitcoin chain

If persistent block production, invalidation, and replay exposure stay absent, the scenario loses force.