Luke Dashjr is gone. BIP-110 is dead. And Bitcoin's governance illusion just got exposed.
Two days after BIP-110's forked chain fell silent, Bitcoin's BIP editors removed Luke Dashjr. The fork was a ghost chain: thousands of nodes, zero blocks since August 8. The removal took 26 hours. No written procedure. No appeal. Just a swift, opaque execution. This is not a governance bug. It is a feature of Bitcoin's myth of leaderless consensus.
Let me rewind the context. BIP-110 was a soft fork proposal. Its goal? Not fully disclosed in the public record, but its activation method was telling. Instead of waiting for miner signaling, a subset of nodes switched to the new rules unilaterally. This is a UASF-style move—user-activated soft fork. But miners did not follow. The result: a fork that produced exactly zero blocks after August 8. A dead chain. Thousands of nodes stranded on a protocol that cannot produce new blocks. This is not a hard fork like Bitcoin Cash. This is a stillbirth.
Then came the purge. Mark Erhardt, known as Murch, initiated a motion on the BIPs mailing list to remove Dashjr as editor and administrator. Within 26 hours, the permissions were revoked. Dashjr claims the accusations against him are false. Simultaneously, he announced an indefinite leave from Ocean, the mining pool he founded. The BIPs repository has no written procedure for removing editors. None. Zero. The entire process was ad hoc, based on informal consensus among a handful of individuals.
Audit the code, not the pitch. The pitch is that Bitcoin is decentralized. The code shows a centralized editorial board. The BIP-110 fork was a UASF-like attempt that failed. The removal was a counteraction. The real risk is not the fork but the governance vacuum. From my experience auditing Zilliqa's sharding consensus in 2017, I saw how a single point of failure in decision-making can undermine an entire protocol. Here, the BIP editors acted as a board of directors. They removed a dissenting voice. But the process was ad hoc. No formal procedure means any future removal could be contested. This creates a perpetual state of potential fork. The dead chain is a symptom: nodes that follow Dashjr's vision are now orphaned. The message is clear: if you challenge the editorial consensus, you risk exile. But the editors themselves are not elected. They are self-appointed maintainers. This is not governance. It is custodianship.
Complexity hides risk. The BIP-110 fork reveals a deeper structural fragility. The thousands of nodes that switched to the dead chain represent a real, if minority, faction. They are not bots. They are operators who believed in Dashjr's technical vision. Now they are left with a choice: switch back to the main chain or remain on a protocol that cannot produce blocks. That is not a choice. It is a forced migration. The editors, by removing Dashjr, have effectively disenfranchised those nodes. They have no voice in the matter. The BIPs process is not a democracy. It is a meritocracy with a thin veneer of process.
But the bulls have a point. Maybe Dashjr's proposals were technically risky. BIP-110 could have introduced unintended consequences. The rapid removal protected the network from a controversial change. The editors acted to preserve stability. However, the lack of transparency undermines trust. The contrarian angle: the removal might have been necessary, but the process was a failure of governance. The real issue is not the removal itself, but the absence of checks and balances. Bitcoin needs a formal BIP editorial process with term limits, conflict of interest disclosures, and a removal procedure with due process. Otherwise, the illusion of decentralization will continue to erode.
Sharding is easy; consensus is hard. Bitcoin's consensus is not just about mining. It is about how the protocol evolves. The BIP-110 episode shows that the governance layer is as fragile as any smart contract. I have seen this pattern before. In 2020, during MakerDAO's collateral audit, I identified a single oracle manipulation vector that could cascade into a liquidation crisis. The vector here is not code but process. The BIP-110 fork is the canary. The editors are the miners of governance. They have the power to fork the conversation.
Trust no one, verify everything. But who verifies the verifiers? The BIPs repository has no formal audit trail for editorial decisions. The removal of Luke Dashjr was executed without a public record of the specific accusations. Dashjr claims they are false, but the community has no way to verify. This is a transparency gap that rivals any centralized exchange.
Bitcoin's immutability is a product of its governance. If that governance is mutable, arbitrary, and opaque, then the immutability is a promise without a foundation. The BIP-110 dead chain is a tombstone. The removal of Luke Dashjr is a warning. The next time a controversial proposal surfaces, the same ad hoc process will repeat. And the network will splinter further. The question is not whether Dashjr deserved removal. The question is whether the procedure that removed him deserved the community's trust. The answer, based on the evidence, is no.
