Why was Luke Dashjr removed as a BIP editor?

He was removed for alleged abuse of editorial authority and conflict of interest related to his support for the failed BIP-110 fork, and for neglecting daily duties.

What is BIP-110 and did it succeed?

BIP-110 was a proposal to create a breakaway Bitcoin chain restricting non-financial data storage; it failed, stalling after mining only two blocks due to insufficient miner support.

How quickly was Luke Dashjr removed after the motion?

He was removed roughly 26 hours after the removal motion was filed.

What are the formal rules for removing a BIP editor?

No written process for removing a BIP editor exists; the action was carried out through informal social consensus.

What changes did Luke Dashjr announce following his removal?

He announced a sabbatical from his roles as Chairman and Chief Technology Officer of the Ocean mining pool.

Bitcoin Ejects Luke Dashjr After Failed Fork Revolt

Longtime Bitcoin Core developer Luke Dashjr was stripped of his role as a Bitcoin Improvement Proposal (BIP) editor on August 10, 2026, according to CoinDesk. The move came roughly 26 hours after a removal motion was filed and is directly tied to Dashjr’s championing of the failed BIP-110 fork. He simultaneously announced a "sabbatical" from his positions as Chairman and Chief Technology Officer of the Ocean mining pool.

The proposal he backed, BIP-110, was an attempt to create a breakaway Bitcoin chain that restricted non-financial data storage, a reaction to protocols like Ordinals. It collapsed almost immediately, stalling after mining only two blocks because it attracted a mere 2.53% miner support, far short of the required 55% threshold.

What Justifies Removing a BIP Editor?

The remaining editors acted on a motion by developer Mark Erhardt that accused Dashjr of abusing editorial authority and showing a conflict of interest.

The specific charges were procedural. Erhardt claimed Dashjr assigned BIP-110 a number on social media before community discussion, then quickly merged a related update into the BIP repository, his first such action since May 2024. Erhardt also noted that Dashjr had made "fewer than 1% of the BIP Editor comments" since April 2024, suggesting neglect of daily duties.

“Luke has otherwise made hardly any contributions to the day-to-day work of the BIP Editors since the additional editors began serving in April 2024: he left fewer than 1% of the BIP Editor comments in the repository since then, and the merge action of this PR was his first since May 2024,” wrote Erhardt.

Dashjr called his removal "an abuse of power" and stated the accusations were false. The execution was technically simple: editors revoked his GitHub permissions and merged a one-line pull request deleting his name from the BIP editors list.

Where Are the Rules for a Removal Like This?

Here lies the central tension. Dashjr was removed for not following process, but no written process for removing a BIP editor exists.

BIP 3, the document outlining the editor role, lists duties but is silent on appointment or dismissal procedures. The action was carried out through an informal temperature check on the Bitcoin Development Mailing List and a GitHub permissions change, the same type of social consensus that governs much of Bitcoin's development.

XOOMAR Analysis: This reveals a governance gap. The system worked efficiently to address a perceived abuse, but it operated on trust and precedent, not codified law. The speed of the removal, 26 hours, shows how quickly this informal apparatus can move when consensus aligns. It’s effective, but its ad hoc nature could be challenged if used against a proposal with broader support, a scenario we explored in Bitcoin's Bizarre Offshoot Stalled for Six Years.

Does This End the Fight or Just Move It?

BIP-110 is formally closed. The network overwhelmingly rejected it, and all 51 signaling blocks came from Dashjr’s own Ocean pool, according to blockchain data. With his sabbatical, Ocean’s leadership is in flux.

However, the underlying ideological rift persists. Dashjr remains the maintainer of Bitcoin Knots, the node implementation that shipped BIP-110's consensus rules. The technical pathway for a similar minority chain still exists. Furthermore, the removal sets a stark precedent for future BIP editors: championing a highly contentious proposal, especially one perceived to benefit your own projects, can cost you your editorial seat.

The immediate fallout is a power vacuum in two places: the BIP editors' roster and Ocean's executive suite. The broader implication is a new awareness of the raw, unwritten power wielded by Bitcoin's core development stewards.

What to watch now:

The Ocean Pool: Who assumes operational control during Dashjr's sabbatical, and will the pool's strategy shift?
Bitcoin Knots: Will development continue to focus on alternative consensus rules, or will it re-align with Bitcoin Core?
Governance Codification: Will the remaining editors attempt to write a formal removal procedure into BIP 3, or does its absence preserve necessary flexibility?

The network's consensus mechanism cleanly killed BIP-110. The social consensus mechanism just as cleanly removed its key proponent from a privileged position. One process is encoded in proof-of-work; the other lives in mailing list posts and GitHub commits. Both just proved they work.

Why This Changes Everything

Exposes how Bitcoin's informal power structures can remove a key, long-standing figure in under a day, challenging perceptions of its decentralized governance.
Highlights the real-world consequences of failed protocol forks, where a proposal with only 2.53% miner support collapsed immediately, wasting development effort.
Raises critical questions about accountability and conflict of interest for maintainers in open-source projects with significant financial stakes like Bitcoin.