I want to explain what's happening with BIP-110 clearly, because the technical language surrounding this debate has made it easy for most people to tune out, and that would be a mistake heading into August.
Bitcoin is in the middle of a fork fight over a proposal called BIP-110, which would restrict how arbitrary data is embedded in Bitcoin transactions. Supporters argue it keeps the blockchain focused on its core monetary purpose. Critics say filtering valid transactions undermines Bitcoin's neutrality as a permissionless network. The ideological debate has been running for months.
What changed recently is that the debate now has a real operational deadline, and infrastructure teams are starting to pay attention.roads
The Current Numbers Are Extremely Low
Let me be precise about where miner support actually sits. Data through July 2 shows 38 BIP-110 signaling blocks out of 9,066 total blocks since May 1, that's 0.42% support. In the most recent seven-day window, it was 8 out of 1,000 blocks, or 0.8%. For context, miner-driven lock-in requires 1,109 of 2,016 consecutive blocks, 55%, to signal support during a single difficulty adjustment period.
At 0.42%, BIP-110 is nowhere near lock-in through normal miner adoption. What's changed is the alert infrastructure around it.
Farside Investors launched an automated alert system that posts every time a new BIP-110 signaling block is produced. That turns a low-level developer debate into a public, real-time feed that exchanges, wallets, mining pools, and node operators now have to monitor. The July 3 alert confirmed a new signaling block and listed seven in the current period.
Why August Changes Everything
Here's where the timeline gets urgent. The BIP-110 specification includes a mandatory-signaling period running from blocks 961,632 to 963,647, with lock-in happening no later than height 963,648. That window falls in August. Activation would follow roughly two weeks later, with the restrictions remaining in place for approximately one year before expiring.
During the mandatory-signaling window, the proposal's rules say blocks that don't signal bit 4 would be rejected as invalid by enforcing nodes. That's not theoretical, it's the activation path written into the BIP text.
For an exchange, that means deposit, withdrawal, and confirmation policies need to account for a potential contentious fork scenario. Wallet teams need to verify Taproot and Miniscript compatibility because the BIP text specifically acknowledges very unlikely scenarios in which funds could be frozen or lost. Mining pools need a clear version-bit policy. Node operators need to know whether their software enforces BIP-110 rules during the mandatory-signaling window.
What Could Actually Flip This
BGeometrics, which publishes the daily BIP-110 signaling data, noted something important in its background analysis: current signaling patterns look consistent with individual miners or smaller operations. No major pool has committed to signaling.
That's the variable that matters most. Foundry USA and Antpool collectively control significant enough hashrate that a decision by either to start signaling would move daily figures from low single digits toward a range where the 55% threshold becomes worth discussing seriously. Without that kind of pool-level commitment, the miner lock-in route remains genuinely remote.
But the mandatory-signaling fallback removes the need for voluntary miner consensus above a threshold. That's the mechanism that makes August matter regardless of where voluntary support sits today.
What I'm Watching Going Into August
I've been watching Bitcoin's technical governance debates for years, and what makes BIP-110 different from previous debates is the combination of a built-in mandatory deadline and a public alert feed that keeps it visible to operational teams rather than just developers on mailing lists.
A small campaign with a fixed calendar problem is a different kind of risk from a large campaign with no timeline. Even if BIP-110 never reaches 55% voluntary miner support, the mandatory-signaling window means exchanges and infrastructure providers have to build procedures for it anyway, and those procedures need to exist before August, not after.
Whether this activates, gets abandoned, or gets resolved through large pool statements in the next few weeks is what I'm watching most closely. The July 4 data will tell us whether the signal is growing. The August window will tell us whether Bitcoin's most contentious fork fight in years actually becomes a live operational event.