
BIP editor Murch Erhardt recommends removing Luke Dashjr over inconsistent editorial authority in BIP-110, testing governance boundaries in Bitcoin's proposal process.
Alpha Score of 58 reflects moderate overall profile with moderate momentum, strong value, weak quality. Based on 3 of 4 signals — score is capped at 90 until remaining data ingests.
Bitcoin developer Mark "Murch" Erhardt, a BIP editor, has called for Luke Dashjr's removal from the Bitcoin Improvement Proposal editorial team. The accusation centers on inconsistent exercise of editorial authority related to the controversial BIP-110 soft fork.
Erhardt submitted his recommendation to the Bitcoin development mailing list on August 9. His objections include Dashjr's role in BIP-110, a premature BIP number assignment, unusually rapid merging of subsequent changes, and broader failures involving trust and coordination among editors.
The dispute tests the governance of the BIP repository, Bitcoin's formal publication system for technical proposals. Editors evaluate whether submissions meet procedural criteria, assign proposal numbers, and merge qualifying documents. Publication does not imply endorsement or community approval.
BIP-110 proposed temporary consensus restrictions on several methods for embedding arbitrary data in Bitcoin transactions. Supporters viewed it as a defense of Bitcoin's monetary function. Opponents argued fee-paying transactions should not be censored based on their purpose.
Erhardt's criticism focuses less on whether Dashjr was entitled to support BIP-110 than on whether his involvement was compatible with neutral administration. Bitcoin's repository states editors should be "liberal" in publishing qualifying proposals while avoiding excessive involvement in deciding their merits.
Erhardt, who authored the current BIP-3 process rules, argued that Dashjr's treatment of BIP-110 contrasted with his relatively limited editorial activity in recent years. He also objected to Dashjr participating directly in a contentious consensus proposal while possessing repository privileges.
Dashjr rejected the accusations. He said he consistently followed the BIP process and countered that Erhardt broke communication with other editors. He called the allegations false and argued Erhardt should be removed instead.
The confrontation follows BIP-110's failed activation. The proposal required a 55% signaling threshold for early activation and later introduced mandatory signaling. When the mandatory phase began at block 961,632, support remained around 2% to 3%. Nodes enforcing BIP-110 separated onto a minority chain that produced only two blocks.
Some BIP-110 supporters, including Dashjr, have discussed whether the stalled minority chain could adopt a different proof-of-work algorithm. No such change has been approved or activated.
Erhardt's removal recommendation does not itself dismiss Dashjr. Bitcoin has no corporate board or central authority capable of unilaterally settling the dispute. Any change will depend on repository maintainers and broader developer agreement.
The episode raises a larger governance question. BIP editors do not determine Bitcoin's consensus rules, but they occupy an influential procedural role in documenting proposals that may alter them. The argument over Dashjr tests where the community believes the boundary lies between technical advocacy and neutral stewardship of Bitcoin's proposal process.
Related: Empery Digital Sold 1,635 BTC Since July as Unrestricted Holdings Fell to 325 Bitcoin
Drafted by a large language model from the source reporting linked above, then screened by automated publishing checks. It is not read by a journalist before publication. Some articles cite our Alpha Score. Verify prices and figures against the original source. Educational coverage, not personalized advice.