18 Nov 2026, Wed

Contentious Bitcoin Improvement Proposal 110 Enters Mandatory-Signaling Phase Amid Low Miner Support

Bitcoin Improvement Proposal 110 (BIP-110) officially entered its mandatory-signaling phase at block 961,632 on Saturday, marking a critical milestone in an ongoing debate over network rules, data bloat, and block space utilization. According to data from the official BIP-110 monitor, participating miners signaled support in just 51 of the preceding 2,016 blocks, translating to a meager 2.53% signaling rate. This figure falls drastically short of the 55% threshold required for the proposal to achieve early activation under normal network conditions.

Starting precisely at block 961,632, specialized nodes enforcing BIP-110 began actively rejecting blocks that failed to set version bit 4. Meanwhile, ordinary Bitcoin nodes across the broader network continued operating under standard consensus rules, accepting both signaling and non-signaling blocks alike. As a direct result of this divergence, a minority BIP-110 branch briefly and subsequently emerged on the network, though it quickly began to fall behind the dominant, majority-supported chain in terms of accumulated work and block production speed.

The exceptionally low signaling rate observed during the opening window makes a sustained, viable rival chain highly improbable unless there is a substantial and sudden surge in miner participation. With relatively sparse mining support backing the initiative, any independent BIP-110 branch faces the very real possibility of advancing at a severely diminished speed or halting block production altogether due to insufficient hash rate.

This high-stakes milestone serves as a definitive test of whether dedicated supporters can successfully advance a contentious consensus change without broad backing from the mining community. Such an attempt carries significant structural risks, potentially separating enforcing nodes from the dominant chain and escalating an ongoing, deeply polarized dispute over how Bitcoin’s limited block space should be allocated and utilized.

BIP-110 Seeks Temporary Limits on Bitcoin Data

Authored by the pseudonymous developer Dathon Ohm, BIP-110 proposes a series of additional consensus restrictions designed to last for a temporary duration of roughly one year. The primary objective of the proposal is to curb the inclusion of non-monetary data, inscriptions, and other auxiliary files that have become increasingly common on the blockchain.

Under the terms of the proposal, most new output scripts would be strictly limited to a maximum of 34 bytes, while OP_RETURN outputs would be capped at 83 bytes. Furthermore, BIP-110 would restrict certain data pushes and witness elements to a maximum of 256 bytes, alongside placing temporary limits on several features associated with the Taproot upgrade. To prevent widespread disruption to existing balances, unspent transaction outputs (UTXOs) created prior to the activation of the proposal would remain entirely exempt from these sweeping restrictions.

Proponents of the measure have argued that these strict limitations are urgently necessary to discourage inscriptions and other forms of non-monetary data. Supporters contend that such data types significantly increase the long-term storage, bandwidth, and processing costs for node operators, threatening the decentralization of the network by making it harder and more expensive to run a fully validating node.

However, the proposal has faced fierce opposition from prominent figures within the cryptocurrency industry. High-profile critics, including Strategy executive chairman Michael Saylor and Blockstream CEO Adam Back, have openly rebuffed the BIP-110 proposal. These leaders and other detractors have argued that pushing forward with such a contentious change could deeply divide the Bitcoin community and cause enforcing nodes to reject legitimate transactions that are entirely permissible under the network’s existing, established rules.

The architectural framework of the proposal utilizes version bit 4 as the designated mechanism for miner signaling. The carefully structured deployment schedule designates blocks 961,632 through 963,647 as a mandatory-signaling window, during which participating nodes enforcing BIP-110 are programmed to reject any blocks that do not carry the required signal.

Looking further ahead in the deployment timeline, the specification formally defines block 963,648 as the official beginning of its locked-in state. Following that milestone, block 965,664 is established as the specific point when the proposed transaction restrictions and data caps would officially take effect across the enforcing network.

In anticipation of potential roadblocks, proponents of BIP-110 have also discussed a more extensive and disruptive fallback option in the event that miners overwhelmingly reject the primary proposal. On Aug. 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work change that was originally authored by longtime Bitcoin Knots maintainer Luke Dashjr.

At the time, Guida described the alternative code as a strategic contingency measure should traditional miners aggressively oppose BIP-110, though he emphasized that no concrete activation date had been established for the alternative proof-of-work mechanism. As the mandatory-signaling window progresses, the eyes of the broader cryptocurrency ecosystem remain fixed on the network to see how the standoff between node operators and miners ultimately unfolds.

Leave a Reply

Your email address will not be published. Required fields are marked *