Luke Dashjr didn’t just disagree with his removal as a Bitcoin Improvement Proposal editor. He built a parallel system and called it the real one. On Nov. 10, Dashjr announced that Bitcoin-specs/BIPs is now the “official” home of BIPs, three months after the existing repository’s five editors removed him. GitHub labels the new repository as a fork of bitcoin/bips, not a transfer. The original archive remains active, with merges recorded as recently as Nov. 9.
This isn’t a technicality. It’s a direct challenge to the editorial authority that has governed how Bitcoin proposals are published and archived for years. And it’s the most visible escalation yet in a dispute that has been simmering since August.
What Dashjr Changed in the Fork
Commits from Dashjr’s luke-jr account restored his editor listing, which the original repository had removed. He also reversed BIP-110, a proposal to temporarily limit arbitrary data in Bitcoin transactions, from “Closed” back to “Complete”. In the original repository, BIP-110 remains “Closed,” and the changelog still explains that closure as following a chain split with stalled mining.
Dashjr framed the August changes as unauthorized. “These unauthorized changes have been corrected,” he wrote on X, “while preserving the repository’s history and legitimate editorial work”. He added that “Bitcoin Core has no authority over the BIP process, which remains independent of any particular Bitcoin implementation”.
That’s the core of the fight. The BIP repository is supposed to be a neutral publication medium, not a battleground for implementation politics. BIP 3, the process document, explicitly says individual BIPs do not represent community consensus or a general recommendation for implementation. Dashjr is arguing that the editors who removed him violated that neutrality. His critics argue he violated it first by manipulating BIP-110’s status and then by claiming his fork is “official.”
The August Removal That Started It All
The timeline matters. On Aug. 9, BIP editor Mark “Murch” Erhardt filed a motion to remove Dashjr, citing conflict of interest and a breach of the editorial process. Within roughly 26 hours, the removal was executed. Jon Atack later verified that Dashjr no longer had editor or administrator rights in the original repository.
BIP-110 was the flashpoint. The proposal sought to restrict non-financial data on Bitcoin, a response to the Ordinals and inscription wave. When its mandatory signaling period began rejecting non-signaling blocks, the chain split and mining stalled. The editors closed the BIP and removed its most vocal champion. Dashjr’s response, three months later, is to restore both the proposal and himself in a repository he controls.
I think this is less about BIP-110’s technical merits and more about a fundamental question: who gets to decide what “official” means in a decentralized protocol? In my experience covering open-source governance, the answer is usually “whoever has the most credible claim to legitimacy.” Right now, both sides have one.
The Mailing List Gambit
Dashjr isn’t stopping at the repository. He’s also established a new Bitcoin Development mailing list, claiming the former list has been “subject to censorship”. He’s proposing an amendment to BIP 3 that would formally designate the new list as the official BIP development forum. Messages to the new list are being held for moderation until Friday, Nov. 13, to give developers time to subscribe.
This is a classic institutional fork. You lose control of the process, so you create a new process and invite people to follow you. The question is whether anyone shows up. The existing repository still has five editors, including Erhardt, Atack, Olaoluwa Osuntokun, and Ruben Somsen. These aren’t marginal figures. They’re core contributors with deep credibility. Dashjr’s fork has history and a familiar name, but it doesn’t have their signatures.
What the Split Means
The immediate risk is confusion. Two repositories, two editor lists, and two mailing lists create ambiguity for proposal authors and reviewers. If the people who actually merge consensus changes ignore Dashjr’s fork, the “official” label becomes symbolic rather than operational. BIP-110 stays closed, stalled, and rejected by miners who never signaled for it. That’s governance theater without governance consequences.
But there’s a more interesting possibility. If Dashjr’s central claim, that Bitcoin Core has no authority over the BIP process, resonates with enough developers, the fork could become a genuine alternative archive. Even if it doesn’t, the controversy might push the existing editors to clarify their own authority and make the process more transparent. I think a fight like this is sometimes the only way to find out where the real lines are.
What to Watch
Watch the moderation window for the new mailing list. If serious developers subscribe and participate, Dashjr’s fork gains credibility. If the list stays quiet, it becomes a protest channel. Watch whether any proposal authors submit new BIPs to the fork instead of the original repository. Watch whether the existing editors respond with a formal statement on authority, or with silence. And watch BIP-110. If it stays closed in the original repository while marked “Complete” in Dashjr’s, the split becomes concrete, not theoretical.
Summary
Luke Dashjr’s declaration that his forked repository is the “official” home of Bitcoin Improvement Proposals is a direct challenge to the editors who removed him in August. By restoring his own editor status and reversing BIP-110’s closure, he’s turned a procedural dispute into a public legitimacy contest. The original repository remains active with five editors and no signs of stepping back. The coming weeks will reveal whether Dashjr’s fork attracts real contributors or becomes a symbolic protest. Either way, the episode exposes a tension Bitcoin has never fully resolved: in a system with no central authority, the fight over who controls the archives is the fight over who controls the narrative.
Comments
Please login to comment
Login