Executive Overview
Triggered at block 961,632, this milestone marks the beginning of a high-stakes stress test for the network. It probes whether a passionate faction of developers and node runners can successfully enforce a consensus change without broad-based backing from the mining community.
The initial rollout yielded low miner support, with only 51 out of the preceding 2,016 blocks (2.53%) signaling adherence to version bit 4. This falls dramatically short of the 55% threshold required for early activation. Consequently, enforcing nodes have begun rejecting non-signaling blocks, spawning a fragile minority chain that risks stalling or falling hopelessly behind the dominant network.
Authored by pseudonymous developer Dathon Ohm, BIP-110 targets rising storage, bandwidth, and state-bloat concerns driven by ordinals, inscriptions, and other data payloads. By temporarily clamping down on output scripts, OP_RETURN sizes, and specific Taproot features, proponents hope to reclaim Bitcoin’s primary identity as a peer-to-peer monetary network.
However, the proposal has ignited an ideological and technical war. High-profile figures, including Strategy Executive Chairman Michael Saylor and Blockstream CEO Adam Back, have fiercely rebuffed the initiative, warning that it threatens to fracture the network and create incompatible transaction processing standards.
With minority factions even discussing nuclear options like proof-of-work (PoW) algorithm changes, the Bitcoin ecosystem finds itself at a historical crossroads. This report provides a comprehensive, investigative breakdown of the mechanics, metrics, controversies, and future outlook surrounding BIP-110.
Detailed Chronology: The Road to Block 961,632
The journey toward BIP-110’s activation phase has been characterized by escalating tensions between node operators, developers, and mining pools. Understanding the timeline of this deployment sheds light on the mechanics of modern Bitcoin soft/hard fork dynamics and the risks associated with minority forks.
Genesis and Conceptualization
BIP-110 first gained serious traction as discontent grew over the proliferation of arbitrary data on the Bitcoin blockchain. Inscriptions, BRC-20 tokens, and similar phenomena drove up mempool congestion and pushed transaction fee markets to levels that alienated traditional monetary users.
Dathon Ohm stepped forward to author the proposal, framing it as a defensive mechanism to protect the decentralization of full nodes. By making it cost-prohibitive or outright impossible to anchor massive data blobs into block space, the proposal aims to preserve the ability of hobbyists to run full nodes on consumer-grade hardware.
The Signaling Window and Block 961,632
The specification established a rigid deployment schedule utilizing version bit 4 for miner signaling. The mandatory-signaling window officially opened at block 961,632 and is scheduled to run through block 963,647.
During this window, nodes enforcing BIP-110 actively screen incoming blocks. Any block failing to set version bit 4 is rejected by these localized enforcement nodes, effectively drawing a line in the sand between compliant and non-compliant software environments.
Concurrently, ordinary Bitcoin nodes—comprising the vast majority of the network—continue to accept both signaling and non-signaling blocks, treating the signaling bits as standard network noise.
As anticipated by pre-activation metrics, the divergence point at block 961,632 resulted in the immediate emergence of a minority BIP-110 branch. However, because miners controlling the lion’s share of network hash rate did not signal support, this minority chain immediately suffered from abysmal block-production rates. Without substantial hash rate migration, transactions processed exclusively on the BIP-110 branch face immense confirmation delays, underscoring the structural safety mechanisms inherent in Bitcoin’s proof-of-share consensus model.
Upcoming Milestones
According to the proposal’s technical roadmap, subsequent critical thresholds include:
- Block 963,648: The designated beginning of the proposal’s locked-in state, provided conditions are met.
- Block 965,664: The final activation point where transaction restrictions and data caps formally take effect on compliant software branches.
However, given the anemic miner participation observed in the opening hours of the signaling window, reaching these subsequent milestones organically on the dominant hash rate chain remains mathematically improbable.
Supporting Context & Metrics: The Anatomy of a Minority Fork
To fully grasp the implications of BIP-110, one must analyze the raw data, structural constraints, and economic incentives driving the current "spam wars" within the Bitcoin ecosystem.
The Numbers Behind the Signaling
According to data compiled by the BIP-110 monitor, miners signaled support in a mere 2.53% of the 2,016 blocks leading up to the mandatory-signaling window. Out of the 2,016 evaluation slots, only 51 blocks carried version bit 4.
This is far below the 55% threshold required for a smooth, early activation sequence.
Furthermore, network telemetry tracking the adoption of BIP-110-enforcing node software indicates that while adoption has ticked upward—surpassing the 2% milestone among reachable full nodes—this software layer remains vastly outnumbered by vanilla Bitcoin Core implementations and alternative client implementations that reject the proposed consensus tweaks.
What BIP-110 Actually Changes
To understand why miners and prominent industry leaders are resisting the proposal, one must examine its core technical restrictions. BIP-110 proposes a mandatory, roughly one-year restriction on several core transaction formats:
- Output Script Limits: Most new output scripts are restricted to a maximum size of 34 bytes.
OP_RETURNCaps: The data payload capability ofOP_RETURNoutputs is strictly capped at 83 bytes.- Data Pushes and Witness Elements: Certain data pushes and witness elements are capped at a maximum of 256 bytes.
- Taproot Restrictions: Several advanced Taproot features and path constructs are temporarily disabled or severely restricted.
- UTXO Exemption: To prevent catastrophic accounting failures, Unspent Transaction Outputs (UTXOs) created before the activation of BIP-110 are explicitly exempt from these restrictions.
Proponents argue that these limits are surgical interventions designed to strangle inscription-based protocols without harming legitimate Layer 2 protocols like the Lightning Network. Conversely, critics argue that arbitrarily capping script sizes and Taproot functionality sets a dangerous precedent of censorship and protocol regression.
The Threat of a Proof-of-Work Contingency
Perhaps the most alarming metric for institutional observers is the fallback plan discussed by hardcore proponents of the anti-spam movement. On August 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work (PoW) algorithm change.
Originally drafted by Bitcoin Knots maintainer Luke Dashjr, this code serves as a nuclear contingency. If miners continuously stonewall BIP-110 and refuse to dedicate hash rate to the enforcing branch, radical proponents could theoretically activate a PoW change, forcing an entirely new mining puzzle that renders existing ASICs obsolete for that specific chain.
While Guida noted at the time that no formal activation date has been set for the PoW shift, its mere existence highlights the profound ideological fracture currently gripping the developer community.
Official Statements and Industry Reactions
The debate over BIP-110 has exposed deep philosophical divides regarding Bitcoin’s long-term utility, censorship resistance, and upgrade governance. Industry leaders have been vocal, lining up on opposing sides of the ideological aisle.
The Anti-BIP-110 Coalition: Protecting Open Access
Institutional heavyweights have overwhelmingly condemned BIP-110, framing it as an authoritarian attempt by a vocal minority of developers to rewrite the social contract of Bitcoin.
Strategy Executive Chairman Michael Saylor has been among the most prominent critics, arguing that attempts to artificially restrict block space usage undermine the open, permissionless nature of the network. Saylor and his contemporaries emphasize that Bitcoin’s security budget relies heavily on robust transaction fee markets, which are artificially stimulated by diverse block space demand—including inscriptions.
Blockstream CEO Adam Back has similarly rebuffed the proposal. Back, a legendary cryptographer whose prior work heavily influenced Bitcoin’s creation, warned that deploying BIP-110 outside of a broad, overwhelming consensus creates unnecessary chain splits. According to Back and other core purists, introducing rules that cause validating nodes to reject valid transactions under existing protocol consensus is a recipe for catastrophic ecosystem fragmentation.
Critics also point out the dangers of "soft-fork user activation" (UASF) tactics when attempted without overwhelming economic and mining backing. Without miners to secure the chain, a minority fork is highly vulnerable to reorganization attacks, double-spending, and eventual economic irrelevance.
The Pro-BIP-110 Defense: Defending Node Sovereignty
Conversely, supporters of BIP-110 view the initiative not as an attack on Bitcoin, but as a vital defense mechanism against the degradation of network decentralization.
Proponents argue that the unchecked growth of the UTXO set and historical blockchain bloat penalize ordinary node operators. When running a full node requires enterprise-grade solid-state drives and gigabit fiber connections due to gigabyte-sized inscriptions, decentralization is sacrificed. In this view, home miners and grassroots node operators are being priced out of verification, concentrating power in the hands of corporate data centers and institutional mining cartels.
Dathon Ohm and supporting developers contend that temporary guardrails are necessary to allow the network to digest technological innovations safely without being overwhelmed by data-storage abuse. They maintain that node operators—those who independently verify the rules—hold ultimate sovereignty over what constitutes valid Bitcoin, regardless of what miners choose to package into blocks.
Future Outlook: Where Does the Network Go From Here?
As the mandatory-signaling window progresses toward its conclusion, the immediate future of BIP-110 appears grim for its supporters, yet rich with lessons for future network governance.
1. Fizzling Out of the Minority Branch
Given the meager 2.53% signaling rate, the BIP-110 minority branch faces insurmountable economic and operational gravity. Without a sudden, coordinated migration of industrial hash rate—an outcome market analysts view as practically impossible—the minority chain will likely crawl forward at a glacial pace or experience complete block production halts. Users and exchanges relying on standard node implementations will continue operating on the dominant chain, rendering the BIP-110 branch an isolated sandbox experiment.
2. Deepening Cultural and Ideological Rifts
The failure of BIP-110 to achieve consensus does not mean the underlying grievances will disappear. The "spam wars" over inscriptions, ordinals, and block space utility will rage on. Developers who feel alienated by the current trajectory of Bitcoin core development may continue to explore radical alternatives, including further iterations of client-enforced soft forks or alternative implementations like Bitcoin Knots patches.
3. Precedent for Future Upgrades
The deployment of BIP-110 will serve as a heavily analyzed case study in Bitcoin governance. It demonstrates both the resilience of the system against minority takeovers and the immense difficulty of enacting contentious changes in a decentralized environment where economic incentives and miner alignments dictate physical reality.
For now, the dominant Bitcoin network continues to function under its established consensus rules, proving once again that changing Bitcoin’s foundational parameters requires far more than ideological passion—it requires overwhelming, undeniable consensus across miners, developers, and economic actors alike.
