Ahead of a hard calendar of block heights, Bitcoin’s BIP-110 is about to flip from polite requests to hard requirements. The mandatory-signaling window is keyed to start at block 961,632. Miner support? Still thin.
By the time this window closes, the proposal is coded to lock in anyway and then activate one period later. That’s the shape of it. The market’s watching a countdown, not a vote.
If you’re seeing pool tags and dashboards tick up a little, you’re not imagining it. But the gap between “some signaling” and “economic readiness” is still wide.
BIP-110 moves into a phase where blocks are expected to carry a specific signal bit during a defined span of heights. This isn’t a popularity contest; it’s an activation process with a safety valve: voluntary early lock-in if signaling crosses a threshold, or a timed lock-in if it doesn’t.
The key point: BIP-110 is scheduled to lock in by a set block even if miners never rally around it, then activate one period after. That design shifts the center of gravity from miner signaling to network timing.
Why now? Because the schedule is on-chain and approaching fast. According to the proposal’s site, the mandatory-signaling window runs from block 961,632 through 963,647, with a hard lock-in no later than block 963,648 and activation at 965,664 one period after that (BIP-110 (official site)).
Who’s affected? Miners who must set the bit, node operators who will enforce post-activation, exchanges/custodians who need policy clarity, and anyone relying on software that needs to be in sync with the rule change.
What BIP-110 Is and How We Got Here
Let’s strip it down. BIP-110 is a consensus rule change being deployed via a version-bit style rollout. The specifics of the rule change itself are not the point of this piece; the timing and activation mechanics are.
Why “mandatory signaling” exists
Mandatory signaling windows exist to force clarity around activation. In earlier activations, prolonged low signaling created uncertainty for months. A mandatory period narrows the window where miners can be ambiguous and gives the rest of the network something deterministic to plan around.
How this differs from past cycles
Past Bitcoin upgrades leaned more on miner thresholds and shorter “speedy trial” windows. Here, early lock-in is still possible if miners coordinate, but the backstop is time-based. If signaling stays low, the process still advances.
The Activation Machinery: Thresholds, Windows, Blocks
There are three moving pieces that matter to anyone tracking this rollout: the mandatory signaling span, the forced lock-in height, and the activation height one difficulty period later.
| Phase | Block range / height | Condition | Notes |
|---|---|---|---|
| Mandatory signaling window | 961,632 to 963,647 | Miners expected to set signal bit | Defined in BIP-110 deployment spec (BIP-110 (official site)) |
| Forced lock-in (no later than) | 963,648 | Locks in regardless of signaling | Early lock-in was possible if threshold was met earlier; otherwise happens here |
| Activation (one period later) | 965,664 | New rules begin enforcement | Standard one-period delay post lock-in |
About that early lock-in threshold
Some trackers referenced a voluntary lock-in threshold around a majority of the period’s blocks. Late-July reporting cited 55% (about 1,109 of 2,016 blocks) as the level that would have enabled an earlier lock-in, which never came close (KuCoin (news)).
Where Signaling Stands and What Changed in July
Short version: miner signaling has been inching up, but it’s still nowhere near a level that would matter for voluntary lock-in. The process is marching forward anyway, by design.
The numbers this period
As of an August 7, 2026 update, the public BIP-110 monitor reported 44 signaling blocks out of 1,777 observed in the current difficulty period (#476), roughly 2.48%, with the chain tip at 961,392 at that timestamp (BIP110Monitor (API)). That’s low, but higher than July’s baseline.
What last period told us
In the prior completed period (#475, blocks 957,600–959,615), the same API recorded just 26 signaling blocks out of 2,016, or about 1.29% (BIP110Monitor (API)). Earlier still, mid-July coverage said miner signaling had never risen above roughly 1% and was at zero at that moment (CoinDesk). By late July, some monitors showed a modest bump to about 2.64% as the mandatory window neared (KuCoin (news)).
What the uptick means (and doesn’t)
That uptick signals more pools flipping the bit. It doesn’t guarantee smooth activation or imply deep operational readiness. Signal bits are cheap to set. Coordinated software updates, policy changes, and risk playbooks are not.
Who Needs to React If Miners Stay on the Sidelines
With mandatory signaling entering, the center of gravity shifts away from miners. The job list lands with node operators and businesses touching Bitcoin transactions.
Miners
Signals will be expected across the mandatory window. Pools that don’t flip the bit during that span could face orphan risk if peers or templates assume signaling. Realistically, many will simply comply with the signaling requirement while waiting out the forced lock-in.
Node operators
Nodes need to be on software that recognizes the deployment and will enforce the new rules at the activation height. This is straightforward but non-negotiable. If you run infra, double-check template providers, mining proxies, transaction policies, and any custom patches. Treat activation like a maintenance window, not a suggestion.
Exchanges and custodians
These desks worry less about signaling metrics and more about safe settlement. The checklist: wallet stack readiness, replay considerations if applicable, deposit/withdrawal halts or delays around activation, and clear client messaging. If the change could affect typical transaction patterns, plan fee and confirmation policies accordingly.
The Next Two Weeks: What to Watch On-Chain
Here’s the practical timeline people will actually feel:
- Mandatory signaling begins at block 961,632. Expect dashboards to light up with more pools flipping bits in templates (BIP-110 (official site)).
- Through block 963,647, miners are expected to keep signaling. Don’t over-interpret daily percentages. They’re noise unless they surge.
- At block 963,648, BIP-110 locks in no matter what signaling showed. That’s the fork decision point baked into the rollout design (BIP-110 (official site)).
- One difficulty period later, at block 965,664, activation hits. New rules begin, nodes that didn’t update are now on borrowed time.
- Immediately post-activation, watch for any short-term reorg noise, miner template adjustments, and whether mempool policy or relay patterns change.
Short-term markers to track
Beyond the raw percentage signals, keep an eye on: the number of distinct pools signaling, whether any large pools publish explicit readiness statements, and exchange status pages around activation. If you manage infra, testnet or signet mirrors are worth a dry run for operational steps.
Post-activation checks
Once activation lands, pay attention to orphan rates and any uptick in transaction failure cases tied to rule enforcement. If nothing shows up, that’s ideal. Quiet activations are the best kind.
Risks & What Could Go Wrong
- Chain split risk if a material minority of hash rate or economic nodes run non-upgraded software at activation.
- Short reorgs around the activation boundary if some miners mine incompatible templates.
- Wallet or service downtime if operators don’t coordinate maintenance windows and policy updates.
- Liquidity hiccups if exchanges pause deposits/withdrawals longer than expected.
- Confusion from misreading signaling as endorsement rather than compliance during the mandatory window.
- Scam risk from fake “upgrade clients” or social engineering targeting node operators and miners.
Don’t confuse low signaling with a delay. The schedule advances with or without it; the risk is operational, not procedural.
Frequently Asked Questions
What exactly is “mandatory signaling” in this context?
It’s a defined window of block heights where miners are expected to set a particular version bit in the blocks they produce. It standardizes behavior across the network before the rule change locks in. It’s not the same as “support” and doesn’t by itself determine whether the change activates.
Can BIP-110 still lock in early if signaling jumps?
Yes. Early lock-in was possible if a threshold of signaling blocks were reached during the voluntary phase. Reporting in late July referenced a 55% threshold (about 1,109 of 2,016 blocks). That never materialized, so the schedule is on track for the time-based lock-in (KuCoin (news)).
When does the mandatory-signaling window start and end?
Per the proposal’s deployment details, the window starts at block 961,632 and runs through 963,647 (BIP-110 (official site)). After that, the proposal locks in no later than 963,648.
What happens at activation?
At activation, set for block 965,664, nodes that enforce BIP-110’s rules begin rejecting blocks or transactions that violate the new rules. From an operator’s perspective, that’s the time to be fully upgraded and monitoring for any short-lived network friction (BIP-110 (official site)).
How low is miner signaling right now?
Recent snapshots: the current period saw about 2.48% signaling at one August 7, 2026 update (44 of 1,777 tracked blocks) (BIP110Monitor (API)). The prior period logged roughly 1.29% (26 of 2,016). Mid-July reporting pegged it near zero at one point (CoinDesk).
What should exchanges and custodians do?
Run through an activation playbook: upgrade nodes, verify wallet stack behavior under the new rules, set conservative deposit/withdrawal policies around activation, and prepare client comms. If nothing breaks, you’ll have over-prepared for a smooth day.
Could there be a tradable event around activation?
Maybe, but it’s not predictable. If activation is quiet, market impact may be minimal. If there’s network turbulence, fees or spreads can widen temporarily. Position sizing and risk controls are on you; this isn’t financial advice.
