We didn't think it would come to this. But the code is set. BIP-110 — the proposal to strangle Ordinals at the consensus layer — has a mandatory activation date. And the countdown is real. The forced activation window opens in August, and the silence from the market is deafening. Most traders are scrolling past this, assuming it's just another FUD wave. They're wrong.
Here's the reality: Bitcoin is about to face its most brutal governance crisis since 2017. The soul of the network — digital cash versus a decentralized data layer — is being fought in the trenches of UTXO rules and OP_RETURN limits. And the outcome will reshape everything you think you know about BTC.
— Root: The conflict is not about spam. It's about who owns Bitcoin's block space.
Let me break down why this matter is moving from fringe debate to live action.
## Context: The Battle Lines BIP-110, authored by Dathon Ohm with an initial draft from Bitcoin Core's Luke Dashjr, aims to cap non-transaction data at 256 bytes per output. The target? Ordinals inscriptions — those JPEGs and text files that turned Bitcoin into a canvas for digital artifacts. The purist camp calls them spam, bloating the UTXO set and forcing volunteers to store data they never asked for. The innovation camp sees them as proof that Bitcoin's utility extends beyond value transfer.
Since Ordinals launched in early 2023, over 50 million inscriptions have been minted. Runes, the fungible token protocol built by the same team, briefly pushed transaction fees up 32% in October 2024. Miners were ecstatic — extra revenue without dilution. Core developers were horrified.
Now BIP-110 tries to pull the emergency brake. But here's the twist: the activation mechanism doesn't require miner majority. It's a forced mandate. Upgrade your node or your blocks get rejected by the new rule. This isn't rough consensus. This is a coup.
## Core: The Technical Chess Match Let's get into the gears. BIP-110's byte limit is blunt. Any transaction containing outputs with more than 256 bytes of arbitrary data becomes invalid. No exceptions. Ordinals, as currently implemented, rely on storing full files — often 100KB or more — across multiple inputs. They'd be dead on arrival.
But the Ordinals devs — Casey Rodarmor and lifofifoX — didn't blink. They proposed a workaround: fragment the data into 256-byte chunks, each in a separate output. A 100KB image becomes 400 outputs. Each chunk stays under the limit. The transaction is technically compliant. But the block space required skyrockets.
s Demo — the proof-of-concept code was already pushed to a test branch. It works. But at what cost? A single large inscription could consume the entire block. Fees would explode not from demand, but from fragmentation. The very problem BIP-110 aimed to solve — bloated UTXO sets — would amplify by an order of magnitude.
This is the irony: the workaround makes the problem worse. It's a technical middle finger, designed to show that you cannot kill an idea by squeezing the pipe. You only force it to become more aggressive.
Now factor in miner incentives. As of July 2025, less than 1% of blocks signal support for BIP-110. Miners are voting with their hash — they like the fee income from Ordinals and Runes. If forced activation triggers a chain split, most hashrate will likely stay on the non-BIP-110 chain. That chain — let's call it "Bitcoin Main" — continues business as usual. The BIP-110 chain — "Bitcoin Pure" — may have no miners, no blocks, and no value.
We didn't see the quiet escape hatch: even if BIP-110 activates, if no miner runs the new code, the chain dies in infancy. The "hard fork" becomes a symbolic ghost. But that's a worst-case scenario for the purists — their chain with zero hash power is the ultimate irony.
Based on my years of writing scripts to track whale movements and on-chain anomalies, I can tell you that the market is underpricing this risk. Volatility indices for BTC options remain subdued. Social sentiment is polarized but not panicked. Most traders assume miner opposition will magically pause the code. But code doesn't care about votes. BIP-110's activation window is hardcoded. It will trigger unless the client developers release a patch to disable it. And so far, the Bitcoin Knots client — which includes BIP-110 — is still pushing the update.
The party doesn't stop when the music fades. It stops when the DJ throws the turntable.
## Contrarian: The Market's Blind Spot Here's the angle that nobody is connecting: the forced activation is not a bug, it's a feature of minority rule. Bitcoin's governance is often described as "rough consensus and running code." But when rough consensus fails, running code becomes a weapon. A few core developers can impose their vision on millions of users. This breaks the myth of decentralized governance.
Contrarian thought: What if BIP-110 actually passes on the activation day? Not because miners support it, but because the code forces nodes to enforce it. The majority of full nodes might upgrade passively — they don't want to be orphaned. Miners then face a choice: switch to the new chain or lose clients who follow the new rules. This is a game of chicken. And given the low signaling, most miners will resist. But if enough economic nodes (exchanges, custodians) adopt the new client, the pressure shifts.
Institutional investors who bought Bitcoin as a stable, predictable asset are watching this with alarm. Traditional finance hates uncertainty. A hard fork risk could push some allocations toward Ethereum or Solana. This is the hidden cost — not an immediate sell-off, but a slow erosion of Bitcoin's narrative as the safe bet.
Another blind spot: the Ordinals workaround may not be a viable long-term solution. It relies on the BIP-110 nodes not actively detecting the fragmented pattern. But nothing stops a future upgrade to scan for chunked inscriptions and reject them too. The cat-and-mouse game could escalate indefinitely, sapping developer attention and community goodwill.
## Takeaway: What to Watch Next The next 30 days are critical. Here are the signals I'm tracking:
- Miner signaling: the percentage of blocks with BIP-110 flags. If it stays below 5%, the forced activation is symbolic. If it jumps above 30%, the risk of a real split rises.
- Exchange statements: Binance and Coinbase will have to announce which chain they support. Their choice will tip the scale.
- Node client distribution: if a majority of full nodes upgrade to BIP-110-compatible software, economic consensus shifts even if hash power opposes.
- Ordinals workaround audits: if the fragmentation code passes security review, the battle continues. If it's found flawed, Ordinals assets face extinction.
My gut says the forced activation will trigger a minority chain that fizzles within weeks. The majority — miners, users, and exchanges — will coalesce around the non-BIP-110 version. But don't sleep on the downside risk. If the purist chain somehow gains traction via centralized exchange backing, we could see a permanent split. That would destroy Bitcoin's network effect and give ammunition to critics who say crypto governance is a joke.
— Root: The real winner here might be the Ethereum L2s. They're watching and smiling.
We didn't expect Bitcoin to eat itself from the inside. But here we are. The clock is ticking. August is coming. And the party? It doesn't stop. But it might change its address.
