Luke Dashjr removed as Bitcoin BIP editor following controversial BIP-110 fork failure
Veteran Bitcoin developer Luke Dashjr was formally removed from his position as a Bitcoin Improvement Proposal (BIP) editor on August 10, 2026. This significant decision by other core developers follows the dramatic failure of BIP-110, a controversial soft fork proposal championed by Dashjr that resulted in a brief, non-consensus chain split from the main Bitcoin network.
The move underscores mounting tensions within Bitcoin’s development community, with critics citing allegations of conflict of interest and a severe breakdown in trust as key factors in Dashjr’s removal from the influential role.
The contentious BIP-110 soft fork’s demise
BIP-110, officially titled “Reduced Data Temporary Softfork,” was designed to temporarily limit non-financial data storage on the Bitcoin blockchain. Submitted by the pseudonymous developer Dathon Ohm, the proposal aimed to restrict ordinary new output scripts to 34 bytes and cap OP_RETURN scriptPubKeys at 83 bytes for approximately one year, intending to curb what proponents viewed as network spam.
However, the proposal faced widespread opposition across the Bitcoin industry. Many argued against its necessity and the manner of its attempted activation, including MicroStrategy Chairman Michael Saylor, who published a 110-point essay deeming BIP-110 “extremely dangerous.”
The soft fork required 55% miner support over a two-week period to activate, but it garnered minimal backing. Only 51 blocks, representing a mere 2.53% of the preceding 2,016 blocks, signaled support during the crucial difficulty adjustment period. All of this limited support originated from the Ocean mining pool, where Dashjr serves as Chairman and CTO.
On August 8, 2026, at block height 961,632, nodes running BIP-110 software attempted to enforce the change, rejecting blocks that did not conform. This action inadvertently created a minority chain, causing a split from the main Bitcoin network as critics had warned. The Bitcoin network continued uninterrupted, while the BIP-110 chain produced only two blocks over roughly eight hours before stalling completely.
Dashjr’s removal from BIP editor role
The formal motion for Dashjr’s removal was filed by Bitcoin developer and BIP editor Mark “Murch” Erhardt on the Bitcoin Development Mailing List at 18:53:50 UTC on August 9, 2026. The technical execution followed swiftly, with Dashjr’s editorial privileges and GitHub repository administrator access for Bitcoin BIPs being revoked.
This involved removing his GitHub permissions and merging Pull Request #2248, which simply deleted his name and email from BIP 3, the foundational document governing the proposal process. Bryan Bishop, another BIP editor, confirmed Dashjr’s removal on the mailing list at 20:52 UTC on August 10, 2026, with Jon Atack merging the request shortly after.
Allegations of conflict and minimal contribution
Mark Erhardt’s motion outlined four primary reasons for Dashjr’s dismissal, painting a picture of escalating friction and governance concerns. A central allegation was a clear conflict of interest; Dashjr was deeply involved in both the creation and implementation of BIP-110.
He reportedly exercised his authority as a BIP editor inconsistently with established editorial processes, unfairly favoring his own proposal. Instances cited included attempting to assign a BIP number publicly on Twitter before a mailing list discussion and merging a pull request updating the BIP within minutes of its opening.
Furthermore, Erhardt noted Dashjr’s minimal contribution to the day-to-day operations of the BIP Editors. Since April 2024, Dashjr had left “fewer than 1% of the BIP Editor comments in the repository,” and the BIP-110 merge was his first such action since May 2024.
The motion also highlighted Dashjr’s leadership in a contentious fork as a “complete departure from the Bitcoin development ecosystem,” and cited a breakdown in trust and communication among the BIP editors.
Dashjr reacts and shifts focus
Just two minutes after Bryan Bishop confirmed his removal, Luke Dashjr took to X (formerly Twitter) to announce a change in his professional life. He stated he was taking a sabbatical as Chairman and CTO from Ocean, the mining company that was the sole supporter of the failed BIP-110 fork.
He publicly characterized his removal as an “abuse of power by Core,” maintaining that “They have no authority to do so.” Dashjr declared his intention to dedicate his efforts to “working on Bitcoin and open-source projects to support Bitcoin,” signaling a continued commitment to the ecosystem despite the recent setback.
Dashjr is a long-standing figure in the Bitcoin community, having been a Bitcoin Core developer since 2011 and contributing significantly to projects like the activation of Segregated Witness (SegWit) and resolving a blockchain split in 2013. His co-founding of Ocean in November 2023 with Mark Artymko and Ian Northon aimed to decentralize Bitcoin mining.
The company, which received seed funding from Jack Dorsey, sought to give miners more control over block construction. This background makes his departure from the BIP editor role and temporary step back from Ocean particularly notable for industry observers.
Implications for Bitcoin governance and development
The dramatic removal of Luke Dashjr sends a clear message about the boundaries and expectations for Bitcoin Improvement Proposal editors. It reinforces the idea that even long-standing and influential contributors are subject to the community’s consensus-driven governance mechanisms, especially when perceived conflicts of interest arise.
This event highlights the decentralized yet highly scrutinised nature of Bitcoin’s development. While anyone can propose changes via the BIP process, the gatekeeping role of editors is crucial for maintaining the network’s integrity and preventing unilateral action. The community’s firm rejection of BIP-110, combined with the swift action against Dashjr, demonstrates a collective resolve to protect Bitcoin’s core principles.
The stalled BIP-110 chain, which as of August 11, 2026, is 326 blocks behind the main Bitcoin chain, serves as a stark reminder of the risks associated with non-consensus changes.
Its next difficulty adjustment is an estimated 6.3 years away due to inheriting the full network difficulty with only about 0.15% of the hashrate, rendering it effectively defunct. BIP-110 is now officially marked “Closed” in the BIP repository.
Moving forward: A precedent for developer accountability
This episode is likely to set a precedent for developer accountability within the Bitcoin ecosystem. It shows that influence and past contributions don’t grant immunity from critique or consequences when actions are seen to deviate from established norms or threaten network stability.
For the remaining BIP editors — Bryan Bishop, Jon Atack, Mark Erhardt, Olaoluwa Osuntokun, and Ruben Somsen — the focus will be on restoring trust and maintaining a transparent, collaborative environment.
The community will be watching to see how this impacts future BIP submissions and the overall dynamic among core contributors. It’s a potent reminder that despite its decentralized nature, Bitcoin relies heavily on the good faith and careful stewardship of its most dedicated developers.
Moving ahead, the emphasis will likely be on stricter adherence to process and a clear avoidance of even the appearance of conflict.
The incident also underscores the ongoing debate within the community regarding acceptable uses of the Bitcoin blockchain.
While Dashjr and his supporters viewed data such as Ordinals as “spam” to be purged, a significant portion of the community sees such data as valid transactions, or at least not something that warrants a contentious hard fork or soft fork without overwhelming consensus.
This ideological divide isn’t new, but the BIP-110 failure and its aftermath have brought it to a head.
The long-term impact on developer relations and project governance remains to be seen, but for now, the message is clear: consensus and process are paramount in the Bitcoin world.
The community will likely remain vigilant in ensuring that future proposals align with the network’s overarching principles of decentralisation and security, with any deviation met with firm resistance. Bitcoin’s volatility remains a constant, but its governance mechanisms are proving robust.