Luke Dashjr has been removed from the list of Bitcoin Improvement Proposal editors following a dispute over BIP 110, a proposal he helped develop that briefly led to a low-support Bitcoin fork. The change was made through a pull request published on Aug. 11, 2026, in the public Bitcoin BIPs repository.
The removal followed criticism from Bitcoin developer Mark Erhardt, who said Dashjr’s participation in BIP 110 created a conflict with his responsibilities as a BIP editor. Erhardt opened the pull request after raising the issue on the Bitcoin Developer mailing list, where he argued that Dashjr had been closely involved in both writing and implementing the proposal while also holding an editorial role.
Jon Atack later wrote in the pull-request discussion that he had verified Dashjr no longer held editor or administrator permissions in the repository. Atack merged the change, which removed Dashjr’s name from the maintained editor list in bip-0003.md.
Dashjr responded on X by calling the action “an abuse of power by Core,” adding that those involved “have no authority to do so.”
BIP 110 dispute moved from code to governance
BIP 110 proposed a temporary limit on the amount of arbitrary data that users could embed in Bitcoin transactions. Such data can be included through mechanisms such as OP_RETURN, a transaction feature that allows users to attach small pieces of information to the blockchain.
The proposal became contentious because it sought to change transaction-relay and block-validation behavior through a coordinated activation process. Supporters framed limits on arbitrary data as a way to reduce uses of Bitcoin block space unrelated to financial transfers. Critics argued that the proposal risked creating incompatible rule sets among nodes and miners without the level of consensus normally expected for changes affecting Bitcoin’s transaction rules.
Erhardt alleged in the mailing-list discussion that Dashjr had tried to assign BIP 110 its number before the proposal had received mailing-list discussion. He also alleged that Dashjr quickly merged an update to the proposal after it was introduced. The public thread cited by Erhardt formed the basis of the subsequent repository action.
BIP editors generally handle formatting, numbering and publication of proposals rather than determining whether a technical change has community support. The BIP process does not itself activate code on the Bitcoin network, but the editor role can affect how proposals are presented, categorized and tracked. That distinction placed scrutiny on whether an editor who helped author a disputed proposal should remain involved in its administrative handling.
Fork produced only two blocks
The practical test of BIP 110’s activation mechanism ended quickly. Nodes enforcing the proposed rules split from the Bitcoin network at block height 961,632 on Aug. 9 after rejecting blocks mined by participants that were not signaling support for the proposal.
According to the proposal’s signaling results, only 2.53% of miners supported the rule change, well below its 55% threshold. The minority chain produced two blocks before stalling, reflecting the lack of hashpower available to keep the separate network advancing.
A blockchain requires miners to continue producing valid blocks for the rules accepted by that chain. When only a small fraction of total mining power follows a different rule set, block production can become extremely slow or stop altogether. The two-block outcome showed that BIP 110’s enforcement path had not attracted enough operational backing to sustain an alternative chain.
The episode also demonstrated the difference between a proposal’s presence in the BIP repository and actual network adoption. A BIP can document an idea, technical specification or implementation path, but miners, node operators, wallet providers and users ultimately determine whether software rules gain meaningful support.
Editorial removal follows a broader argument over process
Dashjr has long been a prominent Bitcoin developer and has advocated for tighter restrictions on transaction data. His removal from the editor list does not prevent him from contributing code, publishing proposals or operating software that enforces rules associated with BIP 110. It removes an administrative role in the repository used to maintain Bitcoin’s formal proposal records.
The disagreement centers less on whether BIP 110 could be discussed and more on who should administer that discussion. Erhardt’s allegations focused on process: assigning an official proposal number, updating the proposal and retaining editorial authority while favoring its implementation.
That makes the dispute relevant beyond one failed fork. Bitcoin’s development model has no central corporate board that can impose protocol changes, so repository maintenance, mailing-list norms and open-source permissions carry unusual weight. Control of those tools does not decide consensus by itself, but it can shape which proposals receive formal status and how technical debates are organized.
Dashjr’s claim that the removal was unauthorized points to the same governance tension from the opposite direction. The BIPs repository is maintained by individuals with access permissions, while its legitimacy depends heavily on whether developers view its processes as neutral, transparent and consistent.
Ocean departure came shortly before repository change
Shortly before losing his repository access, Dashjr also stepped down from his positions as chairman and chief technology officer of the Ocean mining pool, according to the supplied account. The timing adds to a period in which his public roles in Bitcoin’s development and mining ecosystem have shifted rapidly.
Repository records cited in the account show that Dashjr wrote fewer than 1% of editorial comments in the BIP tracking system since April 2024. That limited level of recorded editorial activity may have reduced the practical impact of his removal from routine proposal administration, though it does not resolve the arguments surrounding BIP 110.
Bitcoin’s main chain continued operating normally through the episode, while the BIP 110 branch lacked the mining support needed to function as a durable alternative. The immediate result is a narrower editorial structure for the BIP repository and a clearer reminder that formal proposal status cannot substitute for sustained consensus among the network participants who run Bitcoin’s infrastructure.
To understand how Bitcoin governance and protocols shape markets, explore our guide on Bitcoin’s foundations and mechanics in practice.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
