The Phantom Fork
Bitcoin finds itself at a familiar crossroads, but this time, the silence is what matters most. We are staring down the deadline for BIP 110, a proposal designed to surgically remove what some call 'spam' from the protocol. Yet, as the clock ticks, miner support sits at a flat zero percent. In the world of consensus, that is not just a lack of interest; it is a loud, clear rejection of how we handle protocol changes.
The core of the argument is simple on the surface. BIP 110 aims to cap arbitrary data on the Bitcoin blockchain for a one-year period. It is a reactionary move against the explosion of Ordinals, Inscriptions, and the general trend of turning a financial ledger into a permanent hard drive for JPEGs and BRC-20 tokens. To the purists, this is a cleanup operation. To the builders, it looks like a centralized attempt to dictate what is and isn't a valid use of digital space.
The Risks of Enforced Purity
As a founder, I have seen these cycles before. Whenever a decentralized network finds a sudden, unintended product-market fit—like Bitcoin did with data storage—the first instinct of the old guard is to build a wall. But the pushback against BIP 110 isn't just coming from the 'degens.' It is coming from the ideological heavyweights who usually lead the charge for Bitcoin's integrity.
People like Adam Back and Michael Saylor have voiced a concern that I share: the cure might be significantly more dangerous than the disease. By turning what is essentially a dispute over block space usage into a consensus-level fight, we are opening a door that is hard to close. If we start filtering data today because we think it is 'spam,' what prevents us from filtering transactions tomorrow because we think they are politically inconvenient?
The Founder Perspective: Don't Break the Social Contract
For those of us building in this space, the value of Bitcoin is its predictability. You pay the fee, you get the space. It is a blind, permissionless auction. BIP 110 threatens to break that social contract by introducing subjective judgment into the protocol layer. When you give a protocol the power to decide which data is 'worthy,' you have successfully rebuilt the legacy banking system on a slower database.
The moment we allow consensus to be used as a weapon against specific use cases, Bitcoin loses its primary value proposition: neutrality.
Miners understand this better than anyone. Their business model is built on one thing: fees. They are being told to support a fork that would directly reduce their revenue by capping the very data that is driving up transaction fees. Expecting a miner to vote for BIP 110 is like asking a landlord to vote for a law that bans half of their tenants from paying rent. It simply doesn't make economic sense.
Why Zero Percent Support Matters
The fact that miner support is currently at zero is a fascinating case study in decentralized governance. It shows that the 'Bitcoin is broken' narrative hasn't taken hold among the people actually running the hardware. From a builder's view, this is actually a sign of health. It suggests that the market for block space is working exactly as intended. If people are willing to pay more to put a monkey picture on the chain than someone is willing to pay to send $5, the miners will take the money. That is the consensus mechanism at work.
Trying to hard-code a solution into the protocol to fix a market 'problem' is a slippery slope. We’ve seen this in the AI space recently too—attempts to build 'safety' into the base models often just result in broken, biased systems that no longer serve the end user. In crypto, protocol-level meddling usually leads to chain splits, and a chain split over something as subjective as 'spam' would be a disaster for Bitcoin’s reputation as digital gold.
What This Means for the Future
So, where does this leave the builders? If BIP 110 fails, which looks inevitable, it sends a message that the Bitcoin base layer will remain a permissionless data dump. For those building Layer 2 solutions, this is actually a massive opportunity. The high fees on Layer 1 caused by data competition are the best possible incentive for people to move to the Lightning Network or other scaling solutions.
- Market forces win: You can't code away demand. If people want to put data on Bitcoin, they will find a way.
- Node operators are the final boss: Even if developers want a change, the people running the infrastructure have the final say.
- Censorship resistance is binary: You are either permissionless, or you aren't. There is no middle ground for 'just a little bit of filtering.'
The Real Takeaway
The death of BIP 110 isn't a victory for 'spam,' it is a victory for the protocol's neutrality. Bitcoin was designed to be a system where the rules are set in stone and the players compete based on those rules. When we start trying to change the rules because we don't like how the game is being played, we risk losing the game entirely. For founders, the lesson is clear: build for the reality of the market, not the ideals of the whitepaper. The market wants data storage, and until a better, cheaper alternative exists, they will continue to buy up Bitcoin's block space.
Stop trying to fix the protocol to suit your personal aesthetic of what a blockchain should look like. The market is honest, even when it’s messy. BIP 110 is a reminder that in decentralized systems, the most powerful move is often doing nothing at all.
Read the original at CoinDesk →