Bitcoin's oldest fight just came back, and this time the battle lines say more about who controls the network than what they're actually fighting about.
The Summary
- BIP-110 proposes capping non-financial data on Bitcoin's blockchain for one year, reigniting censorship and decentralization debates not seen since the Blocksize Wars
- Michael Saylor and Adam Back publicly rejected the proposal days before the early-August activation deadline, with miner support currently at zero
- Critics resurfaced BIP-110 author Luke Dashjr's 2014 Gentoo blacklisting controversy to question his motivations, turning a technical debate into a character trial
- The fight reveals who has real power in Bitcoin governance: not the developers who write code, but the miners and institutional holders who can kill proposals by simply ignoring them
The Signal
BIP-110 was supposed to address "spam", the arbitrary non-financial data that's been clogging Bitcoin blocks since Ordinals and inscriptions took off. Cap it for a year, the thinking went, and buy time to figure out a permanent solution. Clean, technical, straightforward.
Except nothing in Bitcoin is ever straightforward. The proposal immediately split prominent developers, miners, and industry leaders, reopening governance wounds that never fully healed from the 2017 Blocksize Wars. The question isn't really about spam anymore. It's about who decides what Bitcoin is for.
"Turning a spam dispute into a consensus fight could create a bigger risk than the spam itself."
Here's the ironic part: Ordinals transaction activity has been in a broad downturn for two years. The "problem" BIP-110 aims to solve is already fading. But the proposal forced everyone to pick a side anyway, because it touches the third rail of Bitcoin philosophy: censorship resistance.
Key battle lines:
- Proponents see bloat that crowds out financial transactions and raises fees
- Opponents see the first step toward permissioned, curated blockspace
- Institutional players see unnecessary protocol risk for a temporary issue
When Saylor and Back came out against it, they didn't just state technical objections. They made it clear that consensus changes require overwhelming support, and this one has none. Miner support sits at zero with the activation deadline weeks away. In Bitcoin, that's not a debate. That's a verdict.
The opposition went further. David Bailey resurfaced Luke Dashjr's 2014 Gentoo Linux controversy, when Dashjr was accused of blacklisting packages for ideological reasons. The message: this isn't about spam, it's about control. Whether that's fair or character assassination depends on who you ask, but it worked. BIP-110's author is now defending decade-old decisions instead of current code.
The Implication
BIP-110 will almost certainly fail to activate. But watch what happens next. Bitcoin upgrades have always required rough consensus, but the threshold for "rough" keeps rising. SegWit took years. Taproot took longer. BIP-110 couldn't get out of the gate.
This isn't a bug. It's a feature that's starting to look like paralysis. Bitcoin's resistance to change protects it from bad ideas and bad actors. It also makes it nearly impossible to ship anything controversial, even temporarily, even when there's a legitimate problem to solve.
The real question isn't whether arbitrary data belongs on Bitcoin. It's whether Bitcoin can still evolve when evolution requires picking sides. Right now, the answer is no. That might be exactly what holders want. Or it might be what makes Bitcoin the only blockchain that can't adapt to what people are actually doing with it.
Sources
Decrypt | CoinDesk | Unchained Crypto | CoinTelegraph | BeInCrypto