The Bitcoin developer community removed Luke Dashjr from his role as a Bitcoin Improvement Proposal editor, days after the soft fork he championed mined just two blocks in eight hours and stopped. The decision came on August 9, and Dashjr has already called it illegitimate while announcing a pause from mining pool Ocean. For an average crypto user this looks like an internal technical dispute, but it shows how fragile trust can be inside a team that formally has no single leader.
What happened to Luke Dashjr?
Fellow editor Mark Erhardt, known as Murch, filed a motion to remove Dashjr on the Bitcoin Development Mailing List on August 9. The same day he opened a pull request proposing to strike Dashjr's name from BIP 3, the document listing all editors. Erhardt cited four grounds. Dashjr had used editorial authority inconsistently, favoring his own proposal. He publicly assigned BIP-110 a number on X before it reached the mailing list, then merged the pull request within minutes of opening it. According to Erhardt, Dashjr left fewer than 1% of BIP Editor comments in the repository since new editors joined in April 2024, and that same disputed merge was his first since May 2024. A soft fork he had championed turned into a hard fork, which Erhardt called a complete departure from Bitcoin's development community. Trust between editors, he wrote, had broken down. Support for the removal showed up as thumbs-up reactions and comments on the pull request, there is no formal vote in the usual sense.
What does a BIP editor actually do?
BIP stands for Bitcoin Improvement Proposal, the formal document developers use to suggest protocol changes. An editor doesn't decide which proposal the network adopts, that's up to miners and node operators, but controls formatting and numbering in the official GitHub repository. The role looks technical, yet it carries real influence. Whoever manages the proposal queue partly controls which ideas reach public review at all. That is why appointing or removing editors rarely passes without disagreement in the developer community. Dashjr was one of the original BIP editors and ran the repository for years, so his removal is a rare precedent for a project with no formal hierarchy. Bitcoin has no official governing body. Decisions come from rough consensus among developers, miners and node operators, and a BIP editor simply records those agreements in documents.
- Numbering: Dashjr assigned BIP-110 its number on X before it was discussed on the mailing list.
- He merged his own proposal within minutes of opening the pull request.
- Low activity: fewer than 1% of editor comments since April 2024.
- His first merge in over a year turned out to be the one that triggered the dispute.
Why did the BIP-110 fork fail?
BIP-110 proposed temporarily blocking non-financial data, such as Ordinals inscriptions, from Bitcoin transactions, which some developers view as network spam. Ordinals let people inscribe images, text or other data directly onto the Bitcoin blockchain, tying them to the smallest unit of the coin, the satoshi. The idea split the community long before Dashjr's removal. Some market participants saw the proposal as a way to protect the network from extra load, while others, including large mining companies, worried about losing fee revenue from those transactions. On Saturday, supporters split off their own chain. It mined only two blocks in eight hours before stopping.
According to BIP110 Monitor, not a single block has signaled for the proposal since mandatory signaling began at block 961,632. Strategy co-founder Michael Saylor tweeted that 99.85% of hashpower stayed on the main Bitcoin chain. The coin's market price barely reacted to the news, trading within its usual recent range.
What is Dashjr saying now?
Dashjr keeps disputing the decision on X, arguing that Bitcoin Core shouldn't control the BIPs repository at all. He refuses to recognize the majority chain as real Bitcoin, calling it by an offensive nickname and insisting it's guaranteed to fail. On Monday he announced a sabbatical from his role as chairman and CTO of mining pool Ocean, saying he wants to focus on open-source Bitcoin development.
"I am taking a sabbatical from OCEAN as Chairman and CTO and will turn my immediate focus to working on Bitcoin and open-source projects to support Bitcoin. I believe this is the best use of my time and is in the best interests of Bitcoin's long-term health."
- Luke Dashjr, from a post on X, August 10, 2026
What does this mean for Bitcoin going forward?
The episode shows that even a technical role like BIP editor can become a flashpoint once personal projects collide with official duties. For everyday Bitcoin holders, the drama passed largely unnoticed. The price and network held steady, since over 99% of computing power stayed on the main chain. Anyone planning to exchange Bitcoin for hryvnia soon won't see any effect from the split on the rate. For the developer community itself, the BIP-110 dispute served as a reminder that even rarely noticed editorial work depends on trust and transparent rules. The next conflict will likely center on a different proposal. Still, the pattern probably won't change much, since it will start with a mailing list discussion, move to a public pull request, and end with the network's hashpower casting the real vote.
Comments
Your email address will not be published. Required fields are marked *