Luke Dashjr is out. The longtime Bitcoin developer no longer holds editor or administrator privileges in the Bitcoin Improvement Proposal repository, following a messy dispute over his handling of BIP 110 — a proposal that briefly cracked the Bitcoin network before collapsing for lack of miner support.
Developer Mark Erhardt kicked things off by posting a recommendation on the Bitcoin Developer mailing list, calling for Dashjr’s removal. He then opened a formal pull request on Sunday to make it official. The core accusation: Dashjr was “heavily involved” in BIP 110’s creation and rollout, and used his editor position to push it along faster than the process normally allows — assigning it a BIP number prematurely and merging updates at a pace critics called suspicious. For a role that’s supposed to be neutral, that’s a pretty serious charge.
What BIP 110 Actually Did
BIP 110 targeted something specific: the amount of arbitrary data that can be embedded in Bitcoin transactions. Supporters argued it was a necessary cleanup. But the proposal didn’t get far before it triggered a minority chain split — nodes enforcing BIP 110 started rejecting blocks from miners who hadn’t signaled support. Without enough hashpower behind it, the fork stalled fast. It basically went nowhere, but not before creating real friction on the network.
That’s the backdrop Erhardt was working from. His argument wasn’t just about the fork failing — it was about how Dashjr handled his editor duties while being one of the people driving the proposal forward. In most governance structures, that kind of dual role raises flags. Bitcoin’s development community is no different.
Developer Jon Atack confirmed the removal by checking the BIP repository directly — Dashjr’s editor and administrator privileges were gone. Atack then completed the pull request, making the change formal. No drama in the execution, even if the lead-up was anything but clean.
Dashjr didn’t take it quietly. He called the move “an abuse of power by Core” and said the people who made the decision had no authority to remove him. That’s a significant claim, and it probably won’t be the last word from him on the subject. Whether the community agrees is another question — so far, no other Bitcoin Core developers have made any public statement about the removal.
Governance Gaps the Incident Exposed
The whole episode is kind of a stress test for how Bitcoin’s development process actually works. BIP editors aren’t elected officials. There’s no formal removal procedure written into a charter somewhere. The process runs on rough consensus, mailing list debates, and pull requests — which means disputes like this one get messy fast, and the line between legitimate process and “abuse of power” is genuinely murky depending on who you ask.
Dashjr has been around Bitcoin development for a long time. He’s not a peripheral figure. So his removal carries weight, and the fact that it happened through a pull request rather than any kind of formal vote says a lot about how informal the governance structure still is, even after years of growth and controversy.
The BIP 110 fork itself is worth sitting with for a second. Minority forks in Bitcoin aren’t new, but they’re always revealing. When nodes start rejecting miner blocks and the hashpower doesn’t follow, the fork dies. That’s how Bitcoin’s consensus mechanism is supposed to work — majority hashpower wins, and proposals without broad miner support don’t stick. BIP 110 ran straight into that wall. The speed with which it collapsed probably added fuel to the argument that it was pushed through without adequate community buy-in.
And that’s where the procedural criticism of Dashjr gets sharper. If you’re an editor and you’re also championing a proposal, the pressure to stay hands-off is enormous. Merging updates quickly and assigning a BIP number before the process normally allows — those aren’t small things. They’re the kinds of moves that, in a system built on trust and transparency, look bad even if the intent was fine.
What Happens to the BIP Process Now
The remaining editors will keep managing proposals. It’s not like the whole system grinds to a halt. But the community will probably watch the next few BIP decisions pretty carefully, looking for signs that the process is tightening up or loosening further. There’s no word yet on whether any structural changes to the editor selection process are being discussed — unclear if that conversation is even happening formally.
What’s clear is that Dashjr’s removal has put Bitcoin governance back in the spotlight. The decentralized nature of Bitcoin is supposed to prevent any one person from having too much sway. But editors, by definition, have real influence over which proposals move forward and how fast. Checks on that influence are pretty thin.
Atack confirmed the repository changes. Dashjr’s access is gone. And the mailing list has gone quiet — at least for now.
Hub: Bitcoin price, news, and analysis
Frequently Asked Questions
Why was Luke Dashjr removed as a Bitcoin Improvement Proposal editor?
Developer Mark Erhardt accused Dashjr of bias in handling BIP 110, including assigning it a BIP number prematurely and merging updates rapidly while being heavily involved in the proposal’s creation and implementation.
What was BIP 110 and why did it cause a chain split?
BIP 110 proposed limiting arbitrary data embedded in Bitcoin transactions. Nodes enforcing it began rejecting blocks from miners who didn’t signal support, triggering a minority fork that quickly collapsed due to insufficient hashpower.
