NOSTR MAGAZINE

Bitcoin’s BIP-110 Disaster: A Developer Dethroned

The Bitcoin network is a multi-trillion-dollar behemoth, often praised for its immutable code and decentralized nature. But beneath the surface of this digital gold lies a complex, and often brutal, political landscape. This week, that landscape erupted in a controversy that has sent shockwaves through the community, revealing deep fissures and raising uncomfortable questions about power, process, and the very purpose of Bitcoin.


The Catalyst: A Fork That Never Was

The drama began on August 8, 2026, at block height 961,632. This was the moment a soft fork proposal known as BIP-110 was supposed to activate. Spearheaded by Luke Dashjr, a legendary figure in Bitcoin’s history and a long-time BIP editor, the proposal aimed to temporarily restrict the storage of non-financial data—like images and text from Ordinals inscriptions and BRC-20 tokens—on the blockchain.

Supporters of the proposal argued that these “inscriptions” were clogging the network, driving up transaction fees, and distracting from Bitcoin’s core mission as a peer-to-peer electronic cash system. They saw it as a necessary cleanup to protect the network’s integrity.

However, the community, and more importantly, the miners, overwhelmingly disagreed. The proposal required a 55% signal threshold from miners to activate—a threshold that was already unusually low compared to the historical 90-95% standard. But even this low bar proved insurmountable. Support never climbed above a meager 2.53%. The minority chain that attempted to enforce the new rules mined only two blocks before grinding to a complete halt. The main chain continued operating as if nothing had happened. F2Pool co-founder Wang Chun even publicly mocked the effort.


The Fallout: A Developer Dethroned

The failure of BIP-110 was just the opening act. The real controversy began almost immediately after, as the community turned its attention to Dashjr’s role in the process.

On August 9, fellow BIP editor and Bitcoin Core developer Mark “Murch” Erhardt formally recommended Dashjr’s removal. The motion cited a litany of procedural grievances: that Dashjr had abused his editorial powers to assign a BIP number to his own proposal before it was properly discussed, that he merged updates into the repository without due process, and critically, that he had contributed less than 1% of the editorial comments in the BIP repository since April 2024. His merge of the BIP-110 PR was his first since May 2024. The vote to remove him was swift, and on August 10, Luke Dashjr was formally stripped of his BIP editing privileges. It was, as many noted, one of the most dramatic governance actions in Bitcoin Core’s history.


The Blame Game and Deeper Conspiracies

Dashjr, who is also the co-founder and CTO of the Ocean mining pool, did not go quietly. He took to X (formerly Twitter) to denounce his removal as “an abuse of power,” and even referred to the majority chain as “Bpedo”. He announced he was taking a sabbatical from his role at Ocean to focus on Bitcoin and open-source projects.

The controversy quickly spiraled into a broader blame game, exposing long-simmering tensions and fueling conspiracy theories. Prominent Bitcoin figure Samson Mow, CEO of JAN3, publicly criticized Bitcoin Core developers, arguing that they brought this dispute upon themselves. Mow claimed the entire BIP-110 movement was a direct consequence of Core developers relaxing the OP_RETURN limit in version 30.0, which he believes should have been left untouched. “The same situation would happen again unless Bitcoin Core developers acknowledged responsibility for directly triggering the BIP-110 movement,” Mow stated.

This narrative feeds into a recurring conspiracy within the community: that certain developers are too cozy with the “spam” (Ordinals, BRC-20) ecosystem, or that they are actively working to change Bitcoin’s fundamental nature. The tension is a classic battle between “maximalists” who want Bitcoin to remain pure money and “innovators” who see new use cases as essential for its long-term viability.


A Governance Crisis or a Sign of Health?

So, what does this all mean? In my experience covering this space, these kinds of blow-ups are often interpreted as signs of impending doom. But I think this situation is more nuanced.

On one hand, this is a significant governance crisis. The fact that a long-standing editor was able to bypass process and push a proposal with virtually no support highlights a vulnerability in the system. It raises the question: what safeguards are truly in place? If 2024’s multi-editor system couldn’t prevent this unilateral action, what additional checks are needed? The BIP process itself has no formal mechanism for removing an editor, leaving the community to scramble and reach an ad-hoc consensus. This is messy, unpredictable, and frankly, a bit scary for those who value stability.

On the other hand, this is a powerful testament to Bitcoin’s resilience. The system worked. A highly influential developer with the power to assign numbers and merge code tried to force through a change, and the network—miners, nodes, and the wider community—simply rejected it. The market didn’t even flinch, with Bitcoin’s price remaining largely unaffected by the incident. The decentralized nature of Bitcoin proved stronger than one man’s ambition, however well-intentioned. The drama shows that while individuals can propose changes, they cannot command them.


Summary

The BIP-110 fiasco and the subsequent removal of Luke Dashjr is the most significant Bitcoin development story of the year. It’s a story that has it all: a failed technical upgrade, allegations of abuse of power, a high-profile ouster, and a philosophical war over the network’s future.

The event serves as a stark reminder that Bitcoin, for all its code, is ultimately a social and political system. Its governance is messy, contentious, and often dramatic. But that messiness is also its greatest strength. The ability of the network to self-correct and decisively reject a proposal with a 2.53% consensus, even when pushed by a powerful insider, is a feature, not a bug. The fight for Bitcoin’s soul is real, and it’s playing out in public. Whether you find that terrifying or exhilarating likely depends on which side of the fork you stand on.

Comments