The deadline is approaching

On July 13, CoinDesk updated its report that Bitcoin Improvement Proposal 110 (BIP-110) had almost no miner support as its mandatory signaling window approached. At 2026-07-13T10:17:44.869Z, the live monitor reported 1.22% signaling in the current period, or 3 of 245 blocks, leaving the proposal far below its 55% threshold.

BIP-110, formally titled the Reduced Data Temporary Soft Fork, would restrict several ways users place arbitrary data in Bitcoin transactions. Its 55% threshold is far below BIP9's usual 95%, while BIP-110 is not part of Bitcoin Core's released consensus rules. The specification caps OP_RETURN outputs at 83 bytes, limits many data pushes to 256 bytes, and temporarily invalidates several other script patterns that carry data. Supporters say those rules would push block space back toward monetary uses. Critics object to making transactions invalid by consensus when they are valid and already paying a fee.

The proposal uses a modified deployment schedule. Mandatory signaling runs from blocks 961,632 through 963,647, with the change locking in no later than block 963,648. Maximum activation is block 965,664, projected around September 1, and the rules expire after 52,416 active blocks, or roughly one year. Calendar dates remain estimates because block production varies.

Signaling hovers near one percent

Support is not literally zero across the whole campaign. The monitor has recorded a small amount of hashrate, while CoinDesk reported node adoption in the low single digits, concentrated in Bitcoin Knots. That is enough to show a committed minority. It is nowhere near enough to show broad agreement among miners and node operators.

Strategy founder Michael Saylor and Adam Back opposed the proposal publicly on July 11. Back, the Blockstream cofounder whose hashcash work is cited in the Bitcoin white paper, told supporters that their recourse was to fork away if they remained unconvinced. Saylor focused on the precedent of using consensus rules to reject transactions that the network currently accepts. He wrote:

"BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions."

If BIP-110 enforcement begins while nearly all miners continue producing blocks that do not signal, nodes enforcing the proposal would reject those blocks. The likely result under today's reported support is a small minority chain rather than a change across the whole network. That outcome is conditional, not predetermined, because signaling and software adoption can change before the mandatory window.

Why It Matters

Bitcoin's resistance to change comes from independent participants deciding which rules they will enforce. No committee declares consensus for them. BIP-110 has advocates and addresses a real dispute over how block space gets used, but a 55% threshold does not manufacture agreement when observed support remains near 1%. If a minority wants stricter rules, it can run them and accept the chain risk. The broader network's refusal to follow is governance in action: costly, slow, and difficult to capture, exactly as neutral money should be.