BIP-110 is now the most contentious proposal of the year. That's not my line — it's the working consensus across Bitcoin's developer ecosystem. Michael Saylor just turned it into a constitutional crisis.
The Strategy chairman didn't mince words. He called consensus rules Bitcoin's "constitution" — the document defining property rights, scarcity, settlement finality, and power distribution. His enemies list: BIP-110's data-field limits, covenant proposals, and larger block sizes. All three, he argues, are constitutional violations. All three, he insists, weaken the network that holds more than 400,000 BTC on his company's balance sheet.
I've audited enough rule-change battles to know when a fight is real. This one is. And the market hasn't priced it yet.
Over the past seven days: zero price movement from Saylor's declaration. Zero liquidation cascades. But the positioning underneath is shifting. Miners are watching. Institutional desks are watching. And the Ordinals crowd — the actual target of BIP-110 — is watching with knives out.
This is not about blocksize. It's about who controls Bitcoin's rulebook.
Bitcoin doesn't have a parliament. It has rough consensus and running code. But that's never been as clean as it sounds.
In 2015, the blocksize war split the community. SegWit took two years to activate. Taproot shipped in 2021 after years of deliberation. Every rule change risks a fork, a narrative fracture, or a breakdown in user confidence.
BIP-110 is a temporary soft fork proposal designed to limit data-field sizes and reduce blockchain bloat. The subtext: Ordinals, inscriptions, and BRC-20 tokens are clogging block space. The intent: restore Bitcoin's "peer-to-peer electronic cash" positioning. The implication: non-monetary uses of block space are illegitimate.
Covenant proposals — CTV (BIP-119), CAT (BIP-347), and others — aim to expand Bitcoin's scripting capabilities. Vaults, atomic swaps, more complex smart contracts. Saylor calls them an attack surface. The bigger-block crowd wants capacity. Saylor calls it dilution.
These are three different fights. Saylor has collapsed them into one. That's the move. And it's why the debate is now ideological rather than technical.
Let's step back and look at what's really hanging in the balance. Bitcoin carries roughly 55-60% of total crypto market cap. It's the only digital asset with ETF flows that institutional desks treat as a treasury reserve asset. That status is precisely what makes this governance moment dangerous. When an asset transitions from speculative vehicle to institutional reserve, its rulebook becomes a financial instrument. Every proposal, every BIP, every community argument is now a risk factor priced by compliance teams at firms managing billions.
This is the angle most coverage misses. The SEC approved spot Bitcoin ETFs in January 2024. That approval changed Bitcoin's legal and financial gravity. The ETFs created a regulated on-ramp for pension funds, endowments, and corporate treasuries. Those institutions didn't buy Bitcoin because of its smart-contract capabilities. They bought it because it fits a scarcity narrative that consultant decks describe as "digital gold." Now imagine those same institutions watching a high-signal governance fight over whether Bitcoin should censor certain transaction types. That's not a technical discussion. That's a compliance event.
Institutional investors don't want to explain to their boards why the asset they purchased as a stable, rules-based reserve is suddenly undergoing a philosophical civil war over inscription data. The ambiguity itself is the risk. Saylor's intervention serves as a reassurance mechanism: a prominent, deep-pocketed voice saying "I will fight any rule change that threatens your investment." That is why his remarks matter far beyond Twitter engagement. He is not just advocating for a technical position. He is protecting the regulatory narrative that underpins Bitcoin's institutional adoption.
But here's what Saylor doesn't address: institutions also need Bitcoin to function as a settlement layer. A base layer that is too expensive or too restrictive for ordinary transactions will eventually peak as an institutional monopoly asset. The ETF crowd may want stability today. They will want capacity tomorrow. Saylor's equilibrium is unstable.
The constitution argument deserves its own scrutiny.
Saylor says consensus rules are Bitcoin's constitution. The analogy is useful but incomplete. A constitution is a living document — it has amendments. Bitcoin's history is a history of amendments. SegWit was an amendment. Taproot was an amendment. Even the 2017 blocksize compromise was an amendment.
Saylor's real position: some amendments are legitimate, others are not. The line he draws is between preserving Bitcoin's monetary properties and expanding its functional scope. But he doesn't define that line with technical precision. He defines it with a hammer. All three proposals — regardless of their distinct technical risks — get the same constitutional curse.
This lack of discrimination matters. It matters because BIP-110 and covenant proposals have opposite risk profiles.
BIP-110's core technical logic is straightforward. Limit data-field sizes. Reduce blockchain bloat. Push non-transactional data off-chain.
On its surface, this is a reasonable optimization. Bitcoin blocks are finite. If inscriptions are consuming a substantial share of block space for what is essentially digital artwork, then transaction fees for legitimate users — exchanges, remittances, settlement — rise. A limit restores the market for block space to its original purpose: monetary transactions.
But here's the trade-off Saylor nails: BIP-110 is a restriction, not an enhancement. It defines what transactions are "valid" by excluding certain data types. That's a form of censorship at the protocol level. The soft fork would invalidate transactions that miners currently include. That's a clean break from Bitcoin's historical commitment to simple, strict, non-content-based validation.
The danger isn't the rule itself. The danger is the precedent. If Bitcoin can exclude data types it deems non-monetary, what else can it exclude? This is Saylor's real constitutional red line. He wants to protect the ability to transact without permission — even if the transaction is an Ordinal inscription he personally finds worthless.
I'll say this plainly: BIP-110 has become the most controversial proposal of the year because it forces a choice between two legitimate but opposed values. On one side: Bitcoin as efficient currency, clean block space, low fees. On the other side: Bitcoin as neutral permissionless ledger, accepting of all uses, no matter how wasteful.
The Ethereum comparison is instructive. EIP-4844 didn't censor data. It created a separate data layer. The problem was framed as a scalability challenge, not a moral question. Bitcoin's BIP-110 debate is framed in constitutional terms. That framing is the tell. This is not a technical conversation. It's a turf war between two visions of what Bitcoin should become.
Let's get into the numbers because this is where most commentary gets sloppy.
Let me set a baseline. Before the Ordinals wave in early 2023, average block occupancy for non-payment data was negligible. By mid-2024, inscriptions had at various points captured more than half of all block weight. That's not hypothetical — that's observable in the mempool data. BIP-110, as described, targets precisely this metadata bloat. The proposal would restrict data-carrying outputs, effectively pricing inscription activity off the base layer.
Now the economic chain: fewer data transactions means lower demand for block space. Lower demand means lower aggregate fee revenue. Lower fee revenue, at the margin, means less incentive to mine. Saylor's argument: with subsidy reduction already in progress, subtracting fee revenue from the equation is a body blow. The line he used: "Weaken the fee market and you starve Bitcoin's defenders when the network needs them most."
Gas spike detected. Run.
But this logic has a significant blind spot: fee market elasticity. Saylor's model assumes that reduced block space demand translates directly into reduced total fee revenue. That's only true if transaction volume is constant. In reality, lower fees enable more transactions. The fee pool is price-elastic. It's entirely possible — I'd argue likely — that a cleaner, cheaper block space market would attract more volume, not less.
Historical precedent? Look at 2017-2018. Fees spiked to insane levels. Volume collapsed. Look at 2020-2021. Fees were moderate. Volume grew massively. The relationship between fee rates and fee pools is non-linear and context-dependent.
Miner revenue is also more complex than Saylor frames it. The block subsidy is shrinking — that's true. Each halving cuts it by half. But mining is a competitive industry with its own economics. When subsidy falls, inefficient miners exit. Difficulty adjusts. The remaining miners — more efficient, better capitalized — often earn comparable returns. Saylor's model treats the hashrate as a pool that shrinks. In reality, it's a market that rebalances.
The real question he avoids: what is a sufficient security budget for Bitcoin? His framing implies "bigger is always better." But marginal security has diminishing returns. Beyond a certain hashrate, the cost of attacking Bitcoin becomes prohibitively high relative to any conceivable payoff. Bitcoin's current hashrate is north of 600 EH/s. The cost of renting even 1% of that momentarily is astronomical. We are past the point where security budget matters more than robustness.
Now the deeper problem with his fee-market argument: it protects incumbents, not the network.
High fees benefit existing miners. They also price out new users. Saylor's Bitcoin — base layer ultra-expensive, lightning network as the only affordable layer — is a Bitcoin that only serves whales and institutions. The grassroots growth engine that made Bitcoin globally relevant in the first place? Dead. The "digital gold" thesis works beautifully for a corporate treasury accumulating 400,000 BTC. It works less well for a merchant in Lagos or a freelancer in Manila who needs to settle a $10 payment without losing 40% to fees.
Let's talk about what Saylor isn't saying.
Strategy holds over 400,000 BTC. Purchased at an average cost that has been widely reported. At current prices, that's a massive unrealized gain. But it's also a concentration of risk that no other CEO in the world is carrying.
Every protocol change that reduces Bitcoin's scarcity premium hits Strategy's balance sheet directly. Every covenant that adds complexity introduces a risk factor that institutional investors might price. Every larger block proposal that could reduce fees per block threatens the "store of value" narrative that keeps Bitcoin at a premium over its utility value.
Saylor isn't only a Bitcoin advocate. He's also the largest single corporate bag holder in crypto. His opposition to BIP-110, covenants, and larger blocks is consistent with his balance sheet. That doesn't make him wrong. It makes him interested.
The market knows this. That's why his speech didn't move price. Because his position was already priced in. Saylor has been the "digital gold" evangelist since 2020. This is business as usual.
But here's what's unreported: BIP-110's impact would NOT harm large holders like Saylor. If anything, it would help them. Restricting block space to monetary uses increases the exclusivity of Bitcoin. It reinforces the "ultra-sound money" narrative. It pushes BRC-20 and Ordinals traders into L2s, where they'll pay fees that enrich the L2 issuers, not the L1 miners.
Wait. Why does Saylor object? Let me re-read his logic.
His objection has two parts. First, precedent. Second, principle. But there's a third part he doesn't name. BIP-110 hurts the "block space is an open resource" culture of Bitcoin. That culture is what makes Ordinals, RGB, and future use cases possible. Saylor's opposition positions him as a liberal — not a maximalist — which is surprising. He wants Bitcoin to be versatile, not restricted.
His actual position is more interesting than the headline: Don't restrict block space because that precedent can be used to restrict ANY use case. Let the market compete. If Ordinals are a fad, they'll die on their own. If they're not, they're part of Bitcoin's evolution. This is a kind of free-market Darwinism. It just doesn't fit the "digital gold" simplification.
Now the hardest technical part. Covenants.
Saylor says covenants "permanently increase consensus complexity and introduce new attack surfaces." He's right. And he's wrong.
He's right because any increase in scripting expressiveness is an increase in consensus complexity. Bitcoin's security model depends on simplicity. Every covenant proposal adds new opcodes, new constraints, new validation paths. Each of these is a potential bug. The history of Bitcoin script bugs is long. The 2010 value overflow incident, the 2012 integer overflow exploit, the 2015 CVE in OpenSSL... Every single bug caused chain reorganization. Every single one was only possible because code was complex.
But he's wrong because covenant designs have matured significantly since the early proposals. CTV (BIP-119) is deliberately minimal. It doesn't enable arbitrary smart contracts. It enables specific, bounded templates that must be committed to in advance. CAT (BIP-347) is more expressive but still bounded. The attack surface argument is real but not decisive.
The fatalism in Saylor's position bothers me more than his technical analysis. He treats covenant proposals as if they were the Ethereum merge — a radical shift in consensus rules. They're not. They're incremental, careful, and heavily scrutinized. The Bitcoin improvement process exists precisely to handle these changes.
But wait — there's a deeper point he's making that deserves respect. Bitcoin isn't a feature-maximizing protocol. It's a value-storing protocol. Every feature added to the base layer is a feature that could destabilize the base layer. If you hold 400,000 BTC, your incentive is to minimize base-layer change, period. That's not intellectual cowardice. That's rational risk management.
The conflict is structural. Developers want to expand capacity and capability. Holders want stability and scarcity. Miners want fee revenue. Users want low fees. These interests don't align. BIP-110 exposes the misalignment. Saylor has chosen a side. The market hasn't decided yet.
Uniswap V2 moved the needle. Here's how: it changed the architecture of exchange, not the rules of money. BIP-110 is a different animal. It changes the rules of what Bitcoin considers a legitimate transaction. That's a much bigger deal, and it's why the governance conflict around it feels more explosive than typical technical upgrades.
ERC-20 rush vibes. Proceed with caution.
Every governance debate has winners and losers. The BIP-110 fight is framed as Saylor vs. the Ordinals crowd. But the actual decision-makers — miners and node operators — are barely mentioned.
Miners are unusually quiet this cycle. That's suspicious. In previous rule-change battles, miners issued public signals, hashrate threats, and mining pool position statements. This time: radio silence. Why? Because BIP-110 could actually benefit them. If the soft fork reduces block space demand, fee pressure decreases — but if it concentrates legitimate demand, fees per transaction could rise. Miners are waiting to see which way the market breaks.
The second missing player: the Lightning Network. Saylor's vision of Bitcoin — a clean base layer for whales, a fee-efficient second layer for everyone else — assumes Lightning works. My previous audits of Lightning routing infrastructure have not been kind. The channel management complexity, routing failure rates, and liquidity constraints have been documented repeatedly. Seven years on, Lightning supports a fraction of Bitcoin's transaction volume. It's a solution that remains perpetually "almost ready."
If BIP-110 pushes more use cases onto Lightning and Lightning fails under load, the entire Saylor model breaks. That's the unreported risk he's not addressing.
The third missing player: institutional investors. Saylor's speech was addressed to Bitcoin holders. But the real audience is probably institutional — the 2024 ETF crowd. Institutions want stable rules. They want to know that their Bitcoin will still be Bitcoin in ten years. Saylor is providing that narrative guarantee. He's telling the market: "I will use my platform and my balance sheet to fight any rule change that threatens your investment." That's not just governance. That's marketing.
But there's a catch. Institutions also want scalability. A Bitcoin that can't process enough transactions at reasonable fees is a Bitcoin that can't serve as a global settlement layer. The ETF crowd may want stability today. They'll want capacity tomorrow. Saylor's equilibrium is unstable.
Based on my audit experience of the LUNA collapse and the 2020 DeFi governance wars, I can tell you when a public voice has a direct financial stake: every word becomes a hedging instrument.
Saylor's position is internally consistent. He believes Bitcoin is digital gold. He believes the base layer must remain neutral, scarce, and secure. He believes innovation should happen on L2s. That's a coherent philosophy.
But it's also a position that beautifully serves the financial interests of a company holding 400,000+ BTC. If Bitcoin remains a simple store of value, Strategy's treasury thesis is validated. If Bitcoin becomes a complex smart-contract platform, Strategy's competitive advantage — pure BTC exposure — is eroded. Saylor is simultaneously a true believer and the biggest beneficiary of belief.
That doesn't make him wrong. It makes him untrustworthy as a neutral arbiter.
And here's the structural problem that keeps me up at night. Bitcoin's governance has always been a messy, decentralized, human process. It has survived existential threats — the blocksize wars, the 2017 fork, the 2022 collapse. Each time, the winning side preserved Bitcoin's core value proposition while allowing enough change to keep it relevant. But the scale of stakeholders has exploded since 2017. Institutional momentum amplifies every precaution. The rulebook is no longer technical. It's legal, financial, and political.
Saylor frames the choice as "protect the constitution" versus "rewrite the rules." But that framing hides the actual risk: not change itself, but who gets to define what change is legitimate. A constitution isn't a suicide pact. It's a constraint on power. The question BIP-110 forces is whether Bitcoin's power to refuse change is stronger than its power to adapt.
BIP-110 won't activate quickly. Governance debates in Bitcoin move at the speed of consensus, which is glacial. But the conversation has shifted.
The key signals to watch: 1. Whether core developers formally engage with BIP-110 or treat it as hostile ideation. 2. Miner pool statements — especially when the next halving approaches. 3. Whether Saylor moves from commentary to action — lobbying, funding developer opposition, or public pressure campaigns. 4. The strength of the Ordinals ecosystem — if it keeps growing, BIP-110 becomes politically harder to pass.
The deeper question: can Bitcoin survive its own rulebook? The network has survived existential threats before. Each time, the winning side was the one that preserved Bitcoin's core value proposition while allowing enough change to keep it relevant.
Saylor thinks the value proposition is scarcity alone. I think he's half right. Scarcity matters. But so does adaptability. The careful rule: freeze only what absolutely must be frozen. Kill only the threats that are actual threats. A constitution isn't a suicide pact.
Bitcoin's next chapter?
Watch BIP-110. Watch the fee market. And watch the miners.
Because the biggest threat to Bitcoin was never an attacker. It's a rules committee that can't tell the difference between protection and capture.