Luke Dashjr has been removed from his role as a Bitcoin Improvement Proposal editor following developer pushback over his handling of BIP 110 and involvement with a stalled minority fork effort.
The removal marks a significant governance shift in Bitcoin's technical development process. Dashjr, a long-time Bitcoin Core contributor, faced criticism from the developer community regarding his editorial decisions and his work on BIP 110, which relates to block size changes. His connection to a minority fork initiative that failed to gain traction intensified calls for his removal from the BIP editor position, a role that carries substantial influence over which proposals move forward in Bitcoin's evolution.
BIPs serve as the formal specification mechanism for Bitcoin protocol upgrades and feature additions. Editors control which proposals receive formal numbers and can move through the review process. The editorial position carries gatekeeping authority over Bitcoin's technical roadmap.
The community's action reflects broader tensions within Bitcoin development. The block size debate has festered since the 2017 scaling wars, when disagreements over transaction throughput sparked the creation of Bitcoin Cash. Dashjr historically opposed larger blocks and advocated for conservative approaches to protocol change. His BIP 110 proposal and connection to the fork attempt appeared to contradict his stated philosophy, prompting scrutiny from other developers.
Removing Dashjr from the editor role doesn't strip his status as a Bitcoin Core contributor or eliminate his ability to propose new BIPs. The move specifically constrains his authority to shepherd proposals through the formal improvement process.
Bitcoin development governance remains decentralized and informal compared to traditional corporate structures. Changes to editor rosters happen through community consensus rather than formal voting. This removal signals that developers prioritized governance transparency and neutrality over individual contributor status.
The incident underscores how Bitcoin's technical stewardship depends on community trust. Editor roles require perceived impartiality, and