BIP-110's August Showdown: 2% Signal, 55% Risk, and Where to Track It Live

BIP-110's current signal is low, but the August deadline already matters

BIP-110 has become an August calendar event as much as a protocol debate. Right now, support is only 13 of 646 blocks, or 2.01%, versus the 55% activation threshold. In practical terms, Bitcoin still needs 1,109-of-2,016 blocks to lock the change in. That is not enough for activation, but it is enough to keep the proposal on the radar because Bitcoin has not seen a consensus rule change since Taproot activated in November 2021.

The base case still does not look like a lasting BTC split or a major asset-risk event. The proposal leaves supply cap, issuance, and existing holdings untouched, so its direct impact on BTC appears limited. The bigger concern is operational: if signaling rises quickly in August, markets and infrastructure providers may have to price a consensus event faster than they expect.

Supporters argue Bitcoin needs hard limits on arbitrary data to keep the network focused on money. Opponents argue the bigger risk is making that dispute a consensus rule, with turning a spam dispute into a consensus change. For investors, that is the core question before August ends.

BIP-110's risk is more operational than monetary

BIP-110 is a one-year soft fork that would change which transactions are valid, not how much bitcoin exists. The proposal leaves supply cap, issuance, and existing holdings untouched, so the direct asset risk looks limited if activation never happens. The real exposure is whether exchanges, wallets, custody systems, and pools suddenly have to react to a new validation rule.

What would actually change

The proposal's mechanism is narrow but concrete. BIP-110 would cap most new outputs at 34 bytes, limit OP_RETURN to 83 bytes, and restrict data pushes to 256 bytes. Supporters argue those limits target arbitrary data while leaving monetary use cases intact. Opponents argue the danger is that the rule would invalidate some currently valid, fee-paying transactions.

That distinction matters. Even with weak signaling, BIP-110 is not just a theoretical debate because the schedule includes a mandatory-signaling checkpoint at block 961,632. Once that window approaches, infrastructure providers have less room to treat the proposal as background noise.

Why low support does not mean no consequence

Skeptics still have a strong case. BIP-110 is close to a non-event for BTC as an asset as long as miner support remains far below the level needed for lock-in. But low probability is not the same as no consequence. If major pools begin signaling after the mandatory window starts, preparation time can shrink quickly.

The watchpoint is simple: watch block production, not ideology. A sharp rise in signaling after block 961,632 would make this an operational risk question for infrastructure and market plumbing.

Where to track BIP-110 live in August

The data sources that matter

If you are tracking this live, start with the signal flag itself: miners indicate support by setting bit 4. From there, use these feeds:

• bip110.org/monitor: the proposal's live dashboard for signaling rate and period progress.
• BGeometrics daily block counts: an independent check on miner signaling.
• Bitcoin Magazine's tracker: another public monitor for current support.

The basic monitoring loop is straightforward: watch the signaling rate, cross-check the block counts, and focus on one question, are block producers actually increasing support?

If the flag remains rare after the mandatory window begins, BIP-110 is more likely to stay a low-probability operational story than a market-moving fork event.