Bitcoin Governance Under Scrutiny as Luke Dashjr Removed From BIP Editor Role After BIP-110 Fizzles

Bitcoin’s social layer just ran a live-fire drill. Days after the BIP-110 soft-fork attempt splintered into a chain that mined two blocks in eight hours and then stalled, long-time contributor Luke Dashjr was removed as a Bitcoin Improvement Proposal (BIP) editor and lost admin access to the BIPs repository. It’s less about one proposal and more about how neutrality and process discipline hold the project together when code meets coordination.

What changed and why - On August 9, fellow editor Mark “Murch” Erhardt filed a motion on the Bitcoin Development Mailing List and opened a pull request to implement it, proposing a one-line change to BIP 3 that removes Dashjr from the editor list. - Erhardt cited four issues: an alleged conflict of interest around BIP-110; irregular use of editorial authority (including an attempt to assign a BIP number on X before mailing list discussion and a near-instant merge of the corresponding pull request); limited participation in the editor role since April 2024 (fewer than 1% of editor comments, with the disputed merge being the first since May 2024); and a breakdown of trust and coordination after a soft fork appeared to drift toward a hard fork path. - Community support for the removal showed up as thumbs-up reactions and comments on the pull request.

The network’s verdict on BIP-110 BIP-110 targeted non-financial data in transactions—effectively pausing Ordinals-style inscriptions. Miner signaling never came close to activation: support peaked at 51 of 2,016 blocks (2.53%), well below the 55% threshold. Since mandatory signaling began at block 961,632, not a single block has signaled in favor, per BIP110 Monitor.

When supporters opted to split, their chain sputtered—two blocks in eight hours—and stopped. Meanwhile, critics like Michael Saylor highlighted that 99.85% of hashpower stayed on Bitcoin’s majority chain, underscoring how miners and operators tend to converge when incentives and norms are clear.

Dashjr pushes back Dashjr has continued to dispute the process and its ownership, arguing on X that Bitcoin Core shouldn’t control the BIPs repo. He has also refused to recognize the majority chain as “Bitcoin,” at one point deriding it as “Bpedo” and claiming it is guaranteed to fail. On Monday, he said he was taking a sabbatical from Ocean—the mining pool that lists him as chairman and CTO—to focus on Bitcoin and open-source work.

The real fault line: editorial neutrality as a public good This episode is a stress test of Bitcoin’s governance hygiene. Editors don’t set policy; they curate process. That distinction sounds semantic until a proposal touches culture and revenue, like inscriptions. When an editor appears to tilt the table—pre-numbering a proposal on social media, merging within minutes, participating minimally otherwise—it strains confidence in the neutral gatekeeping the BIPs repo is supposed to represent.

Technically, BIP-110’s mechanics collided with the reality of miner coordination. Signaling was an efficient referendum, not a rubber stamp. The near-zero support and the failed splinter chain showed that economic actors—pools, exchanges, custodians—tend to resist changes that risk orphaned work, user confusion, or fee-market uncertainty.

Psychologically, attempts to police on-chain expression often galvanize opposition. Developers and miners frequently prefer minimal rule-setting and market discovery over prescriptive bans, even temporary ones. Labeling the majority chain as illegitimate can rally a faction, but it rarely attracts hash rate when activation math is this lopsided.

Business-wise, the numbers spoke. With 2.53% signaling at peak and 99.85% hashpower staying put, operational risk premia for switching chains looked indefensible. Most enterprises default to continuity when faced with asymmetric downside and ambiguous upside.

Ethically, editors carry a fiduciary-like responsibility to the process, not outcomes. The move to delete a single name from BIP 3 is symbolically small yet institutionally significant: it reinforces that influence must run through transparent procedure and broad coordination, especially when a soft-fork initiative starts to resemble a hard-fork schism.

What to watch next - Repository governance: Whether the BIPs process tightens norms around pre-announcement, merge timing, and conflict disclosures. - Mining alignment: If signaling for content-curation proposals remains near zero, the market may be reaffirming protocol minimalism. - Ocean and contributors: Dashjr’s sabbatical could shift focus back to code contributions separate from editorial authority.

Bitcoin doesn’t vote with press releases; it votes with blocks. Here, the chain and the editorial bench both leaned toward conservatism, signaling that change without broad economic buy-in rarely clears the bar.