Luke Dashjr Ousted as Bitcoin BIP Editor After BIP-110 Fork Stalls

Accusations of Editorial Overreach Surface

Longtime Bitcoin developer Luke Dashjr has been removed from his role as a Bitcoin Improvement Proposal (BIP) editor following a contentious episode involving BIP-110. The removal, formalized on August 9, came after Mark Erhardt initiated a motion on the Bitcoin Developer mailing list, citing Dashjr’s inconsistent application of editorial authority. Specifically, Erhardt accused Dashjr of assigning a BIP number to the controversial BIP-110 before any substantive discussion and merging changes to the proposal within minutes—steps that bypassed the established review process.

Dashjr’s activity as an editor had already drawn scrutiny in recent months. Since April 2024, he contributed fewer than 1% of all BIP Editor comments in the official repository, with his only merge action since May being the disputed update to BIP-110. This pattern led several developers to question whether Dashjr was fulfilling his responsibilities impartially or using his position to advance certain proposals.

On paper, the BIP process is designed to ensure transparency and consensus—but this episode has exposed how easily those ideals can be challenged by internal disputes.

BIP-110 Fork Fizzles, Fallout Ensues

At the center of the controversy is BIP-110, a proposal intended to temporarily restrict non-financial data—such as Ordinals inscriptions—from being embedded in Bitcoin transactions. The proposal’s activation method required miners to signal their support by including a specific code in mined blocks, with a threshold of 55% needed for network-wide adoption. However, support peaked at just 51 out of 2,016 blocks in the relevant period—about 2.53%—falling far short of what was required.

The forked chain initiated by BIP-110 stalled after only two blocks were mined by Roughnecks using Ocean’s DATUM protocol at block heights 961,632 and 961,633.

When mandatory signaling began at block 961,632 on Saturday, only a single mining group called Roughnecks produced two blocks on the minority chain using Ocean’s DATUM protocol; after block 961,633, no further blocks were added and the fork stalled completely.

Meanwhile, the main Bitcoin chain continued unimpeded, reaching block 961,744 by Sunday afternoon. Ocean Mining responded by pledging to reimburse miners whose hashpower was unintentionally diverted to the failed fork with rewards equivalent to what they would have earned on the main chain. As reported by bitcoinmagazine.com, public figures like Michael Saylor and Adam Back criticized both BIP-110 itself and its attempted activation process.

The rapid collapse of the minority chain left little doubt about community sentiment: since mandatory signaling began, none of the first 113 blocks on the dominant chain signaled for BIP-110 at all.

Dashjr Defends Actions, Cites “Abuse”

In response to his removal as BIP editor and accusations of procedural violations, Luke Dashjr took to X (formerly Twitter) to denounce what he described as “an abuse of power” by Core developers. He maintains that the allegations against him are false and asserts that those responsible for his ouster lack legitimate authority over his position. Despite these claims, Jon Atack confirmed that Dashjr’s editor and administrator privileges were revoked following community discussion and a merged pull request.

The episode has also prompted Dashjr to announce a sabbatical from his roles as chair and CTO at mining pool Ocean so he can focus more directly on Bitcoin and open-source projects. It’s unclear whether he plans to seek reinstatement or pursue other forms of involvement within Bitcoin development circles after this break.

Miner Support for BIP-110 Falters

The numbers behind miner participation tell a stark story: out of 2,016 blocks during the relevant difficulty period leading up to activation, only about 2.53% signaled for BIP-110—far below not just the necessary 55% threshold but even basic viability for any meaningful fork attempt. Once mandatory signaling began at block 961,632, support disappeared entirely: no subsequent blocks on Bitcoin’s dominant chain signaled for activation.

This near-total lack of miner backing proved decisive; without broad hashpower support, minority forks rarely survive more than a few blocks—and in this case, just two were produced before stalling indefinitely.

For many observers in both technical and mining communities, these numbers reinforced skepticism about both BIP-110’s content and its path through governance channels. Some prominent critics argued that such low support should have precluded any attempt at activation in the first place.

Editorial Process Under New Scrutiny

Who truly decides which proposals move forward in Bitcoin—the editors who manage documentation or the broader developer and mining communities?

While Dashjr’s removal was executed swiftly after Erhardt’s motion on August 9 received visible support via thumbs-up reactions and comments on GitHub, it has sparked renewed debate over how much authority individual editors should wield—and what checks exist when process is perceived as compromised. Jon Atack handled the technical removal by merging a pull request that deleted Dashjr’s name from BIP 3 (the official list of editors), cementing what some see as a rare but necessary intervention against editorial overreach.

As governance debates continue and new proposals emerge in coming months, it remains uncertain whether this episode will result in lasting changes to how Bitcoin Improvement Proposals are managed—or simply serve as another chapter in ongoing struggles over decentralization and control within Bitcoin’s open-source ecosystem.

What to watch closely

If any blocks begin signalling for BIP-110 after block 961,632—where mandatory signalling started—it would immediately indicate renewed miner support, but as of now, none of the first 113 blocks on the main chain have signalled and whether this will change remains unclear.