The data suggests that Bitcoin’s block space devoted to non-financial data has increased by over 400% since the Ordinals protocol launched in early 2023. Yet the market barely noticed a quiet proposal—BIP-110—that aims to cut this data to zero. This isn’t a technical patch. It’s a governance ambush, and it threatens to reignite the bitterest schism since the Blocksize War.
If you hold ORDI, SATS, or any token inscribed on the Bitcoin base layer, this article is your early warning radar. BIP-110 may not be a bug fix; it’s a declaration of war against the very idea of a programmable Bitcoin.
The Context: Bitcoin’s Identity Crisis
Bitcoin was born as a peer-to-peer electronic cash system. Over a decade, its dominant narrative shifted to “digital gold”—a store of value with fixed supply, minimal state, and zero smart contracts. That narrative was comfortable for Core developers and long-term holders. Then came the Taproot upgrade in 2021, which opened up script space for complex data. Enter Casey Rodarmor’s Ordinals protocol in January 2023, which turned every satoshi into a canvas for arbitrary data—images, text, even entire HTML pages. BRC-20 tokens followed, a flawed but viral standard that created a new DeFi-esque ecosystem on Bitcoin.
Miners cheered. Inscription fees surged, providing a second revenue stream after the April 2024 halving cut block rewards in half. But Core developers and many maximalists saw only “spam.” Their argument: Bitcoin is not a cheap data storage chain; every byte of non-financial data competes with real transactions, bloats the UTXO set, and degrades the network’s security model.
BIP-110 codifies this hostility. It proposes to limit the amount of non-financial data that can be embedded in a Bitcoin transaction. The specifics are still vague—some versions target OP_RETURN size, others ban certain script patterns used by Ordinals. But the intent is clear: strangle the inscription ecosystem at birth.
The Core: A Surgical Dissection of BIP-110
Tracing the data-capping logic back to the Bitcoin Core codebase reveals a surprisingly simple change. Most of the combat will happen in the validation layer, specifically in the function that checks standardness rules (IsStandardTx). By adding a new policy restricting the total bytes of non-financial data per transaction (or per input), the Core developers can make Ordinals transactions non-standard, meaning nodes will refuse to relay them. Miners, if they follow the majority signaling, would not include them in blocks.
This is a soft fork—no consensus change, just a policy upgrade. But policy forks are the most dangerous kind of governance, because they can be enforced by a minority of node operators without a hard fork. The Bitcoin Core maintainers hold the merge keys. They can merge the change, release a new version (e.g., Bitcoin Core 27.0), and declare that the network is “better.” The market would then face a choice: upgrade or get left behind.
I’ve seen this playbook before. In 2017, the same dynamic led to the SegWit activation via UASF (User-Activated Soft Fork). But SegWit was a genuine technical improvement. BIP-110 is a value judgment masquerading as a protocol optimization. It doesn’t fix any bug; it reorganizes block space allocation based on a philosophical preference.
Let’s run the numbers. Before Ordinals, average block occupancy was around 1 MB out of 4 MB (SegWit-adjusted). Inscription-heavy weeks pushed that to 3.8 MB. Without Ordinals, blocks would become 60% empty, and the fee market would collapse. Miners earned over $200 million in inscription fees in 2023 alone. Post-halving, with block reward at 3.125 BTC, those fees represent 10–30% of total miner revenue. BIP-110 would effectively delete that revenue stream.
Miners, therefore, are the first constituency that will rebel. The second is the developer community building on Bitcoin L1—the teams behind Ordinals, BRC-20, Runes, and even L2s like Stacks and Babylon that rely on Bitcoin’s data availability. If you kill the base layer’s ability to carry metadata, you kill the entire L2/L1 smart contract thesis.
BIP-110’s proponents argue that L2s can use separate data layers (like Cellars or sidechains) and that Bitcoin should remain pristine. But that argument ignores the network effect of cheap data. Ethereum thrives because L2s can post state diffs to L1. If Bitcoin cannot support even minimal metadata, its L2s become isolated federations, not trustless rollups.
The Contrarian Angle: The Real Threat Is Not Ordinals, It’s Governance Capture
Here’s the counterintuitive take that most market participants miss: BIP-110 is not a technical defense of Bitcoin; it’s a power grab by a small group of Core maintainers who want to reassert control over the narrative. The Ordinals boom exposed a fractured community—developers, miners, and users pulling in different directions. BIP-110 is the “solution” proposed by those who believe they know what Bitcoin “should” be.
But centralization of governance is the real vulnerability. If a few maintainers can unilaterally kill an entire ecosystem that the market has validated (hundreds of millions in fees, thousands of developers), then Bitcoin’s decentralized governance is a myth. The decision is being made not by the economic majority (miners, hodlers, exchanges) but by the technical elite who control the pull requests.
Consider the 2017 Blocksize War. The Core developers opposed increasing the block size, even though many miners and businesses (Bitcoin.com, ViaBTC) wanted it. The result was a chain split—Bitcoin Cash was born. BIP-110 could trigger a similar split if miners refuse to enforce the new policy. Already, some mining pools (like F2Pool) have publicly supported Ordinals. A UASF (User-Activated Soft Fork) from the other side could force the hand.
The risk to the ecosystem is not just a hard fork; it’s a loss of trust. If BIP-110 passes without broad consensus, developers will flee to other chains (Litecoin, Dogecoin, Kaspa, or even Ethereum). Bitcoin’s application layer will remain barren for another decade. The “digital gold” narrative will be preserved, but the network will become a zombie—secure, stable, but without growth.
From a security perspective, I worry about the unintended consequences. In 2020, I spent six months modeling Optimistic Rollup fraud proofs and discovered that the 7-day challenge window was insufficient against certain reentrancy attacks. Similarly, BIP-110 may have hidden side effects: it could break certain legitimate protocols that use embedded data for timestamps, contracts, or notarization. The definition of “non-financial” is subjective. Would a hash commit to a legal document be considered non-financial? The policy would need to be enforced by node operators interpreting ambiguous rules—a recipe for censorship.
The Takeaway: A Fork in the Road for Bitcoin’s Soul
BIP-110 is not a done deal—yet. It faces a critical activation deadline (reported as mid-2025) that forces miners to signal support or face a UASF. The next three months will be decisive.
Watch these signals like a hawk: first, the Bitcoin Core GitHub for pull requests containing BIP-110 code. Second, miner signaling from pools like Antpool, F2Pool, and ViaBTC. Third, exchange announcements about BRC-20 listing status. If Binance delists ORDI, the market will price in a 99% probability of BIP-110 activation.
If you are a developer building on Bitcoin L1, start hedging. Consider deploying contracts on alternative L1s (like Stacks or even Ethereum) that won’t be subject to this governance attack. If you are an investor in ordinal-based assets, the time to exit is now—the risk/reward ratio has turned violently negative.
BIP-110 is a test of whether Bitcoin can evolve or whether it will fossilize. The answer will not come from mathematics or code, but from the messy, human process of governance. And as I learned from auditing Uniswap v1’s gas savings: the most elegant code can be undone by the people who control the repository.
Tracing the governance anomaly back to the Bitcoin Core merge process. Trust is a variable we solved for—but it’s not the code that breaches, it’s the consensus. Architecture reveals the true intent: BIP-110 is a wall, not a bridge. The question is whether the community will tear it down before it splits the chain apart.
