The BIP-110 drama showed us something way bigger than just Ordinals and spam
Alright, let's talk about the recent BIP-110 situation. Everyone is treating this like another endless thread about whether JPEGs belong on Bitcoin or whether Luke Dashjr has gone rogue. But honestly? The technical side is almost secondary at this point.
What's actually wild is what this whole event exposed about how Bitcoin decision-making works right now.
Looking at both sides, everyone seems to have a point:
Why proponents pushed for it:
- Node operators are the ones storing the chain forever, but miners are getting paid all the short-term fees for high-data transactions.
- Many felt Core developers changed default relay policies over time without actual consensus, and BIP-110 was an attempt to force the node client back to stricter relay defaults.
- The argument that letting Bitcoin turn into a generic data layer compromises its primary function as censorship-resistant sound money.
Why opponents shut it down:
- Deciding what counts as "spam" vs. "legitimate financial data" is a slippery slope toward subjective censorship.
- Trying to push a soft fork without broad miner support was a massive game-theory risk that could have fragmented the network.
- Trying to filter data usually backfires, people just hide data in standard script fields, which makes UTXO bloat even worse.
The bigger issue isn't even whether BIP-110 was good or bad code. It's the governance dynamic.
If Core maintainers set the default client rules, miners choose what blocks to build based on immediate profit, and node operators are left trying to coordinate soft-fork signalling when they don't like the direction, who is actually calling the shots in Bitcoin today?
Did we just watch decentralisation work as intended because a non-consensus proposal died out, or are node operators slowly losing their seat at the table to miners and maintainers?
Curious how you guys see it.