What Is BIP-110 and Why Is It Dividing the Bitcoin Community?

History is repeating itself on the Bitcoin network. If you were around for the blocksize wars, you remember the vitriol, the split in the community, and the fundamental disagreement over what Bitcoin is supposed to be. Today, we are staring down the barrel of BIP-110, a proposal that has reopened those old wounds by trying to solve a new problem: digital junk.

The Core Conflict of BIP-110

BIP-110 is a proposal designed to restrict the amount of non-financial data being embedded into the Bitcoin blockchain. On paper, it sounds like technical housekeeping. In practice, it is a direct assault on the growing ecosystem of Ordinals, BRC-20 tokens, and the various digital artifacts that have flooded the mempool over the last year. These use cases utilize a loophole in the SegWit and Taproot upgrades to park arbitrary data directly on-chain.

The pushback is coming from a faction of developers and purists who believe Bitcoin is a peer-to-peer electronic cash system and nothing more. To them, pictures of rocks and experimental meme tokens are spam. They argue that this data drives up transaction fees for people who just want to move money, making the network less accessible for its original intended purpose. But for builders who have spent the last twelve months creating value around these new layers, BIP-110 looks like censorship.

The Miner Dilemma

Miners are caught in a weird spot here. On one hand, they generally support whatever keeps the network secure and efficient. On the other hand, non-financial data has been a windfall for their bottom line. When Ordinals are booming, transaction fees skyrocket. Miners get paid. In a post-halving world where block rewards are shrinking, telling miners to stop accepting high-fee transactions just because the data inside is a JPEG is a hard sell.

If BIP-110 gains traction, it forces miners to choose between ideological purity and economic reality. Most of the miners I know are pragmatists. They operate on thin margins and high electricity bills. If someone is willing to pay 100 sats/vB to store an inscription, a miner is going to take that money regardless of what a developer in a GitHub thread thinks about the "sanctity" of the ledger.

What This Means for Builders

If you are building in the Bitcoin ecosystem right now, this uncertainty is your biggest risk. BIP-110 represents a governance crisis. It suggests that the rules of the game can be changed retroactively to brick specific business models. We saw this with early internet protocols, and we are seeing it now with the base layer of crypto.

For founders, the lesson is clear: don't get too comfortable with loopholes. The builders who flourished during the Ordinals craze did so by exploiting a technicality. While that is smart in the short term, it creates a fragile foundation. If the protocol developers decide that your entire product category is a bug rather than a feature, your roadmap can be deleted with a single merge. You have to decide if you are building a product that relies on Bitcoin's durability or if you are just squatting on its block space.

The Censorship Trap

The most dangerous part of the BIP-110 debate is the precedent it sets for censorship. The moment we start defining what is "legitimate" use of block space, we move away from the neutral, permissionless nature that made Bitcoin valuable in the first place. If we can block JPEGs today, what can we block tomorrow? Stablecoins? Privacy-preserving transactions? Complex smart contracts?

Once you introduce a filter, you have a gatekeeper. Bitcoin was designed specifically to avoid gatekeepers. Even if you hate the current wave of inscriptions, you have to realize that the tool used to remove them is the same tool that could eventually be used to remove you. This is why the debate is so toxic; it is not just about data sizes, it is about the soul of the network.

Technical Reality vs. Social Consensus

Technically, BIP-110 would make it harder for non-standard data to be relayed across the network. It wouldn't necessarily stop a miner from including an inscription if they received it directly, but it would cripple the infrastructure that makes these transactions easy for the average user. This creates a fragmented network where some nodes see one version of the mempool and others see another.

This kind of fragmentation is exactly what leads to hard forks. We have seen this movie before, and it usually ends with a lot of lost value and a decade of infighting. The builders who win in this environment are the ones who stay flexible. If you are building on Bitcoin, you need to be prepared for the possibility that the base layer becomes aggressively hostile to anything that isn't a simple transfer of value.

The Real Takeaway

BIP-110 is probably not going to pass in its current form because the economic incentives are too skewed in favor of high-fee data. However, the fact that it exists and has high-level support should be a wake-up call for anyone working in the Bitcoin space. The "Blocksize Wars 2.0" are not just coming; they are already here.

Stop assuming the protocol is static. Bitcoin is a living organism governed by a messy, human social consensus. If you want to build something that lasts, you can't just rely on the technical specs of 2024. You have to understand the political landscape of the developers and the economic motivations of the miners. If your project sits at the intersection of those two forces and pokes them both in the eye, don't be surprised when they poke back.

The value of Bitcoin isn't just in its code; it's in the trust that the rules won't change on a whim. BIP-110 threatens that trust by attempting to define what 'good' data looks like.

As an industry, we need to move past the idea that we can scrub the blockchain of things we don't like. The ledger is a mirror of the market. If the market wants to put cats on Bitcoin, it will. Trying to stop it through protocol-level restrictions is a short-term fix that creates long-term fragility. For builders, the path forward is to focus on efficiency and actual utility. If your use of the chain is so inefficient that a single BIP can kill your company, you aren't building a product; you're just taking advantage of a temporary oversight.

Read the original at Decrypt →