It began not with a bang, but with a dashboard. On a Tuesday afternoon in late July, I refreshed the BIP-110 signaling tracker out of habit—a habit I've kept since the SegWit debates of 2017. The number hadn't moved in weeks: 1.2% miner support. A statistical dead proposal walking. But then Michael Saylor posted. Three paragraphs, calm tone, no caps lock. He didn't call for war. He simply reminded the community what Bitcoin is for.
"Code is law, but empathy is truth." That's what I whispered to myself as I read his thread. Because what Saylor was really saying—between the lines about 'protocol simplicity' and 'no permissionless compromise'—was that Bitcoin’s greatest asset is not its hash rate. It's its refusal to pick winners.
Let’s rewind. BIP-110, formally the "Reduced Data Temporary Soft Fork," is a proposal to temporarily limit the data payload per Bitcoin block. Its stated goal: suppress what its authors call 'non-monetary usage'—specifically Ordinals inscriptions, BRC-20 tokens, and the Runes protocol. In practice, it would have capped the data per transaction to a tiny fraction of what is currently allowed, effectively banning most inscriptions without explicitly naming them.
The proposal had been floating in the BIP repository for over a year, largely ignored. But as Ordinals fees spiked during the April halving, a small group of developers revived it, arguing that spam was driving up costs for ordinary users. They proposed lowering the miner activation threshold from the traditional 95% to just 55%—a radical departure from Bitcoin's conservative governance norms.
"Trust no one, verify everyone, feel everyone." That's another signature I've written more times than I can count. And in this debate, verification was clear: the proposal had almost no miner support. But the feeling—the underlying anxiety about Bitcoin's direction—was real.
Core: The anatomy of a failed coup
To understand why BIP-110 died so decisively, we have to look past the technical details and into Bitcoin's soul. I've spent years auditing protocol discussions, from the block size war to Taproot. What I've learned is that Bitcoin doesn't change unless a supermajority wants it to change. And here, the community spoke with unusual clarity.
First, the technical flaws. BIP-110 doesn't improve security or scalability. It imposes a restrictive filter on transaction content. In my experience auditing governance proposals, this is the hallmark of a 'censorship tool disguised as an optimization.' The proposal's authors argued that reducing data load would lower fees for small transactions. But what it really does is allow miners to decide which transactions are 'valid' based on content—not just signature validity.
"Behind every hash, a heartbeat." Every Bitcoin transaction is someone's economic choice. When you empower miners to reject inscriptions because they contain too much data, you create a slippery slope. Today it's JPEGs. Tomorrow it might be transactions from a sanctioned wallet. The day after, a privacy tool. Saylor understood this. His warning—"this sets a precedent that can be used against privacy tools or enterprise applications"—was not hyperbolic. It was an accurate read of how consensus rules evolve.
Second, the activation threshold. Lowering from 95% to 55% is not a minor tweak. It's a fundamental change to Bitcoin's social contract. The 95% threshold exists precisely to prevent a minority from forcing a rule change on the majority. By proposing 55%, BIP-110's authors were essentially saying: "We only need a simple majority to rewrite the rules." That's not a soft fork. That's a hostile takeover.
Adam Back, Bitcoin's most respected cryptographer, called it "reckless." Jameson Lopp, a veteran engineer, agreed. And Saylor, as the largest public holder of Bitcoin through Strategy (formerly MicroStrategy), added his institutional weight. His company holds over 840,000 BTC. When he speaks, capital moves. But more importantly, when he speaks against a proposal, the community listens.
The result? Miner signaling never budged from 1%. The proposal is effectively dead. But why do I say 'effectively' rather than 'definitively'? Because the debate isn't over the proposal itself—it's over Bitcoin's future.
Contrarian: The hidden cost of saying no
Let me play the devil's advocate for a moment. The Ordinals ecosystem has generated real congestion. In the week after the April halving, average transaction fees hit $120. Users sending small payments were squeezed out. The argument for BIP-110—that it would restore low-cost access—is not invalid. It's just myopic.
The contrarian perspective is that Bitcoin's 'immutability' is also a form of paralysis. By rejecting any mechanism to manage data load, the community has accepted that fees will remain volatile. Poor users in developing countries who rely on Bitcoin for remittances will continue to pay the price of sporadic congestion. Was there a middle ground? A less restrictive approach, perhaps limiting data per block rather than per transaction?
"Surviving the winter to plant the spring." That's a phrase I often use to remind myself that bear markets are for building. But here, the winter is the governance gridlock. The spring—the Ordinals ecosystem—is being planted on Layer 1, and many argue it should have been on Layer 2 from the start.
Indeed, the real winner of this debate is Bitcoin's L2 ecosystem. The message from Saylor, Back, and Lopp is clear: if you want to build applications on Bitcoin, build them off-chain. Lightning Network, RGB, Stacks, Rootstock—all of these projects just received a massive validation signal. The main chain will remain immutable, secure, and pure. Any complexity moves to the second layer.
But here's the uncomfortable truth I've observed in my own research: L2s are still experimental. Lightning has scaling challenges. RGB is complex to use. Stacks is not fully decentralized. The gap between 'vision' and 'usable product' is still wide. If Ordinals continue to grow—and Runes is gaining traction fast—the congestion problem won't disappear. It will intensify. And Bitcoin's governance will face this same test again, possibly with a more sophisticated proposal.
Takeaway: What we learned about Bitcoin's soul
This episode is not about a failed soft fork. It's about a successful immune response. Bitcoin's decentralized governance, often criticized for being slow and messy, proved its strength. A small group of powerful voices—Saylor, Back, Lopp—aligned with the broader community to kill a proposal that threatened the network's core principles.
"In the chaos of the reset, we find clarity." That clarity is this: Bitcoin will not sacrifice permissionlessness for efficiency. It will not allow a 55% threshold to rewrite its social contract. And it will not let fear of spam undermine the philosophy that made it valuable in the first place.
But we must also ask: what happens when the next proposal comes, wrapped in better marketing, perhaps framed as 'environmental sustainability' or 'compliance readiness'? Will the immune response still work? I don't know. But I do know that the ledger remembers, and the heart forgives. Bitcoin's heart—its community—just showed it can still say no.
The next chapter belongs to the L2 builders. They have been handed a mandate: build without touching the core. If they succeed, Bitcoin will scale without losing its soul. If they fail, the congestion debate will return, more urgent than ever.
"Philosophy before protocol, people before profit." That's the lesson of BIP-110. And as I close my dashboard and step away from the screen, I feel a strange sense of peace. The fork that almost wasn't taught us that Bitcoin's greatest upgrade is the one that never happens.