- Luke Dashjr faces removal as a BIP editor over alleged procedural concerns.
- BIP-110 gained only 2.53% support before its mandatory signaling phase began.
- BIP editors manage proposals, but network adoption depends on broader consensus.
Luke Dashjr’s position as a Bitcoin Improvement Proposal (BIP) editor is under review after developer Mark Erhardt, known as Murch, opened a formal request to remove him from the BIP editors list. The dispute has emerged alongside the failed activation of BIP-110, a controversial consensus proposal backed by Dashjr that entered its mandatory signaling phase with only 2.53% support.
The situation has highlighted a central feature of Bitcoin development: there is no CEO or central authority with unilateral power to appoint or remove contributors or decide which protocol changes Bitcoin must adopt.
Who Decides Luke Dashjr’s Future?
Murch’s request, submitted on August 9, seeks to remove Luke Dashjr from the BIP3 list of editors. The motion cites procedural concerns, including an alleged attempt to assign a BIP number outside established communication channels and the merging of a pull request shortly after it opened.
Murch also pointed to Dashjr’s editing activity, stating that he had made less than 1% of editing comments since April 2024. Dashjr rejected the allegations and said he had followed the BIP process.
Do BIP Editors Control Bitcoin Changes?
The BIP process allows proposals to begin as drafts that authors develop through community discussion. Protocol proposals also require a reference implementation before they can progress toward final status.
That editorial process does not, by itself, determine whether Bitcoin adopts a consensus change. Changes that affect Bitcoin’s protocol depend on broader agreement and software adoption.
This distinction matters in the Luke Dashjr dispute. Removing an editor from the BIP repository would change who holds an editorial role, but it would not by itself change Bitcoin’s consensus rules or alter the software used by Bitcoin Core or Bitcoin Knots.
BIP-110 Shows the Limits of Editorial Influence
The BIP-110 dispute clarifies the difference between proposing a rule change and gaining network support. Mandatory signaling began at block 961,632 after only 51 of the previous 2,016 blocks signaled support.
Nodes enforcing BIP-110 produced a minority branch that generated two blocks before stalling. Another data point showed the dominant Bitcoin chain 111 blocks ahead.
A separate pull request now seeks to change BIP-110’s status from Complete through Deployed to Closed, while the specification still lists it as Complete.
No Single Party Has Final Control
The dispute leaves separate questions about Dashjr’s editorial position and BIP-110’s status. Neither issue has a single Bitcoin-wide voting mechanism that determines the outcome.
Bitcoin’s decentralized structure instead separates editorial responsibilities from consensus adoption. Developers can write and review code, while miners, node operators, businesses, and users determine whether software changes gain sufficient network adoption.
In practice, decisions such as whether Dashjr remains a BIP editor are handled through informal coordination among repository maintainers rather than a formal voting system. When disagreements arise, there is no single authority to resolve them, and outcomes instead depend on broader community alignment and software adoption.
Related: Can Bitcoin Upgrade Without Consensus? What the BIP-110 Debate Means
Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.
