The illusion of Bitcoin's decentralized governance is a carefully maintained fiction. Every cycle, when a controversial proposal emerges, the community rallies behind the narrative of 'rough consensus'—a messy, organic process where miners, node operators, and developers converge on truth. But this week, that fiction was laid bare by a single act: Luke Dashjr, a core maintainer of Bitcoin Core, vetoed a motion to withdraw BIP-110, a proposal already mired in high controversy.
For the uninitiated, this looks like a procedural footnote. For anyone who has spent years mapping the power structures within open-source blockchain development, it is a stark reminder that Bitcoin's governance is not a democracy—it is a benevolent oligarchy of code maintainers. The veto is a signal, not just about a specific improvement proposal, but about the fragility of the entire decision-making apparatus that underpins the world's largest digital asset.
I have watched this pattern repeat since 2019, when I spent six months auditing Uniswap V1's liquidity pool mechanics and realized that the real leverage in this industry is not capital—it's the ability to merge a pull request. In Bitcoin's case, that power is concentrated in fewer than a dozen hands. Luke Dashjr is one of them. And his recent veto is a case study in how structural skepticism should be applied to crypto's most sacred governance models.
Context: The BIP-110 Saga
Bitcoin Improvement Proposal 110—whose technical details remain largely undisclosed to the public—has been described as 'highly controversial.' In Bitcoin's governance ecosystem, that phrase is code for a proposal that threatens the delicate equilibrium between miners, developers, and users. Historically, such proposals either wither under community pressure or are forced to compromise through social consensus. BIP-110, however, took an unusual turn: a faction within the community called for its withdrawal, hoping to avoid a contentious debate that could fracture the network. That motion was put to the core maintainers, and Luke Dashjr said no.
The reasoning, as per Dashjr's public statements, is rooted in his interpretation of the BIP process: a proposal should not be withdrawn simply because it is controversial. It should be debated, refined, or rejected on technical merits, not silenced by mob rule. On the surface, this sounds like a defense of rigorous discourse. But beneath it lies a deeper truth—one that exposes Bitcoin's governance as a system where a single maintainer holds veto power over the entire network's upgrade path.
To understand why this matters, we must examine the governance model itself. Bitcoin does not have a formal on-chain voting mechanism like Tezos or Polkadot. Instead, it relies on a social contract: proposals are aired on mailing lists and GitHub, debated by developers, and ultimately merged or rejected by a small group of maintainers who have commit access to the Bitcoin Core repository. These maintainers—Luke Dashjr, Wladimir J. van der Laan, Pieter Wuille, and a few others—are the gatekeepers. They are not elected by miners or users. They are self-appointed guardians of the codebase, and their legitimacy rests on historical credibility, technical competence, and the tacit acceptance of the community.
But acceptance is not accountability. And the veto of BIP-110's withdrawal exposes the fundamental asymmetry in this arrangement.
Core: The Power of a Single Veto
Let me be precise about what happened. A motion to withdraw BIP-110 was put forward. Luke Dashjr vetoed it. That means the proposal remains active in the BIP repository. It does not mean BIP-110 will be activated. But it does mean that the proposal's sponsors are now empowered to continue the debate, knowing that they have at least one core maintainer who believes the proposal deserves a fair hearing—or perhaps even supports it.
This is where the structural skepticism must be applied. In a truly decentralized system, a single individual should not be able to prevent the community from removing a controversial proposal. The fact that Dashjr can do so is a symptom of Bitcoin's governance debt. The system relies on the benevolence and judgment of a few individuals, and while Dashjr has historically been a conservative force (he famously opposed SegWit early on and argued for a different approach to scaling), his veto now sets a precedent: maintainers can overrule the majority sentiment of the community if they deem it technically or philosophically necessary.
Based on my own experience—having spent three years analyzing CBDC frameworks in Southeast Asia, watching how central banks concentrate power under the guise of stability—I recognize this pattern. Bitcoin's governance is, in practice, a form of platonic guardianship. The maintainers are not accountable to a voting base. Their power is exercised through the ability to merge or block code. And unlike a central bank, there is no legislative oversight. The only check is a fork—users and miners choosing a different client. But forks are costly, and the network effects of Bitcoin make real splits rare.
So what makes BIP-110 so controversial? The analysis from the community suggests it may involve changes to Bitcoin's scripting language or consensus rules that could affect existing smart contract layers like RGB or Taproot Assets. If so, its passage could unlock new functionality—or introduce fragility. Its rejection could stifle innovation. The fact that Dashjr has effectively kept it alive ensures that the debate will continue, but it also ensures that the debate will be toxic.
Consider the market implications. Bitcoin's price has been largely unaffected by this news, because market participants are preoccupied with ETF flows and macro liquidity. But for developers building on Bitcoin—those creating Lightning Network routing algorithms, or experimenting with BitVM-based rollups—this governance friction is a direct headwind. They need clarity. They need to know what the L1 will support in the next two years. Without that clarity, innovation migrates. It always does.
Contrarian: The Veto Is Not a Bug—It Is a Feature
Now, let me pivot to a contrarian view, because the easy narrative is that Luke Dashjr is a dictator and Bitcoin governance is a sham. That is too simplistic, and it ignores the ethical dissonance guard that should be part of any honest analysis.
The contrarian thesis is this: Dashjr's veto might actually be a prudent defense of Bitcoin's long-term stability. He has been a consistent voice against rash upgrades that could introduce systemic risk. Remember the 2017 block size war? A small group of developers advocated for a hard fork to increase block size. The community was loud. Miners were divided. But the core maintainers refused to merge the change, and eventually the community settled on SegWit, a soft fork that preserved security while achieving scaling gains. The hard fork faction went on to create Bitcoin Cash, which has since faded into obscurity. The maintainers' resistance was not censorship; it was caution.
In that light, Dashjr's veto of BIP-110's withdrawal could be seen as a way to ensure that the proposal is given a thorough technical review, rather than being killed by social pressure. He is effectively forcing the community to engage with the proposal on its merits. If the proposal is truly bad, it will die through lack of support. If it has merit, it may eventually be refined and activated. This is not oligarchy; it is quality control.
But here is the problem with that argument: it assumes that maintainers are neutral arbiters of technical merit. They are not. They have biases, and their biases shape the network's evolution. Luke Dashjr has been open about his preference for Bitcoin as a monetary settlement layer, not a smart contract platform. If BIP-110 proposes enhancements that would enable more complex scripting, Dashjr might oppose it on philosophical grounds, not technical ones. That is not neutral gatekeeping; it is political gatekeeping.
And that brings us to the real tension: Bitcoin's governance is caught between two competing narratives. The 'digital gold' narrative requires minimal changes to maintain security and stability. The 'programmable money' narrative requires continuous upgrades to compete with Ethereum, Solana, and other platforms. Dashjr's veto reinforces the former. But is that what the market wants? The market has already priced Bitcoin as digital gold, with a trillion-dollar market cap. But the premium on that narrative only holds if Bitcoin remains credible as a settlement layer. Any sign of governance paralysis undermines that credibility.
Takeaway: What Happens Next?
The most important signal from this event is not the veto itself, but the question it raises: When will Bitcoin's governance break? We have seen similar situations in other chains—the EOS community's inability to agree on upgrades led to stagnation. The Bitcoin Cash hard fork in 2018 showed how disagreements can split the chain. Bitcoin's defenders will argue that its size and network effects make it immune to such splits. I am not so certain.
Consider the user base. The majority of Bitcoin holders are passive investors who do not care about governance. They hold via ETFs or custodians. They pay no attention to BIP numbers. The active developers, miners, and node operators are a small minority. If the core maintainers become gridlocked, the development community may simply build on layer2 solutions and treat L1 as ossified. That is a viable path—but it means Bitcoin cedes the innovation narrative to other chains.
Alternatively, if BIP-110 is eventually activated despite the controversy, it could set a precedent that the maintainers are not invulnerable. That would be healthy. But if it is killed by the same maintainer who blocked its withdrawal, the cynicism will deepen.
In my time analyzing Central Bank Digital Currencies, I learned one thing: power is never willingly relinquished. Bitcoin's governance is not a democracy, and it never was. The veto by Luke Dashjr is not a bug; it is the system working as designed. But a system designed around vetoes is a system designed for stagnation.
Liquidity is a mirage; only settlement is real. But settlement requires agreement on the rules. And agreement on the rules requires a governance process that is trusted by all participants. That trust is now frayed.
The next few months will determine whether Bitcoin can evolve or will harden into a relic. Watch the BIP-110 mailing list. Watch whether other maintainers break ranks. And watch the L2 ecosystem—if builders start migrating to other L1s, you will know they have lost faith in the guardians.
