The numbers didn’t lie, but my trust did. For three days, the Bitcoin Core mailing list had been a battlefield. BIP-110, a proposal to introduce basic covenants on Bitcoin L1, was facing a coordinated push for withdrawal. The noise was deafening: developers called it a Trojan horse for ‘smart contract bloat,’ while institutional supporters whispered about unlocking DeFi trillions. Then came the quiet missile—Luke Dashjr, the core maintainer with the austere beard and the Merkle-tree mind, vetoed the withdrawal. No explanation. No code comment. Just a single reject on the GitHub pull request. The market barely flickered—BTC stayed flat around $68,500—but the fault line in Bitcoin’s governance had just cracked open.
Context: The House That Satoshi Left Unfinished
Bitcoin’s governance is a paradox—a decentralized system with human gatekeepers. The Bitcoin Improvement Proposal (BIP) process is meant to be permissionless: anyone can propose a change, but only a handful of core maintainers, Lazarus-like, can merge code into the master branch. Luke Dashjr is the most adamant of those maintainers. He has been a Bitcoin Core developer since 2011, long before the ETF approvals and the Ordinals mania. His philosophy is simple: Bitcoin is not a platform for innovation; it is a settlement layer for value. Change must be minimal, tested, and agreed upon by ‘rough consensus.’ In practice, rough consensus means: if Dashjr says no, the code stays out.
BIP-110, as far as the public knows, proposes a minimal covenant primitive—a way for transactions to enforce conditions on future spends. Think of it as a conditional lockbox for BTC. Proponents argue it would enable secure vaults, improved Lightning channel factories, and trust-minimized atomic swaps. Opponents see it as the thin end of the wedge: once covenants are in, complex contracts follow, and with them, Turing-complete risks on the most valuable blockchain. The proposal had been in ‘draft’ for six months, gathering dust, until a coalition of startup founders and venture capitalists began a media campaign to fast-track it. The pushback was predictable: a dozen senior developers signed an open letter calling for immediate withdrawal, citing ‘unresolved security concerns and lack of community consensus.’
Core: The Order Flow Nobody Sees
I’ve spent years analyzing incentive flows—first as a Solidity auditor in 2017, then as an arbitrageur on Curve. In those trenches, I learned one iron rule: power follows order flow, not votes. In Bitcoin’s case, the order flow is not retail buying on Coinbase; it is the flow of code commits and merger decisions. Dashjr’s veto is not democracy—it’s a check on democracy. He is the circuit breaker against capitulation to market pressure.
Let’s dissect the numbers. Over the past 12 months, Bitcoin’s hashrate has risen 78%, but the number of active developers contributing to Bitcoin Core has declined by 15% (source: Electric Capital). The network is becoming more secure computationally but less resilient intellectually. A small group of maintainers now controls the upgrade path. Dashjr’s veto is a signal: he is willing to short-circuit the very process he protects. Why? Because he sees the hidden risk that retail hype ignores.
From my own copytrading community—500 traders who follow my signals—I see the retail blind spot every day. They crave the next catalyst, the new narrative. A Bitcoin covenant upgrade sounds bullish: more utility, more adoption. They don’t see the fractal of risk. I missed a reentrancy vulnerability in 2017 because I trusted the code looked clean. The exploit cost $1.2 million and a project’s life. I learned that security is not in the code alone—it is in the incentives around the code. A covenant vulnerability—even a subtle one—could allow an attacker to freeze BTC in multisig wallets, affecting custodians like Coinbase, BitGo, and the ETF custodians handling $60 billion in AUM. The damage would be systemic, not isolated.
Dashjr understands this. His veto is not anti-innovation; it is anti-negligence. He is saying: you haven’t convinced me, and the process requires my conviction. The proposal is still alive, but its future is uncertain. In the meantime, the order flow of development attention will shift. I have observed that conversations on the Bitcoin-Dev mailing list have already pivoted to alternative proposals—BIP-119 (CTV) and BIP-118 (SIGHASH_ANYPREVOUT). Both are more conservative and have existing early implementations.
Contrarian: The Blind Spot of ‘Smart Money’
The popular narrative is that Luke Dashjr is a relic, a Luddite blocking progress. Institutional investors see him as a risk to Bitcoin’s competitiveness. They point to Ethereum’s ability to iterate and adapt, and they call Bitcoin ‘dinosaur money.’ The counterintuitive truth is that Dashjr’s veto may be the very reason institutional capital is flowing into Bitcoin—not despite it, but because of it.
In 2020, I engineered an arbitrage bot for Curve stablecoins. I deployed $50,000 of my own capital, but the real edge came from reading incentives, not code. When a competing protocol tried to manipulate yields via governance attacks, my bot survived because I had positioned for irrational behavior, not rational markets. That lesson taught me that the most reliable signal in crypto is conservatism under pressure. Dashjr’s conservatism is the same: it is a bet that the cost of moving fast and breaking things is higher than the gain. For a global reserve asset, stability is itself the feature.
The blind spot of ‘smart money’ is that they project the same risk appetite from altcoins onto Bitcoin. They see the lack of upgrade as a bug, but the largest ETF issuers—BlackRock, Fidelity—have explicitly stated that they value Bitcoin for its immutability, not its programmability. Dashjr’s veto supports that narrative. If BIP-110 had been rushed through and then broken, the regulatory fallout would have been catastrophic. SEC would question whether Bitcoin is truly decentralized if a small group of developers can change its rules. Dashjr’s inaction is actually an action for regulatory clarity.
Takeaway: The Silence Behind the Code Review
Where does this leave us? BIP-110 is not dead; it’s in a state of limbo. Dashjr refused to withdraw it, but he hasn‘t merged it either. The community is split, and the proposal’s future rests on whether a champion emerges to rework the implementation and build a coalition strong enough to override Dashjr’s resistance—or to replace him as maintainer. Neither is likely in the short term.
The real action will be in the margin. Developers who wanted covenants will drift to sidechains (Liquid) or new L1s like blockstream’s sidechain or even BitVM-based approaches. The Ordinals mania showed that fee revenue can be unlocked without L1 changes—through inscription data. That fee revenue now accounts for 2-3% of Bitcoin’s total security budget. If Bitcoin cannot upgrade, it may rely more on such external innovations, which introduces its own risks—centralization through sidechain operators.
For the trader: do not bet on a binary outcome. The market will price in neither immediate upgrade nor permanent stagnation. Instead, watch the GitHub pulse. If Dashjr’s veto is overruled by other maintainers or if a new draft of BIP-110 appears, volatility will spike. Until then, the current remains: Bitcoin’s governance is art, not science. Art burns hot; patience burns colder.
Silence is the loudest audit. And today, the silence from the miners and exchanges tells me they are comfortable with the status quo. They will not activate a contentious change. The numbers didn’t lie, but my trust did—I trusted that a single developer’s veto would break the spell. Instead, it revealed that Bitcoin’s governance is working exactly as designed: slowly, painfully, and with enough friction to make sure we really want the change.