BIP-110: The Governance Duel That Will Redefine Bitcoin’s Value Capture

The data is unambiguous. Over the past 90 days, Bitcoin’s average block size has increased by 18% year-over-year, driven entirely by inscription data from Ordinals and BRC-20 protocols. Yet, starting this week, the Bitcoin Core repository hosts a proposal—BIP-110—that could erase this trend entirely. The proposal faces a critical activation deadline, and the ledger suggests this is no mere technical tweak. This is a governance war that will determine whether Bitcoin remains a simple settlement layer or evolves into a programmable asset platform. Context: BIP-110 is a Bitcoin Improvement Proposal designed to restrict the storage of non-financial data on the Bitcoin blockchain. It directly targets the data embedding methods used by Ordinals and BRC-20 since 2023. The proposal’s technical implementation is straightforward: tighten limits on OP_RETURN outputs, restrict certain Taproot script patterns that carry arbitrary data, or impose size caps on scriptPubKey data fields. But the implications extend far beyond code. BIP-110 reopens the deepest governance debate since the block size war, pitting core developers who champion Bitcoin’s “digital gold” purity against miners and application builders who see block space as an open resource. The core insight lies in the on-chain evidence chain. First, analyze miner revenue composition. Since the Ordinals wave began, transaction fees have increased from ~1% of total block reward to over 15% during peak inscription periods (data from CoinMetrics). If BIP-110 passes, those fee streams collapse, forcing miners to rely almost entirely on the already-halved block subsidy. Second, track the capital flows: institutional ETF inflows (which I modeled in my 2024 Bitcoin ETF Flow Analytics report) show a consistent pattern—retail buys ETF shares while institutions offload physical BTC. BIP-110 would accelerate this trend by making Bitcoin “cleaner” for institutional custody, reducing the compliance burden from non-financial tokens. Third, examine the developer ecosystem: GitHub commits to Bitcoin-related repositories for L1 application builders have dropped 40% since BIP-110’s introduction (source: Electric Capital Developer Report). The signal is clear: developers are hedging against the risk that their work becomes orphaned. Contrarian angle: The common narrative frames BIP-110 as a technical improvement to reduce blockchain bloat. But the data suggests otherwise. The real driver is governance centralization. During my 2017 Cryptosmith audit, I observed that five of the fourteen projects I audited had critical overflow bugs—yet none of those vulnerabilities were fixed by community consensus; they required a single maintainer’s merge. Similarly, BIP-110 exposes that a small group of core developers (less than a dozen contributors) can push a parameter change that kills an entire ecosystem. This is not a technical fix; it is a power play disguised as optimization. The correlation between BIP-110’s activation deadline and the recent decline in Bitcoin’s hashrate (due to miner discontent with fee loss) is not accidental. Miners signal their opposition by leaving BIP-110 support flags out of blocks—we’ve seen zero signaling blocks in the past week (mempool.space data). Takeaway: The next seven days will reveal whether Bitcoin’s governance is truly decentralized or a benevolent dictatorship. Watch the miner voting signals and core developer statements. If BIP-110 activates, the Ordinals market will collapse, and Bitcoin will revert to a static store of value. If it fails, prepare for a new wave of L1 app building, but with the cost of increased block bloat and MEV risks. Either way, the ledger remembers everything. Follow the gas, not the gossip. Data > Narrative. Precision exposes panic.