Bitcoin’s latest governance scrap is over something most people outside the trenches barely think about: who gets to use scarce blockspace, and how much junk the network should tolerate before it pushes back.
- BIP-110 is framed as a temporary soft fork to limit arbitrary data and reduce spam, congestion, and node burden.
- Luke Dashjr says it is “too late” to cancel BIP-110.
- Michael Saylor argues Bitcoin should stay immutable, change slowly, and resist feature creep.
The dispute sits at the center of Bitcoin’s identity. Is Bitcoin a monetary network that should keep blockspace tightly focused on payments, or a neutral base layer where inscriptions, token-like experiments, and other non-financial uses can keep carving out room?
BIP-110 is designed to restrict arbitrary data in Bitcoin transactions. In plain English, that means data stored on-chain that is not needed to move bitcoin from one owner to another. The proposal aims to reduce spam, limit UTXO growth, and keep the cost of running a node from creeping higher.
That matters because blockspace is limited. Every block has room for only so much data, and every extra byte competes with something else. When the chain is stuffed with non-monetary payloads, it can raise costs for node operators and make full verification harder for ordinary users over time. That is not a theoretical purity test. It is a decentralization issue.
The proposal is also meant to be temporary. That word is doing a lot of work here. In Bitcoin, “temporary” changes are rarely treated as harmless stopgaps. They are usually read as a political signal: a short-term fix now, followed by a longer-term fight over what the rules should become later.
Luke Dashjr, a Bitcoin developer and maintainer of Bitcoin Knots, is clearly in the camp that thinks action is necessary. He rejected calls to cancel the proposal, saying:
“Saylor didn't say anything about BIP110.”
“And no, it's too late to cancel BIP110.”
He added:
“If Core gets their act together in the next year, maybe we won't need a follow-up long-term softfork.”
That tells you this is not a polite academic dispute. It is a live governance fight over whether Bitcoin should tighten its rules now to deal with data abuse, or wait for the main development path to produce something better. Dashjr’s view is blunt: the process is already moving, and turning back now is not on the table.
For non-technical readers, a soft fork is a rule change that makes Bitcoin stricter without necessarily forcing every participant to upgrade immediately. It is less disruptive than a hard fork, but it is still a big deal because it can change what the network considers valid behavior.
The technical argument behind BIP-110 is not just “we hate Ordinals.” The broader case is that arbitrary data storage competes with payments, bloats the chain, and increases validation and storage costs. The proposal’s own logic is that Bitcoin should do one thing well: move value securely, without turning into a general-purpose data dump.
There is a real case there. If blockspace becomes a free-for-all, then the costs do not disappear. They get redistributed onto node operators, wallet users, and anyone trying to verify the chain independently. Bitcoin’s credibility rests on the fact that ordinary people can run nodes and check the rules for themselves. If that gets too expensive, decentralization does not die all at once, it just gets quietly less accessible.
That is where the Bitcoin scalability issue comes in. UTXO stands for unspent transaction output, which is the basic accounting unit Bitcoin nodes track. More UTXOs and more data-heavy activity mean more storage and more work for nodes. Again, not sexy, but very real. The network does not care about your favorite narrative; it cares about what has to be stored, verified, and carried forward forever.
Michael Saylor is pushing the opposite philosophical instinct: keep Bitcoin extremely conservative about change. He argues that Bitcoin’s success depends on immutability and that protocol changes should face an incredibly high burden of proof. He said:
“Bitcoin is not a technology stock, a payments company, or a software platform competing to add features.”
“Its purpose is not to move fast and break things. Its purpose is to move slowly and not break.”
That is classic Saylor. Bitcoin, in his view, is not supposed to act like Silicon Valley software chasing feature growth and rapid iteration. It is supposed to be boring in the best possible way: stable, scarce, and hard to mess with. In Bitcoin terms, that is not cowardice. It is a feature.
There is a serious counterargument, though. If Bitcoin becomes too rigid, it can struggle to respond to new forms of abuse. That is the uncomfortable part of the debate. The same conservatism that protects Bitcoin from reckless change can also make it slower to address problems that were not obvious a few years ago. The network has to balance ossification against practical defense, and there is no clean answer that makes everyone happy.
Saylor also tied Bitcoin’s growth to capital rather than constant protocol tinkering. He said:
“The halving tightens supply. Capital flows set the growth trajectory, ”
That is a reminder that Bitcoin’s next major moves are likely to be driven as much by institutional demand and market structure as by technical upgrades. The halving is the scheduled event that cuts new bitcoin issuance, while capital flows are the big money entering or leaving the market. Saylor’s bet is that scarcity plus deep-pocketed adoption does more work than endless feature debates ever will.
He also warned about the risks of creating “paper Bitcoin” through excessive leverage. In plain terms, that means synthetic or borrowed exposure that looks like bitcoin on a screen but is not the same thing as actual on-chain ownership. That warning is not just pearl-clutching. Leverage can make markets appear stronger than they are, until they suddenly remind everyone why borrowed stability is usually fake stability.
Put together, the disagreement is bigger than one proposal and one famous Bitcoin advocate. On one side is the view that Bitcoin must defend its monetary core by limiting arbitrary data and preserving low-friction verification. On the other is the warning that every new rule, even one sold as temporary, is a precedent that can be abused later.
Both sides think they are protecting Bitcoin. The real fight is over what kind of threat matters more: too much junk in blockspace, or too much meddling with the rules in the name of cleaning it up.
Key questions and takeaways
-
What is BIP-110 trying to do?
It is meant to limit arbitrary data on Bitcoin, cut spam, reduce network congestion, and lower the burden on node operators. -
Why are Ordinals and Runes part of this fight?
They are associated with non-financial use of blockspace, which critics say crowds out payments and adds pressure to the network. -
Why do node costs matter?
If running a full node gets more expensive, fewer people can do it. That can weaken Bitcoin’s decentralization and make self-verification harder. -
Why is Luke Dashjr saying it is too late to cancel BIP-110?
He appears to view the proposal as already in motion as part of a live coordination process, not something that can simply be walked back now. -
What is Michael Saylor’s main objection to frequent Bitcoin changes?
He believes Bitcoin should stay immutable, resist feature creep, and only accept changes that clear an extremely high bar. -
What does “paper Bitcoin” mean?
It refers to synthetic or leveraged Bitcoin exposure that is not the same as direct on-chain ownership, which can distort market behavior.
The stakes are simple enough, even if the politics are messy. If Bitcoin wants to stay a hard-money network that anyone can verify, it has to keep blockspace scarce and node-running manageable. If it tolerates more arbitrary data, it needs a very good reason, because every extra rule, every extra byte, and every extra layer of financial engineering changes who gets to participate on equal footing.
Further reading
A few related pieces on the blockspace fight and the bigger Bitcoin governance fallout:
- Veteran investor slams Michael Saylor’s Bitcoin stance
- Bitcoin Improvement Proposal 444 sparks controversy over legal threats
- Bitcoin BIP-110 battles begin: onchain image inscription
- Bitcoin developer refuses to withdraw BIP-110 amid Ordinals and Runes debate
- BIP-110 soft fork sparks Bitcoin split fears as Jameson Lopp slams dangerous proposal
- Bitcoin dev Martin Habovštiak mocks BIP-110 with 66-kB blockchain image stunt
