I remember the moment I saw the alert on my node. Block 961632 had been rejected by a handful of clients running a modified version of Bitcoin Core. The nodes were enforcing a rule that hadn't reached consensus—a soft fork that had barely 2.53% signal support from miners. For eight hours, the network experienced a localized chain split, two blocks orphaned by a software fork that was never meant to be a fork at all. This wasn't a 51% attack. It was a governance attack, and it came from within the developer community itself.
This is the story of BIP-110, the attempt to limit arbitrary data in Bitcoin transactions, and the subsequent removal of Luke Dashjr as BIP editor. It's a story that exposes the tension between the desire for purity and the reality of decentralized consensus.
Context: The War on Ordinals
Bitcoin's blockspace has always been a battleground. In 2023, Ordinals and inscriptions flooded the network, embedding images, text, and even entire NFTs into witness data. Purists saw this as spam, a violation of Bitcoin's original intent. Luke Dashjr, a long-time core developer and BIP editor, was among the loudest voices. He proposed BIP-110, a soft fork that would limit the amount of arbitrary data that could be included in a transaction. The technical mechanism was straightforward: enforce a new rule that rejected transactions exceeding a certain data payload. The goal was to restore Bitcoin to its intended use case—peer-to-peer electronic cash.
But the proposal never gained traction. Miners signaled support at a peak of just 2.53%, far below the 55% activation threshold. Most of the network simply ignored it. Yet, a small group of developers, likely including Dashjr, implemented the rule in their own client software. And that's where the trouble began.
Core Insight: The Fork That Wasn't a Fork
What happened next is a classic case of technical governance failure. The modified client, running a version of Bitcoin Core with BIP-110 enforced, started rejecting blocks that did not include the signal. From block 961632 onwards, these nodes refused to accept blocks mined by the majority of the hashrate, which had not signaled. The result was a temporary chain split lasting about eight hours, with two blocks orphaned on the minority fork.
Now, let's be clear: this was not a contentious hard fork. It was a unilateral enforcement of a rule that had no social consensus. The nodes that enforced it were effectively saying, "We know better than the miners and the rest of the network." This is a dangerous precedent. In my years of auditing code for decentralized protocols, I've seen similar patterns—developers who believe their technical judgment should override the messy reality of consensus. It's the same arrogance that led to the DAO hack's aftermath, the same hubris that fuels the endless cycle of Ethereum improvement proposals.
Based on my experience auditing TheDAO's successor project in 2017, I learned that code is law only if it's aligned with human values. BIP-110 was technically sound—it achieved its goal of limiting arbitrary data. But it violated the fundamental principle of Bitcoin: that no single group can impose rules on the rest of the network without broad agreement. The conscience of code demands that we respect the social layer as much as the technical layer.
Contrarian Angle: Was Luke Dashjr Right to Be Removed?
Many in the Bitcoin community celebrated Luke Dashjr's removal as BIP editor. They argue that he used his position to push a controversial proposal through the process, assigning BIP numbers prematurely and merging PRs before consensus was reached. From a procedural standpoint, they are correct. The BIP process is designed to be a neutral gatekeeper, not a platform for activism.
But let's pause. The contrarian view is that Dashjr's removal itself is a symptom of a deeper problem: the centralization of editorial power. Who decides who gets to be a BIP editor? The same group of long-time core developers. The removal was not a vote of the community; it was a decision by a small clique. This is not decentralization; it's a benevolent dictatorship. The irony is that the very people who removed Dashjr for being too aggressive are themselves consolidating power.
I've witnessed this dynamic before. In 2020, during the DeFi summer, I audited a governance contract that was supposedly egalitarian but had a hidden backdoor for early adopters. The hypocrisy of decentralized centralization is real. The Bitcoin developer community is not immune to it. The removal of Luke Dashjr may be procedurally justified, but it also sets a precedent: the BIP editor is not a neutral arbiter but a servant of the majority. That's a dangerous path.
Takeaway: The Fragile Consensus
What does this mean for the future of Bitcoin? The BIP-110 incident reveals that the network's governance is only as strong as its weakest social contract. If a small group of developers can cause a chain split with a 2.53% signal, then the network is vulnerable to more serious fractures. The takeaway is not that we should embrace Ordinals or reject them. It's that we must build better governance mechanisms—mechanisms that allow for dissent without fragmentation.
I'm not optimistic. The Bitcoin community is deeply divided between the "store of value" purists and the "digital gold" maximalists. And those who try to enforce their vision through code, like Luke Dashjr, will be removed. But those who enforce through social pressure will remain. The question is: which is more dangerous? A rogue editor or a rogue mob?
As I sit here in Denver, watching the blocks tick by, I realize that Bitcoin's governance is not a technical problem. It's a human one. And humans are messy. Perhaps the best we can do is to acknowledge the mess and build systems that tolerate it.
⚠️ The Conscience of Code
⚠️ The Voice for the Conscience
⚠️ The Vulnerable Analyst