Luke Dashjr Removed as Bitcoin BIP Editor: What the BIP-110 Controversy Means for Bitcoin
Luke Dashjr’s removal as a Bitcoin Improvement Proposal editor has turned the failed BIP-110 soft fork into something larger: a test of Bitcoin’s informal governance in a decentralized network.
Bitcoin has spent much of its history avoiding the kind of institutional politics that define conventional technology projects. There is no chief executive who can settle a dispute, no central committee that can impose a software upgrade and no board capable of deciding which developer gets the final word. That makes the latest dispute involving longtime Bitcoin developer Luke Dashjr particularly revealing.
On August 10, 2026, Dashjr was removed from the Bitcoin Improvement Proposal, or BIP, editorial team following a contentious dispute surrounding BIP-110, a proposed temporary soft fork aimed at restricting certain forms of non-financial data on Bitcoin. The move came shortly after BIP-110 effectively failed to establish a viable minority chain, producing only two blocks before stalling. The technical experiment was short-lived. The governance argument is not.
BIP-110 Started With a Familiar Bitcoin Argument
At its core, BIP-110 was an attempt to address a long-running disagreement over how Bitcoin’s limited block space should be used.
The proposal sought to temporarily restrict the inclusion of certain types of non-financial data in Bitcoin transactions. That includes use cases associated with inscriptions, Ordinals and other applications that treat Bitcoin’s blockchain as something more than a settlement network for monetary transfers.
Supporters see this as a question of efficiency and sustainability. Bitcoin nodes must download, validate and store the blockchain. Every additional byte creates some burden for the network, while block space itself remains scarce. From this perspective, using consensus rules to discourage what supporters consider unnecessary data could help preserve Bitcoin’s monetary function and reduce the resources required to operate the network.
Critics approach the issue from almost the opposite direction.
Bitcoin’s permissionless architecture does not generally ask users to justify why they want to occupy block space. If a transaction follows the consensus rules and the sender pays the required fee, opponents argue that deciding which legitimate uses are “financial” and which are “junk” risks introducing an arbitrary distinction into the protocol. That is why BIP-110 became so contentious.The argument was never just about data. It was about what Bitcoin is supposed to permit.
Why BIP-110 Became a Governance Problem
The controversy intensified because Dashjr was not merely an outside commentator advocating for the proposal. He was one of BIP-110’s principal proponents while also serving as a BIP editor.
BIP editors do not control Bitcoin’s consensus rules. Their role is primarily administrative and editorial: managing the proposal process, assigning BIP numbers and helping maintain the documentation surrounding proposed changes. A BIP number itself does not make a proposal part of Bitcoin’s rules.
That distinction is important. Bitcoin’s development process depends heavily on social norms and contributor consensus rather than a conventional chain of command. When someone involved in administering that process is simultaneously a prominent advocate for a controversial protocol change, questions about neutrality become almost inevitable.
Other BIP editor Mark “Murch” Erhardt ultimately proposed removing Dashjr from the editorial team. The arguments included concerns about the handling of BIP-110, procedural issues and an alleged conflict between Dashjr’s editorial responsibilities and his role as a leading advocate for the proposal.
Dashjr disputed the accusations and maintained that he had acted within the established process. The disagreement therefore became a question of institutional credibility: can an editor remain a trusted administrator of a proposal system while actively campaigning for one of its most divisive proposals?
The Numbers Were Brutal for BIP-110
Whatever one thinks about the proposal itself, BIP-110 struggled to attract the network support necessary to become consequential. Its mandatory signaling period began around block 961,632 on August 8. Before that point, miner signaling had been extremely limited. Reports put support at only about 2.53% of blocks during the relevant signaling period, dramatically below the 55% threshold associated with activation.
That lack of support mattered because Bitcoin’s consensus changes ultimately require more than a compelling argument from developers. They require participants across the ecosystem to accept the proposed rules.
Miners are one part of that equation, but they are not the only one. Nodes, developers, businesses, exchanges, wallets and users all have incentives and choices that can determine which chain becomes economically meaningful.
BIP-110 exposed the difference between having software that enforces a rule and having an ecosystem willing to recognize that rule as Bitcoin.
The Minority Chain Lasted Just Two Blocks
The most dramatic test came when nodes enforcing BIP-110 began rejecting blocks that did not comply with its rules. That created a minority chain. In theory, a chain split does not necessarily mean one side immediately disappears. Both networks can continue producing blocks if they have sufficient mining support and economic participation. In practice, however, the BIP-110 chain had almost none of the hashpower required to sustain a serious alternative network.
It produced two blocks and then stalled. The main Bitcoin chain continued moving forward while the minority chain remained stuck, demonstrating a fundamental reality of proof-of-work networks: creating an alternative rule set is relatively easy; creating an economically viable alternative Bitcoin is considerably harder.
The episode also provided a real-world demonstration of how decentralized consensus resolves contentious changes without a central authority issuing a ruling. The market, miners and network participants effectively chose which chain mattered.
Why Dashjr’s Removal Matters More Than the Failed Fork
If BIP-110 had simply failed, the episode might have become another footnote in Bitcoin’s long history of unsuccessful protocol proposals. Dashjr’s removal changed that. The decision raised questions about the governance of the BIP system itself. Bitcoin deliberately avoids creating a centralized institution with absolute authority over protocol development. That philosophy protects the network from a single point of control, but it also leaves certain administrative questions surprisingly informal.
One of those questions is how a BIP editor should be removed.
The absence of a detailed, universally accepted removal mechanism became conspicuous during this dispute. The decision was ultimately carried out through the collaborative development infrastructure surrounding the BIP repository rather than through a conventional corporate-style governance procedure.
That may sound mundane. Bitcoin’s decentralization depends partly on the fact that authority is fragmented. But fragmented authority does not eliminate governance. It simply moves governance into repositories, mailing lists, developer discussions, software releases, miners and the economic participants who decide which rules they will recognize. BIP-110 made that invisible machinery unusually visible.
Bitcoin Has No Supreme Court for Protocol Disputes
One of the fascinating characteristics of Bitcoin is that there is no final institution capable of declaring a consensus dispute permanently settled.
Developers can write code. Miners can choose what they mine. Node operators can choose which software they run. Businesses can decide which chain they support. Users can decide which assets they hold and which transactions they recognize.
None of those groups has unilateral authority over everyone else. This is precisely why Bitcoin’s governance can look chaotic from the outside. A traditional company can resolve a technical disagreement with a management decision. Bitcoin cannot do that without undermining the very decentralization that gives the network much of its value.
The result is a form of emergent governance. Consensus is not simply written into a document. It is demonstrated through participation. BIP-110 did not acquire sufficient participation, and its minority chain quickly demonstrated the consequences.
The Bigger Dispute Is About Bitcoin’s Identity
The technical question surrounding inscriptions and arbitrary data is unlikely to disappear. Bitcoin’s block space will remain scarce. Users will continue finding new ways to use it. Developers will continue debating whether those uses strengthen the network or impose unnecessary costs on node operators.
The disagreement reflects two competing visions.
One sees Bitcoin primarily as a monetary settlement network that should aggressively preserve its efficiency, simplicity and ability to be operated by relatively ordinary hardware. The other places greater emphasis on permissionlessness: if the protocol permits a transaction and the user pays the market price for block space, the network should not impose additional ideological restrictions on how that space is used.
Neither position is trivial. The first highlights the economic and infrastructural costs of running a blockchain. The second highlights the danger of allowing developers or maintainers to decide which legitimate uses deserve access to a supposedly neutral protocol. That tension will almost certainly return in future Bitcoin upgrades.
What This Means for Bitcoin Developers
The immediate consequences for Dashjr are straightforward: he is no longer listed as a BIP editor, and the dispute has added another chapter to an already contentious period surrounding BIP-110. The longer-term implications for Bitcoin development are more interesting.
The episode may encourage contributors to clarify expectations around BIP editors, conflicts of interest and procedural authority. If a proposal can generate a dispute over who is entitled to administer the proposal process, then the process itself becomes part of the problem.
Yet Bitcoin should be careful about overcorrecting. Creating an elaborate bureaucracy to govern BIPs could solve one problem while creating another. The attraction of the existing system lies partly in its lightweight structure. Turning Bitcoin development into a heavily institutionalized organization would introduce precisely the kind of centralized authority the ecosystem has historically tried to avoid. The challenge is finding enough procedural clarity to preserve trust without constructing a new hierarchy.
What Investors Should Take From the BIP-110 Dispute
For Bitcoin investors, this is not primarily a price story. The more relevant issue is protocol governance. A contentious consensus proposal can create uncertainty around software compatibility, mining behavior, infrastructure support and the willingness of major ecosystem participants to coordinate around an upgrade. Even an unsuccessful fork can expose disagreements that resurface during future attempts to change Bitcoin’s rules.
At the same time, BIP-110’s failure also demonstrates something reassuring about Bitcoin’s architecture. A controversial proposal did not automatically become Bitcoin simply because developers wrote the code or assigned it a BIP number. The proposal required broader participation, and that participation did not materialize.
The network continued. That distinction is worth remembering whenever headlines make it sound as though a developer, miner or BIP editor can simply “change Bitcoin.” They cannot.
BIP-110 Failed, But the Governance Debate Won’t
Luke Dashjr’s removal marks the end of one episode in the BIP-110 saga, but probably not the end of the underlying argument.
The proposed restrictions on non-financial data remain part of a much older Bitcoin debate about block space, inscriptions, node costs and the purpose of the protocol. Meanwhile, the controversy surrounding Dashjr has exposed another issue that Bitcoin rarely discusses so openly: how should a decentralized ecosystem govern the people who help coordinate its development?
BIP-110 failed to attract anything close to the support required to establish itself as a viable alternative to the dominant Bitcoin chain. Its minority network produced only two blocks before stalling, while the broader ecosystem continued operating on the main chain.
But the failed fork still accomplished something important. It revealed where Bitcoin’s informal governance mechanisms become strained. For a network that deliberately distributes authority among developers, miners, node operators, businesses and users, disagreement is not a bug. It is part of the design. The real test is whether the ecosystem can absorb those disagreements without allowing any individual faction to turn its preferred interpretation of Bitcoin into a unilateral rule.
BIP-110 did not win that battle. But it has given Bitcoin developers, miners and users a much bigger question to debate: when nobody is officially in charge, how does everyone agree on who gets to speak for the protocol?
