This current juncture represents a profound test of whether a group of Bitcoin developers and users can successfully advance a contentious consensus change without the broad and unequivocal backing of the network’s miners, a scenario that carries the significant risk of physically separating enforcing nodes from the established, dominant chain, thereby potentially escalating a fundamental dispute over the philosophical and practical implications of how Bitcoin’s finite block space should be allocated and utilized, moving beyond its initial purpose as a peer-to-peer electronic cash system. At its core, BIP-110, authored by the pseudonymous developer known as Dathon Ohm, proposes a series of additional, temporary consensus restrictions designed to be in effect for approximately one year, a period deemed sufficient by its proponents to address perceived issues with network congestion and data proliferation. Specifically, the proposal aims to curb the influx of what its supporters categorize as "non-monetary" data by implementing precise byte limits: it would restrict the size of most new output scripts to a maximum of 34 bytes, cap OP_RETURN outputs, which are commonly used for embedding small amounts of arbitrary data, at 83 bytes, limit certain data pushes and witness elements—components of transactions that became more prevalent with Segregated Witness (SegWit) and Taproot—to 256 bytes, and temporarily impose limitations on several features introduced with the Taproot upgrade, such as those related to script path spending. Crucially, any unspent transaction outputs (UTXOs) that were created prior to the activation of BIP-110 would be entirely exempt from these new restrictions, ensuring backward compatibility for existing funds.

The primary motivation behind these proposed restrictions, as articulated by BIP-110’s proponents, is to actively discourage the proliferation of inscriptions and other forms of non-monetary data, which they argue significantly increase the storage and bandwidth costs borne by node operators, thereby potentially centralizing the network by making it more expensive and resource-intensive to run a full node. Inscriptions, which rose to prominence with the Ordinals protocol, leverage Bitcoin’s Taproot upgrade and SegWit architecture to embed arbitrary data, including images, text, and even executable code, directly onto individual satoshis, effectively creating "digital artifacts" on the Bitcoin blockchain; while proponents view this as expanding Bitcoin’s utility and expressiveness, critics, including those supporting BIP-110, perceive it as "spam" that clogs the network, inflates blockchain size, and diverts resources away from Bitcoin’s fundamental purpose as a financial ledger. This perspective posits that such data bloat could lead to higher transaction fees, slower confirmation times, and ultimately erode the accessibility and decentralization of the network by raising the barrier to entry for running a full node, a critical component for verifying transactions and maintaining network integrity.

However, the proposal has drawn sharp criticism from prominent figures within the crypto space, including MicroStrategy Executive Chairman Michael Saylor and Blockstream CEO Adam Back, both of whom have vocally argued that BIP-110 carries the severe risk of dividing the Bitcoin network, potentially leading to a hard fork or a sustained chain split, and critically, causing Bitcoin nodes enforcing the new rules to reject transactions that are perfectly valid and permissible under the network’s existing, established consensus rules. Their arguments, and those of many other critics, often center on the principle of censorship resistance, asserting that restricting the type of data that can be written to the blockchain, even if temporarily, sets a dangerous precedent for future censorship and deviates from Bitcoin’s ethos of open, permissionless access. They contend that Bitcoin’s design, particularly after SegWit and Taproot, inherently allows for various data types, and that attempting to restrict these post-facto could undermine the network’s neutrality and immutability, potentially alienating developers and users who value Bitcoin’s extensibility. Furthermore, the idea of a "minority chain" intentionally rejecting blocks from the "dominant chain" is seen as a highly aggressive and potentially destructive act, reminiscent of past contentious debates like the Block Size Wars, which threatened Bitcoin’s unity and could severely impact its fungibility and perceived reliability.

The mechanics of BIP-110’s deployment schedule are specific and illustrate a calculated attempt to introduce these changes: it utilizes version bit 4 for miner signaling, a standard mechanism for indicating support for a soft fork. The mandatory-signaling window, during which BIP-110 enforcing nodes reject non-signaling blocks, spans blocks 961,632 through 963,647. Following this, the specification defines block 963,648 as the precise beginning of its "locked-in" state, a phase that would typically precede activation if sufficient signaling were achieved, and block 965,664 as the exact point when its transaction restrictions would formally take effect, fundamentally altering how transactions are validated on the BIP-110 chain. This structured deployment, however, now faces the stark reality of insufficient miner buy-in, throwing its future into considerable doubt.

Beyond the initial BIP-110 proposal, its proponents have also openly discussed and prepared for a more extensive and potentially radical fallback plan, signaling the seriousness with which they view the "spam" issue and their commitment to enforcing their vision for Bitcoin’s block space. On August 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work (PoW) change, an extremely significant and rare modification to Bitcoin’s core security mechanism, which was originally written by the long-standing Bitcoin Knots maintainer Luke Dashjr, a developer known for his staunch stance against non-monetary data. Guida explicitly described this rebased code at the time as a "contingency" plan, to be deployed if the network’s miners continued to oppose BIP-110, although he was careful to note that no specific activation date had been set for this drastic measure. A proof-of-work change, unlike a soft fork or a simple set of transaction restrictions, would entail altering the fundamental algorithm that secures Bitcoin, effectively creating an entirely new chain that would be incompatible with the existing Bitcoin network and require a completely separate set of miners and nodes, representing an ultimate escalation in the dispute and a genuine hard fork that would irrevocably split the network. Such a move is widely considered an act of last resort due to its profound implications for network stability, user confidence, and the potential for a permanent fracturing of the Bitcoin ecosystem, highlighting the depth of the ideological chasm that has emerged around the use of Bitcoin’s blockchain.

The broader context of this debate lies within the evolving landscape of Bitcoin’s utility and its governance model. Bitcoin Improvement Proposals (BIPs) are the formal process through which changes to the Bitcoin protocol are proposed, discussed, and eventually implemented, requiring widespread consensus for successful activation, especially for consensus-critical changes like soft forks. The emergence of Ordinals and inscriptions in late 2022 and early 2023 ignited a fierce debate, forcing the community to confront questions about Bitcoin’s "intended use" and whether its permissionless nature should extend to all forms of data, regardless of their perceived monetary value. While some argue that any data written to the blockchain, as long as it adheres to the current protocol rules, is valid and part of Bitcoin’s evolution, others contend that such uses detract from its primary function as a secure, decentralized monetary network, potentially jeopardizing its long-term viability by increasing operational overhead for its most critical infrastructure: full nodes. This tension between maximalist views of Bitcoin as purely monetary and more expansive views of its potential as a general-purpose data layer has been brewing for years, but BIP-110 and the Ordinals phenomenon have brought it to a head. The low miner support for BIP-110, coupled with the discussion of a radical proof-of-work change, underscores the severe challenges in achieving widespread consensus on contentious issues within Bitcoin’s decentralized governance framework, where no single entity holds ultimate authority, leaving the future trajectory of BIP-110, and indeed the broader debate over Bitcoin’s block space, in a state of precarious uncertainty and continued fervent discussion.