The signal is weak. Across the Bitcoin network, only 2.64% of mined blocks have waved the flag for BIP-110 — a soft fork proposing to cap transaction data sizes. In any other context, this would be a footnote, a dead proposal awaiting archival. But here’s the twist: the mandatory signal window is about to open. No threshold needed. Just a date on the calendar when upgraded nodes will begin rejecting blocks from miners who didn’t signal support.
I’ve seen this pattern before. During the 2020 DeFi Summer, I tracked impermanent loss traps across fifty protocol dashboards. The numbers told a story the headlines ignored. Now, the 2.64% tells me something else — not about technical feasibility, but about the cultural war simmering under Bitcoin’s pristine surface.
Code speaks, but culture listens. And this culture is fractured.
Context: The Anatomy of a Proxy War
BIP-110 stands for "Reduced Data Temporary Softfork." Its goal is simple: limit the size of transaction witness data and OP_RETURN outputs. Practically, it’s aimed squarely at Ordinals inscriptions — those JPEGs and text strings that turned Bitcoin into a pseudo-NFT platform starting in 2023. To proponents, BIP-110 is a cleanup; to opponents, it’s an illegitimate attack on permissionless innovation.
The proposal uses a modified BIP-8 activation mechanism. Miners signal support by setting a specific bit in block headers. Once a predefined block height is reached—regardless of support percentage—nodes running the upgraded software will treat any block without the signal as invalid. This is the "mandatory signal window." It’s a forced deadline.
Currently, support sits at 2.64%. Even factoring in uncommitted hash rate, that’s barely a whisper. Foundry USA, Antpool, ViaBTC — the largest pools have not signaled. Their silence speaks louder than any vote. Ocean, the small pool run by Bitcoin purists, is the main supporter. But Ocean’s hash share is negligible.
So why is this article being written? Because the window is opening. And if history teaches anything, it’s that software forks don’t need majority to create chaos—they only need a determined minority.
Core: The Machinery of Forced Consensus
Let’s peel back the technical layers. BIP-110 modifies two main areas: the maximum size of each transaction’s witness data (originally limited by SegWit) and the number of OP_RETURN outputs allowed per transaction. Current limits already exist, but the proposal lowers them significantly—from 80 bytes per OP_RETURN to 40, and from no explicit global limit on witness data to a hard cap of 400 bytes per transaction.
Why these numbers? Because they effectively kill Ordinals inscriptions, which often embed kilobytes of data inside witness fields. The proposal’s name includes "Temporary" — suggesting a one-year sunset clause. But as any software engineer knows, temporary restrictions tend to become permanent once adopted.
The activation mechanism is the key risk. The mandatory signal window forces miners to choose: either upgrade and include the signal, or risk their blocks being orphaned by upgraded nodes. If only 2.64% of hash rate signals, but those nodes are running BIP-110, then after the window opens, they will reject all blocks from non-signaling miners. A minority chain emerges.
However, Bitcoin’s longest-chain rule means the majority hash rate chain continues uninterrupted. The minority chain, composed only of upgraded nodes, will have a tiny fraction of the hashrate. Its blocks will be orphaned by the rest of the network within minutes. The practical result: nothing. A ghost chain.
But here’s the dark scenario: what if a major exchange or wallet provider upgrades its nodes? They could inadvertently follow the minority chain, causing temporary transaction confirmations that later disappear. "Another rug pull? Or just another myth?" — that’s what I wrote in my 2021 NFT Anthropologist newsletter when a similar soft fork failed. The myth is that Bitcoin’s governance is purely democratic miner vote. The reality is that disputes are resolved not by votes, but by economics and social pressure.
During the 2022 bear market, I studied modular blockchain theses while others fled. I spent weekends in Celestia Discord servers debating sharding economics. That experience taught me one thing: when a proposal has almost no support, its advocates often resort to social coercion or code-level trickery. BIP-110’s forced window is a form of trickery — it assumes that miners will eventually capitulate to avoid creating a split. But miners aren’t paying attention. They care about profitability, and Ordinals fees have been a significant revenue stream.
Foundry’s voting mechanism amplifies this. They poll each client’s average hashrate and switch pool policy when >51% of clients agree. Since most institutional miners likely want to keep inscription fees flowing, they never instructed Foundry to signal. The 2.64% support likely comes from ideological solo miners.
Systemic Risk Cartographer’s note: the risk here isn’t a chain split—it’s the precedent. If a future BIP with similarly low support forces a window, it could be weaponized by a powerful minority to impose unwanted changes. Bitcoin’s defense against this is the economic majority, but the code doesn’t care about majority—only consensus rules.
Contrarian: The Real Attack Isn’t on Ordinals—It’s on Narrative Neutrality
Here’s the counter-intuitive truth most analysts miss. The conventional narrative frames BIP-110 as a battle over block space: pure Bitcoin vs. noisy NFTs. But the deeper conflict is about narrative neutrality — the idea that Bitcoin should not encode any particular use case preference.
By attempting to cap data fields, BIP-110 signals that certain uses (like financial transfers) are legitimate while others (like digital art) are not. That’s a value judgment embedded in protocol rules. Once you open that door, where does it stop? Could a future soft fork ban transaction types linked to privacy mixers? Could it enforce compliance with OFAC sanctions through code?
The Cassandra complex is real. In 2017, while reverse-engineering the Zeppelin Security Library, I realized that every technical safeguard carries an implicit worldview. The developers who wrote those contracts assumed certain trust models. BIP-110 assumes that Bitcoin should remain "store of value" and not "smart contract platform." But who gets to decide?
The proposal’s low support actually validates the opposite: the majority of miners and node operators prefer to keep Bitcoin neutral. They don’t want protocol-level censorship of data. They recognize that the second you start parsing transaction content, you introduce slippery-slope governance.
Proponents argue that enormous inscriptions bloat the UTXO set and harm full node operability. That’s a legitimate technical concern. But the solution shouldn’t be a forced soft fork with virtually no consensus. Better solutions already exist—like node operators voluntarily rejecting large transactions (a policy many already implement), or using off-chain data availability layers. The BIP-110 approach is a sledgehammer where a scalpel would suffice.
I’ve seen this dynamic in other ecosystems. During the Bitcoin Cash split, the minority chain argued for larger blocks under a similar "temporary" soft fork. It ended in a messy hard fork. BIP-110 tries to avoid that by using a soft fork, but the mandatory window creates a coercive environment. Even if it fails, the attempt fractures community trust.
Takeaway: The Next Narrative Shift
So what happens next? I anticipate one of two outcomes.
Scenario A (70% probability): The mandatory window opens, upgraded nodes reject non-signaling blocks, the minority chain sputters and dies within hours. The Ordinals community celebrates, but the underlying tension remains. Attention will pivot to Bitcoin layer-2 solutions (like RGB, Taproot Assets, or BitVM) that can offload data without congesting the base layer. The narrative shifts from "block space war" to "scaling through modularity."
Scenario B (30% probability): A mid-tier mining pool (like such as ViaBTC or F2Pool) suddenly signals support, pushing the count above 10%. This triggers panic among Ordinals users and creates short-term price volatility. But without Foundry’s support, the threshold remains unreachable. The forced window becomes a flash in the pan.
In either case, the real story is Bitcoin’s governance maturation. The 2025 regulatory clarity wave I predicted in my institutional consulting work is here. Regulators are watching how Bitcoin resolves internal disputes. A messy forced fork would harm its reputation as a "settlement layer." A quiet failure confirms its robustness.
My advice to readers: ignore the noise. Focus on layer-2 infrastructure and the growing adoption of Bitcoin as collateral in DeFi. BIP-110 is a passing storm in a teacup. The real narrative is unfolding elsewhere—in the code that enables Bitcoin to scale without sacrificing its neutral, permissionless soul.
Code speaks, but culture listens. And Bitcoin’s culture is resilient enough to survive a 2.64% rebellion.