BIP Editor Luke Dashjr Stripped of Privileges: The BIP 110 Minority Fork That Never Was
Pulse on the chain, breath in the market. The Bitcoin Improvement Proposal (BIP) process just lost its most vocal editor. Luke Dashjr – the long-time core developer, Bitcoin Knots maintainer, and strict constructionist of the Bitcoin protocol – has been removed from the BIP editor list. The trigger? A three-year-old proposal, BIP 110, and the stalled minority fork that never materialized.
I’ve watched the BIP process for years, and Dashjr’s removal is a symptom of a deeper schism. This isn’t a simple disagreement over code. It’s a clash between two visions of Bitcoin governance: one that prioritizes editorial authority and another that demands procedural neutrality.
Context: The BIP editor role is a gatekeeper. Editors review proposals, assign numbers, and ensure formatting. They don’t approve or reject technical merits – but their influence is immense. Dashjr held this role for over a decade. He was also the author of BIP 110, a proposal to increase the block size via a soft fork using a new transaction version. The proposal stalled. It never gained consensus. But Dashjr continued to push for a minority fork – a chain split that would activate the change without broad support.
Running where the liquidity flows fastest, but here the flow is political. Other developers raised concerns that Dashjr’s dual role as editor and proponent created a conflict of interest. The BIP process is supposed to be a neutral pipeline. When the editor is also the champion of a controversial fork, the line between curation and advocacy blurs. The concerns were formalized in a GitHub issue and a subsequent call for removal. Last week, the decision was final: Dashjr is no longer a BIP editor.
Core: The immediate impact is procedural. The BIP repository now has fewer editors – down to three. The removal also signals a shift in governance norms. Dashjr was a vocal critic of “soft fork sprawl” – the idea that every new feature should be squeezed into a soft fork. He advocated for a more conservative approach, even when it meant blocking proposals. His removal removes a major obstacle for proposals that require a looser interpretation of the protocol.
But the real story is the minority fork – or the lack thereof. Dashjr’s BIP 110 was never a serious threat. The hash rate backing it was negligible. The fork was a phantom. Yet the controversy around it exposed a fundamental tension: the BIP process is run by volunteers, but the editors act as de facto gatekeepers. When an editor becomes a partisan, the whole system suffers.
I’ve seen this pattern before. In 2017, the SegWit2x drama nearly tore the community apart. The difference this time is that the battle was over governance, not just block size. Dashjr’s removal is a procedural cleanup, not a revolution. But it’s a significant one.
Caught in the flash, framed in fact. The contrarian angle: This isn’t about centralization of power. It’s about the opposite. Dashjr’s removal could actually weaken the BIP process’s legitimacy. The editor role is already under scrutiny. If the community sees editors as replaceable based on political pressure, trust erodes. The BIP process is not a democracy – it’s a meritocracy. But the removal of a long-standing editor by a vocal minority of developers sets a precedent: editors can be fired for controversial stances, even if those stances have no market support.
What’s unreported? Dashjr’s removal was not a consensus decision. It was a majority vote among the remaining editors, but several developers abstained. The process was opaque. The BIP repository is managed by a small group of maintainers, and the removal was decided behind closed doors. This is the opposite of the transparent, decentralized governance Bitcoin preaches.
Seventy-two hours without sleep, zero doubts. The underlying issue is institutional design. The BIP process lacks a formal dispute resolution mechanism. When an editor’s behavior is questioned, there’s no clear path to removal. This ad-hoc approach creates uncertainty. The next editor might be removed for a different reason – perhaps for being too permissive, or for blocking a proposal backed by a powerful miner. The precedent is dangerous.
Takeaway: What to watch next. The remaining BIP editors will now face pressure from both sides. Proponents of BIP 110 will see this as a purge. Opponents will see it as a necessary correction. But the real test will be the next controversial proposal. Will the new editors approve a BIP that Dashjr would have blocked? Or will they be more cautious, afraid of the same fate?
I’m watching the next BIP number assignment. If it’s for a proposal that Dashjr had publicly opposed, the narrative will be clear. If not, the process may survive this crisis. But the BIP editor role is now a political hot potato. And that’s not a healthy state for a protocol that prides itself on code over politics.
Pulse on the chain, breath in the market. The BIP process is still breathing. But the rhythm is different now.