TL;DR
- Luke Dashjr was removed as a Bitcoin Improvement Proposal editor after developers raised concerns about his involvement in creating, implementing and advancing BIP 110.
- Mark Erhardt alleged Dashjr favored BIP 110 while serving as editor, including trying to assign a number before mailing-list discussion and rapidly merging an update.
- Jon Atack confirmed Dashjr lost repository privileges, while BIP 110’s minority fork stalled after attracting little hashpower, intensifying debate over governance.
Bitcoin developer Luke Dashjr has been removed as an editor of Bitcoin Improvement Proposals after developers raised concerns about his role in BIP 110 and the stalled minority fork tied to it. Mark Erhardt opened the pull request on Sunday following a recommendation on the Bitcoin Developer mailing list. The dispute is unusually sensitive because it combines technical governance with allegations that an editor favored a proposal he helped create and implement. Dashjr rejected the decision, arguing that Bitcoin Core had abused its power and lacked authority to remove him from the role.
This is just an abuse of power by Core.
They have no authority to do so.— Luke Dashjr (@LukeDashjr) August 10, 2026
BIP 110 controversy spills into Bitcoin’s proposal process
Erhardt alleged that Dashjr had been heavily involved in creating and implementing BIP 110 while also using his editorial position in ways that favored the proposal. According to the account, Dashjr attempted to assign BIP 110 a number before discussion on the mailing list and later merged an update to it quickly. The concern was not simply that Dashjr supported BIP 110, but that his support overlapped with responsibilities meant to administer the proposal process. That overlap became the central governance issue behind calls to remove his repository privileges.
Bitcoin developer Jon Atack said he verified that Dashjr no longer had editor or administrator privileges in the BIPs repository following the mailing-list discussion. Atack then merged the pull request that removed Dashjr from the official list of BIP editors. The sequence turned a public disagreement into a concrete change in Bitcoin’s development infrastructure, rather than leaving the matter as a debate over conduct. Dashjr, however, disputed the legitimacy of the action, framing the removal as an abuse by Core rather than an accepted outcome of community governance.
BIP 110 itself sought to temporarily restrict the amount of arbitrary data that could be embedded in Bitcoin transactions. Nodes enforcing the proposal later rejected blocks from miners that did not signal support, creating a minority chain split. The fork quickly stalled because it attracted little hashpower. That failure now hangs over the editorial dispute, making the removal inseparable from questions about how aggressively developers should advance controversial changes. The episode leaves Bitcoin’s proposal process facing a familiar but difficult problem: how to preserve neutral administration when influential contributors are also active advocates inside a decentralized project without a conventional central authority.
