The Battle for Bitcoin’s Block Space: BIP-110 and the High-Stakes Miner Signaling Crisis

The delicate balance of power governing the world’s largest cryptocurrency faced a major test on Saturday as Bitcoin Improvement Proposal 110 (BIP-110) entered its controversial mandatory-signaling phase. Triggered precisely at block 961,632, this highly anticipated milestone revealed a stark division within the global network: database monitors tracked miner support at a meager 2.53%, with only 51 of the preceding 2,016 blocks actively signaling in favor of the proposal. This fell drastically short of the 55% threshold required for early activation, exposing a profound disconnect between a passionate cohort of developers and the massive mining operations that secure the ledger. As nodes programmed to enforce BIP-110 began systematically rejecting any newly mined blocks that failed to set version bit 4, a minority chain briefly splintered off from the main network, only to quickly fall behind the dominant chain due to its lack of computing power. This dramatic divergence highlighted the limits of attempting to push through a contentious consensus change without broad, industry-wide cooperation. It also raised serious questions about the network’s resilience, demonstrating how a small fraction of validating nodes can easily become isolated when they attempt to dictate terms to a massive, profit-driven mining ecosystem that remains loyal to the economic incentives of the primary blockchain fork.

The Core Conflict: Curbing Inscriptions and the Fight Against Bloat on the Blockchain

At the heart of this ideological and technical standoff is a temporary set of consensus restrictions designed to reshape how Bitcoin’s precious block space is utilized. Drafted by the pseudonymous developer Dathon Ohm, BIP-110 was envisioned as a one-year circuit breaker aimed at curbing the proliferation of arbitrary data on the blockchain, particularly “inscriptions” and metadata associated with the popular Ordinals protocol. To achieve this, the proposal outlines strict limitations on transaction payloads: it caps the vast majority of new output scripts at 34 bytes, restricts OP_RETURN outputs—frequently used to embed non-financial data—to just 83 bytes, and limits specific witness elements and data pushes to 256 bytes. Furthermore, it imposes strict temporary boundaries on several features introduced in the 2021 Taproot upgrade, which critics argue opened the floodgates for non-monetary storage uses. While existing, unspent transaction outputs (UTXOs) created before the activation date are explicitly grandfathered in to prevent the loss of older funds, supporters argue that these aggressive new constraints are absolutely vital. They contend that the rapid growth of data-heavy transactions threatens to price out ordinary users by driving up transaction fees, while simultaneously bloating the ledger and imposing unsustainable storage, bandwidth, and synchronization costs on the independent Bitcoin node operators who form the backbone of the network’s decentralized security model.

Industry Heavyweights Sound the Alarm: Why Michael Saylor and Adam Back Oppose BIP-110

Despite the altruistic intentions of its proponents, BIP-110 has encountered fierce resistance from some of the most influential and respected figures in the cryptocurrency ecosystem. Industry leaders, including MicroStrategy Executive Chairman Michael Saylor and Blockstream CEO Adam Back, have warned that implementing such restrictive consensus changes could severely fracture the network and undermine its core value proposition. Opponents argue that censoring specific types of data or limiting transaction structures goes against Bitcoin’s fundamental philosophy of censorship-resistance and permissionless innovation, transforming the network from an open, neutral utility into a curated ledger governed by subjective rules. They argue that if a transaction pays the necessary market rate in fees, the network should process it without judging its underlying utility, whether it represents a simple peer-to-peer payment, a complex smart contract, or an digital inscription. Furthermore, critics point out that forcing nodes to reject transactions permitted under existing, widely accepted rules introduces systemic risks, potentially triggering a permanent blockchain fork that could confuse users, disrupt decentralized finance applications, and ultimately damage the credibility of the asset as a reliable store of value and global settlement network.

A Quiet Divergence: The Mechanics of the Minority Chain and Node Enforcement

The technical mechanics of the weekend’s fork illustrate the fascinating, automated nature of decentralized consensus. When block 961,632 was reached, ordinary validating nodes continued to operate normally, accepting both signaling and non-signaling blocks based on the established, long-standing rules of the network. However, nodes running specialized software designed to enforce BIP-110 immediately began rejecting any block that did not explicitly carry the version bit 4 signal in its header. This binary ruleset forced an immediate bifurcation: miners who supported BIP-110 attempted to build on top of the few compliant blocks, creating a distinct minority branch of the blockchain. Yet, without a significant share of the global hashrate, this minority chain struggled to find blocks at a normal pace, quickly falling behind the dominant chain in terms of total accumulated proof-of-work. In the proof-of-work model, the chain with the most cumulative difficulty is recognized as the valid history, meaning the lagging BIP-110 branch remains economically unviable and practically unusable for mainstream transactions unless a massive wave of mining power suddenly shifts to support it. This real-time experiment serves as a stark reminder that while node operators hold immense power in validating transactions, they cannot easily force a change on the network if the underlying economic actors and miners refuse to follow their lead.

The Activation Roadmap and the Looming Threat of an Ideological Split

The timeline for the BIP-110 deployment is designed with several distinct phases, setting up a prolonged period of tension across the ecosystem. According to the proposal’s deployment schedule, blocks 961,632 through 963,647 serve as a mandatory-signaling window, during which enforcing nodes will continuously filter out non-compliant blocks. Following this window, the specification designates block 963,648 as the starting point of its “locked-in” state, with block 965,664 marked as the official activation height when the strict transaction data restrictions are supposed to take full effect. This structured, multi-week progression was modeled after past successful upgrades, such as Segregated Witness (SegWit) in 2017 and Taproot in 2021, both of which utilized miner signaling to ensure a smooth transition. However, unlike those historic upgrades, which achieved near-unanimous consensus before activation, BIP-110 is moving forward in a highly polarized environment with virtually no miner backing. If the small group of BIP-110 supporters refuses to back down as these milestones pass, the network could see a permanent, albeit small, parallel chain emerge, representing a persistent ideological split over how Bitcoin should be scaled and whether its primary purpose is to serve as a pure monetary instrument or an all-purpose database.

The Nuclear Option: A Proof-of-Work Contingency and the Future of Bitcoin Governance

As the prospects for miner adoption of BIP-110 look increasingly bleak, some proponents are already looking toward more radical alternatives to assert their vision for the network. In August, prominent developer Chris Guida rebased preliminary code for a highly controversial proof-of-work (PoW) algorithm change, which was originally drafted by veteran Bitcoin Knots maintainer Luke Dashjr. This code represents the “nuclear option” in cryptocurrency governance: a hard fork that would alter the cryptographic hashing algorithm of the network, effectively rendering the multi-billion-dollar fleet of specialized Application-Specific Integrated Circuit (ASIC) mining machines obsolete overnight. While Guida emphasized that this PoW change was merely a contingency plan with no set activation date, its mere existence underscores the depth of the frustration among developers who feel that large mining cartels have monopolized control over the protocol’s evolution. Ultimately, the unfolding BIP-110 drama highlights a fundamental, unresolved question at the very core of decentralized systems: who truly controls the rules of the network—the developers who write the code, the node operators who run it, the miners who secure it, or the users who hold the economic value?