Sometime this weekend — around Sunday, August 9, by current block pace — Bitcoin reaches block 961,632, and the most argued-about number in the protocol this year goes live: the start of BIP-110’s mandatory signaling window. From that block through block 963,647, nodes enforcing the proposed “Reduced Data Temporary Softfork” will reject any block that does not signal bit 4, per the activation parameters covered by CryptoSlate and KuCoin. Here is what is actually likely to happen, stripped of the apocalypse framing on both sides.
The math says: no activation this period
BIP-110 — which would cap the size of certain data fields in transactions, targeting Ordinals inscriptions and large OP_RETURN payloads — needs 55% of blocks in a difficulty period to signal support. As of the final stretch before the window, signaling sat between roughly 2.45% and 2.64% — about 40 of 1,561 blocks per KuCoin’s count, or on the order of 5 EH/s of hashrate per Bitcoin.com News. Support comes almost entirely from Ocean and small independent miners; Foundry, Antpool, ViaBTC and F2Pool — the pools that collectively dominate hashrate — have not signaled. Against a 55% threshold, activation in the current period is mathematically impossible. That part is not a prediction; it is arithmetic.
So what does the “mandatory” window actually do?
The drama concentrates in one mechanism: nodes running enforcing software (principally Bitcoin Knots with BIP-110 rules) will treat non-signaling blocks as invalid starting at 961,632. If a meaningful share of hashrate mined under those rules, the network could briefly run two chains — the split scenario that has dominated headlines. But the same arithmetic that dooms activation defangs the split: with under 3% of blocks signaling, the enforcing side would build its chain at a tiny fraction of the network’s speed. Economic activity — exchanges, ETF custodians, payment processors — follows the most-work chain built by the roughly 97% of hashrate mining business-as-usual. The practical risk for an ordinary holder this weekend rounds to: your node, if you run stock Bitcoin Core, follows the heaviest chain and nothing visible happens. The people who need a plan are those who deliberately opted into enforcement.
The loudest wildcard is Luke Dashjr, the Knots maintainer, who per TFTC has threatened a proof-of-work-changing hard fork should BIP-110 fail at the threshold — an escalation that would be a genuinely separate event with its own (vanishingly small) constituency. Threats of last-resort forks have a long Bitcoin pedigree and a short list of realizations.
What happens when the window closes
The likeliest ending is anticlimax. If the period closes below 55% — the mathematically certain outcome absent a mass pool conversion mid-window — BIP-110 simply fails to lock in on this attempt, enforcing nodes face a choice between following the majority chain and continuing to reject it into irrelevance, and the debate returns to mailing lists and podcast feeds where it has lived all year. For holders, the practical guidance is unglamorous: nothing about the window requires action from anyone running standard software, avoid making large time-sensitive transactions during the opening hours if you want to be maximally careful about settlement finality, and be deeply skeptical of anyone marketing “fork insurance,” split-coin claims, or urgent wallet migrations this weekend — contentious-fork moments have historically been phishing season.
The numbers that matter this weekend
| Parameter | Value |
|---|---|
| Window opens | Block 961,632 (~Sunday, Aug 9, 2026) |
| Window closes | Block 963,647 (~2 weeks / one difficulty period) |
| Activation threshold | 55% of blocks signaling bit 4 |
| Signaling entering window | ~2.45–2.64% (~40 of 1,561 blocks; ~5 EH/s) |
| Signaling pools | Ocean + small/independent miners |
| Not signaling | Foundry, Antpool, ViaBTC, F2Pool |
| Next difficulty retarget | ~Tuesday, Aug 11 |
What we are watching, and how we will grade it
Our M3 marker grades Monday on the window’s opening stretch, and we are defining the checklist now, in public: first, whether the blocks immediately after 961,632 include any orphaned or rejected-then-reorged blocks attributable to enforcing miners — the only on-chain fingerprint a split attempt would leave; second, whether any major pool flips its signaling once the window is live (pools have historically waited for windows to open before moving); third, mempool and fee behavior, since a fee spike would be the market’s tell that someone is hedging settlement risk, and none has appeared so far. Note the calendar collision worth savoring: the difficulty retarget lands around Tuesday, August 11 — mid-window — meaning the same period that decides BIP-110’s fate also reprices the hashrate that just declined, by 97-plus percent, to vote for it.
The honest frame for this weekend is that BIP-110’s mandatory window opens as a referendum that has already been counted. The interesting story was never whether 2.6% beats 55% — it is that Bitcoin’s governance pressure valve is being exercised in production, on mainnet, with real money at stake, and the overwhelming economic majority is expressing its preference the only way Bitcoin recognizes: by the blocks it builds. We will report what the chain says Monday.
Disclaimer: This article is for informational and educational purposes only and does not constitute investment, financial, or trading advice. Cryptocurrency markets are highly volatile and you can lose your entire investment. Always do your own research and consult a qualified financial advisor before making investment decisions.