Imagine waking up to find that the very protocol you've been betting your hard-earned capital on is about to be rewritten—not by a hack or a hostile takeover, but by a seemingly harmless soft fork disguised as a security upgrade. That's the reality Bitcoin holders woke up to on July 19, 2026, when BIP 110 burst onto the scene, sparking a firestorm that pits Bitcoin's most vocal institutional advocate, Michael Saylor, against a pack of core developers who believe they know what's best for the network.
This isn't just a technical squabble over script size limits or witness version rules. It's a philosophical war over the very soul of Bitcoin: should it remain a neutral, immutable store of value, or should it be permitted to evolve—and potentially risk its core promise—in the name of scalability and lower fees? Saylor, the executive chairman of MicroStrategy, didn't mince words. He called BIP 110 a "crude proxy for an unmeasured cost" and accused its authors of violating Bitcoin's sacred principle of neutrality. His intervention, as we'll see, is the single most important factor that could determine whether this proposal dies a quiet death or becomes the most consequential (and divisive) upgrade in Bitcoin's history.
But before we dive into the drama, let's set the stage. BIP 110 is a proposed soft fork that aims to limit the size of script data in Bitcoin transactions. Its stated goal is to reduce the risk of denial-of-service (DoS) attacks and curb blockchain bloat caused by prolific data embedding. To the uninitiated, this sounds reasonable. Who wouldn't want a more efficient, more secure Bitcoin? However, the devil is in the details—and in the hidden trade-offs.
Context: Why Now?
The proposal surfaces at a time when Bitcoin's transaction fees are already at historic lows. The network is not congested, and ordinary users are not complaining about cost. Yet, a subset of developers—those who favor a more conservative, “store-of-value” vision for Bitcoin—argue that the current lack of fee pressure is an illusion. They fear that once Ordinals, BRC-20 tokens, and other data-heavy experiments gain traction, miners could be incentivized to fill blocks with cheap, bloated transactions, driving up historical data storage costs for full nodes. BIP 110, they claim, is a preemptive strike: a way to lock in low-fee usage before the problem becomes unmanageable.
But here’s the kicker: the rationale is built on a hypothesis that has never been convincingly measured. As Saylor pointed out, BIP 110 is a “solution in search of a problem.” It’s targeting a cost that the network has never actually paid, and it does so by imposing arbitrary limits that could close the door on future innovation—specifically, on technologies like BitVM, which promises to bring Turing-complete computation to Bitcoin without changing the base layer.
Core: Inside BIP 110’s Technical Machinery—and Its Hidden Dangers
To understand why this is a big deal, we need to unpack the proposal’s technical contents. BIP 110 bundles several restrictions into a single package. First, it caps the total size of script data per transaction to 400 bytes (excluding the output amount and taproot control block). Second, it introduces the concept of “undefined witness versions”—any new witness version that’s not yet defined by the protocol would be rejected unless explicitly whitelisted by a future soft fork. Third, it tightens the rules around Taproot script path spending, effectively limiting how complex future smart contracts can be.
On the surface, these changes seem incremental. But their cumulative effect is profound. By limiting script data, BIP 110 makes it harder for users to embed arbitrary data (like NFTs or token metadata) on-chain. More importantly, by restricting witness version flexibility, it decapitates any future upgrade that relies on new witness versions—including BitVM, which could theoretically use a specialized witness version to prove computations. In effect, BIP 110 is a “kill switch” for Bitcoin’s programmability aspirations.
Let’s consider the numbers. A single Bitcoin block has a maximum weight of 4 million weight units (WU). Script data, under current rules, can account for only a fraction of that due to the existing block size limits. Yet, BIP 110’s proponents argue that even this small fraction could be weaponized by attackers. But data from the past year shows that script data usage has never exceeded 5% of block capacity. The proposed cap of 400 bytes per input (or output) is so low that it would effectively ban almost all existing Ordinal inscriptions, which often exceed 1,000 bytes. Imagine if a government suddenly banned all packages over a certain size—would that make the postal service more efficient, or would it merely kill it?
The Contrarian Angle: Is Saylor Playing Defense for His Own Bag?
Saylor positions himself as the guardian of Bitcoin’s neutrality. But let’s consider a less flattering interpretation. MicroStrategy holds over 200,000 BTC. Any proposal that threatens Bitcoin’s long-term stability—or introduces uncertainty—is a direct threat to his personal wealth and his company’s balance sheet. If BIP 110 passes and later proves to be a mistake, Bitcoin’s price could suffer, and MicroStrategy’s massive collateral could be jeopardized. This is not pure altruism; it’s rational self-interest dressed up as principled objection.
Moreover, Saylor’s preferred alternative—a market-driven approach with voluntary relay policies and variable transaction fees—sounds noble but fails to address the root cause of perceived DoS risk. The market is already working: miners prioritize high-fee transactions, and low-fee spam is naturally excluded. Why fix what isn’t broken?
The Takeaway: What Happens Next?
BIP 110 has a built-in sunset clause: if it’s not activated within one year, it expires. Given the fierce opposition from Saylor and the lack of consensus among core developers (Adam Back predicted it would “stagnate in weeks”), the proposal’s fate seems sealed. But even if it dies, the debate leaves scars. The low activation threshold of 55% miner signaling—far below the traditional 95%—sets a dangerous precedent. Future proposals with similarly aggressive thresholds could attempt to ram through changes without community buy-in, fragmenting the network.
My advice? Don’t panic sell. But do pay attention. Follow the miner signaling on the latest chain data (look at BIP 110’s activation flag). If signal reaches 30%, the proposal may gain momentum, and we’ll need a broader community pushback. Until then, treat this as a stress test of Bitcoin’s governance—one that it’s likely to pass, but not without leaving permanent scars.
As for the “unrealistic profits” narrative—yes, Bitcoin is still the hardest asset, but its true value lies in its neutrality and its ability to evolve without sacrificing its core. BIP 110 threatens that. The next few months will tell us whether Bitcoin’s community can stand its ground.
