Bitcoin maintainers oust Luke Dashjr after failed fork

Node operators tried to bully miners into a code rollback. Miners barely flinched.

The failed activation of Luke Dashjr’s BIP 110 soft fork has triggered a swift governance reckoning across the Bitcoin development community. Mark Erhardt, known as Merch in the core contributor space, filed a pull request to strip Dashjr of his role as a Bitcoin Improvement Proposal maintainer. Erhardt cited editorial misconduct, pointing out that Dashjr skipped mandatory code review procedures to fast-track BIP 110 - despite having authored fewer than 1 percent of editorial comments over the previous four months.

Dashjr’s proposal sought to strip non-financial data like Ordinals from the blockchain and roll back Taproot additions. For a moment, ideological users seemed ready to follow. As investor Simon Dixon highlighted on BTC Sessions, node adoption of Dashjr’s custom Bitcoin Knots client surged from under 1 percent to nearly 20 percent. Dixon described the campaign as a deliberate stress test to see whether an organized minority of sovereign nodes could coerce major pools like Foundry into enforcing stricter protocol limits.

The answer from the mining sector was an emphatic rejection. Michael Saylor noted on Bitcoin And that 99.85 percent of total network hash power remained firmly on the main chain. Dashjr’s split chain stalled out almost instantly, producing just four blocks in a week while operating under a single pool - his own Ocean mining venture.

When the soft fork collapsed, the minority chain maintainers pivoted toward a complete hard fork targeting Blake2b GPU mining. The fallout inside Dashjr's own camp was immediate. Dashjr announced a sabbatical from his leadership position at Ocean pool, departing alongside co-founder Mechanic while publicly criticizing main-chain developers.

On Stacker News Live, hosts Keon and Car analyzed the structural residue of the split. Keon characterized the event as a clean break that excised bad-faith governance tactics from the core project. Car warned that even a dead-end GPU fork could siphon critical developer attention away from primary layer-one improvements.

The episode offers a stark counterpoint to the 2017 block size war. Nine years ago, user nodes successfully blocked corporate actors from forcing SegWit2x onto the network. The BIP 110 collapse proved that while node operators hold veto power against unwanted changes, they cannot unilaterally force miners to enforce policy rollbacks without total ecosystem consensus.

Ego ran headfirst into network consensus, and consensus won.