Bitcoin’s spam problem is heating up, and developer Luke Dashjr just made it clear: there’s no backing down from BIP-110. On July 6, 2026, Dashjr firmly stated that calls to cancel the Bitcoin spam proposal were too late. This statement has reignited one of the most important debates in cryptocurrency—what should Bitcoin actually do?
BIP-110 is a temporary proposal designed to fight what many call “spam” on the Bitcoin network. The proposal would restrict how much arbitrary data can be stored on Bitcoin’s blockchain. But here’s the problem: not everyone agrees this is spam. Some users love Ordinals and Runes—technologies that let people store digital art and create tokens on Bitcoin. To them, restricting this data isn’t fixing a problem; it’s censorship.
What Is BIP-110? A Clear Explanation
BIP-110 stands for Bitcoin Improvement Proposal 110. In simple terms, it’s a suggested rule change for how Bitcoin handles data. The proposal would limit the size of data that can be embedded in Bitcoin transactions, with some exceptions.
How BIP-110 Would Work
Here’s what BIP-110 would actually do:
BIP-110 would cap new output sizes at 34 bytes (except for OP_RETURN outputs, which could be up to 83 bytes). This means new data chunks couldn’t be as large as they are today. The proposal would also limit how much data can be pushed into a single transaction to a maximum of 256 bytes.
One important feature: BIP-110 includes grandfathering protections. This means Bitcoin stored before the rule change would still work under the old rules. Your existing Bitcoin UTXO wouldn’t be frozen or made unspendable. This is crucial because it prevents what many feared most—coins becoming locked up and unusable.
Why Would Bitcoin Need This Rule?
Bitcoin nodes need to store something called the UTXO set. This is a database of all unspent Bitcoin transactions. As more data gets embedded in Bitcoin transactions, this database grows larger. Larger databases cost more money to store and maintain. This drives up the costs for people who run Bitcoin nodes.
Higher node operating costs can reduce decentralization. If running a node becomes too expensive, fewer people will do it. Fewer nodes means less security and more power in fewer hands. BIP-110 supporters argue that limiting data storage protects Bitcoin’s decentralization by keeping these costs manageable.
The Bitcoin Spam Debate: Two Sides Explained
What BIP-110 Supporters Believe
Supporters of BIP-110 argue that Bitcoin has a genuine spam problem. They point to data showing that Ordinals and Runes consume massive amounts of block space—sometimes 35 to 45 percent or more of available transaction room.
When Bitcoin’s block space gets filled with data storage, regular Bitcoin users pay higher fees to send actual money. If you want to transfer value using Bitcoin, you’re competing against people willing to pay premium fees just to inscribe digital images or create tokens. For BIP-110 supporters, this isn’t Bitcoin working as designed—it’s Bitcoin being hijacked for non-monetary purposes.
The philosophy here is clear: Bitcoin should prioritize being sound money, not a data storage service. There are other ways to store data permanently online. Bitcoin should stay focused on what it does best: enabling peer-to-peer payments and preserving wealth.
Research from analysts has quantified the problem. Their data suggests that spam transactions frequently consume over one-third of Bitcoin’s block space. Simulations show that BIP-110 could reclaim significant block space without disrupting legitimate Bitcoin payments at all. This evidence forms the backbone of the bitcoin spam fight.
What BIP-110 Critics Believe
Critics see BIP-110 very differently. They argue that Bitcoin’s core strength is permissionlessness—the idea that anyone can use Bitcoin however they want, as long as they follow the rules and pay fees.
From this perspective, defining what counts as “spam” is subjective. Who decides? Today it’s Ordinals. Tomorrow it might be privacy transactions or lightning channels or something else that someone disagrees with. Once Bitcoin starts restricting certain transaction types, where does it stop?
Jameson Lopp, a respected Bitcoin developer, has raised serious concerns. He worries that activating BIP-110 without broad agreement could cause a chain split—essentially breaking Bitcoin into two competing networks. Users and exchanges would have to pick which one is the “real” Bitcoin. This would be catastrophic for Bitcoin’s value and credibility.
Lopp also points out that Ordinals and Runes generate substantial transaction fees. As Bitcoin’s block subsidy continues declining toward zero, these fees become increasingly important for miner security incentives. Restricting the activity that generates these fees could actually harm Bitcoin’s long-term security.
The Open Blockspace Argument
The “open blockspace” philosophy says Bitcoin should remain completely neutral about transaction content. If a user wants to broadcast a valid transaction and pays the market fee, the network should accept it without judgment. This neutrality is what makes Bitcoin truly permissionless and censorship-resistant.
Critics also question whether BIP-110 would even work. Determined actors could use steganographic techniques—hiding data within other data—to circumvent the restrictions. The proposal might solve nothing while creating significant governance risks.
Luke Dashjr’s Firm Stance on BIP-110
Luke Dashjr is no minor figure in Bitcoin development. He’s the maintainer of Bitcoin Knots, a popular alternative Bitcoin client software that many users and operators prefer. When Dashjr takes a position, it matters.
What Dashjr Said
In July 2026, when critics suggested BIP-110 should be canceled, Dashjr responded directly: “And no, it’s too late to cancel BIP110.” This wasn’t a tentative maybe. It was a flat refusal to walk back the proposal.
Dashjr framed his position partly as a response to Michael Saylor‘s recent statement that Bitcoin should “move slowly and not break things.” Interestingly, **Dashjr interpreted this principle as actually supporting BIP-110**, since the proposal is temporary and limited in scope. It “moves slowly” with conservative changes and includes protections for existing Bitcoin holders.
Why Dashjr’s Support Matters
Dashjr’s role as Bitcoin Knots maintainer gives his technical opinions significant weight. Bitcoin Knots is used by mining pools, node operators, and serious Bitcoin users who want conservative software. By backing BIP-110, Dashjr signals that Bitcoin Knots could support and implement the proposal if it moves forward.
This technical support is important in Bitcoin governance. Software implementations function as proxies for what users and operators actually want. If Bitcoin Knots actively supports BIP-110, that strengthens the proposal’s chances of activation.
Dashjr’s statement also reveals something important about BIP-110 proponents’ thinking. They seem to view the activation window as their moment of maximum leverage. Dashjr even suggested that if Bitcoin Core developers address spam concerns through other methods within the next year, maybe a permanent long-term softfork won’t be necessary. This implies a threat: if the broader development community doesn’t act, consensus-level restrictions will become permanent.
How Would BIP-110 Activate? Understanding the Mechanism
The Role of Miners and Nodes
Bitcoin’s upgrade process normally requires agreement between three groups: miners, developers, and nodes. Miners select which transactions to include in blocks. Developers write and review code. Nodes validate all transactions according to the rules.
BIP-110 would require 55% miner signaling to activate through a User-Activated Soft Fork (UASF). This is actually a relatively low threshold. However, current miner signaling for BIP-110 remains weak. Why? Miners profit directly from transaction fees, regardless of the transaction source. Higher fees from spam transactions mean more revenue for miners. So miners have little incentive to restrict the activity that pays them.
The UASF Controversy
A User-Activated Soft Fork is a special activation mechanism. It allows a determined majority of node operators to force a rule change even without miner support. This sounds democratic in theory. In practice, it raises serious concerns.
Adam Back, CEO of Blockstream and a prominent Bitcoin figure, explicitly warned that forcing BIP-110 through via UASF without broad ecosystem consensus could create a contentious fork. A contentious fork means Bitcoin splits into two competing chains. Users would face confusion. Exchanges would struggle to handle both chains. Bitcoin’s credibility would suffer severely.
This didn’t happen with previous successful upgrades like SegWit. SegWit succeeded because it achieved genuine consensus. Miners, developers, and the community all agreed it was good for Bitcoin. BIP-110 doesn’t have that broad agreement, which makes the activation mechanism much riskier.
Ordinals and Runes: The Technologies at the Center
Understanding BIP-110 requires understanding what it’s actually targeting: Ordinals and Runes.
What Are Ordinals?
Ordinals emerged in early 2023 as a protocol for inscribing data onto individual satoshis. A satoshi is the smallest Bitcoin unit (one-hundred-millionth of a Bitcoin). Ordinals let users inscribe digital art, text, and other content directly onto these satoshis, making the data permanently part of Bitcoin’s blockchain.
The Ordinals ecosystem exploded in popularity. Artists created collections. Trading platforms emerged. Communities formed around Ordinals art. From a cultural and economic perspective, Ordinals generated genuine activity with real value to participants.
From BIP-110 supporters’ perspective, however, Ordinals represent wasteful data storage. They consume valuable block space for purposes—making digital art permanent—that could be served by other systems outside Bitcoin. This consumes space that could be used for actual Bitcoin transactions.
What Are Runes?
Runes are a more recent Bitcoin-native token system. Unlike Ordinals, which are relatively static once inscribed, Runes enable token minting, transfer, and burning through Bitcoin transactions. This creates a dynamic ecosystem for on-chain digital assets. Runes are more efficient than some earlier token protocols, but they still consume block space. They generate transaction fees, so miners like them. But from a Bitcoin maximalist perspective, they’re another example of Bitcoin being used for purposes beyond peer-to-peer money transfer.
The Impact on Bitcoin’s Fee Market
Here’s the real tension: Both Ordinals and Runes generate substantial transaction fees. This fee revenue matters for Bitcoin’s security model. As the block subsidy (the new Bitcoin miners receive) continues declining, transaction fees become increasingly important to keep miners incentivized. Restricting Ordinals and Runes activity could reduce the Bitcoin fee market, ultimately harming miner incentives and potentially Bitcoin’s security budget. This is why miners aren’t enthusiastically supporting BIP-110 despite claims that it solves a real problem.
The Governance Challenge: Can Bitcoin Govern Itself?
The Core Problem: Defining “Spam”
At the deepest level, BIP-110 raises a fundamental question: Who decides what counts as spam? One person’s spam is another person’s legitimate use. Ordinals artists say their work is legitimate. Token creators say Runes are legitimate. BIP-110 supporters say both are spam clogging the network.
The danger is clear: if Bitcoin creates consensus rules that restrict certain transaction types, the principle is established for future restrictions. Today you restrict Ordinals. Tomorrow, someone with a majority votes to restrict privacy transactions. The day after, restrictions on lightning channels pass. Where does it stop? This represents a fundamental departure from Bitcoin’s permissionless design.
Chain Split Risks
Adam Back’s warning about contentious forks deserves serious consideration. A chain split would be devastating for Bitcoin. Users would face confusion. Some exchanges might support one chain while others support another. Bitcoin’s market price would likely crash. The whole proposition of Bitcoin as reliable money would be compromised.
Previous successful Bitcoin upgrades like SegWit didn’t carry these risks because they achieved genuine consensus beforehand. BIP-110 hasn’t achieved that consensus, making activation via UASF significantly more dangerous.
Alternative Approaches
Some argue Bitcoin could address spam concerns without consensus-level restrictions. Options include: Node-level filtering would let individual node operators reject certain transaction types without forcing everyone else to do so. This respects Bitcoin’s permissionlessness while allowing operators to customize their experience. Fee market mechanisms naturally discourage unwanted activity. If the community views certain transactions as spam, users simply won’t pay high fees for them. The fee market self-corrects.
Policy solutions could involve agreements among exchanges and wallet providers to handle Ordinals and Runes differently, without changing Bitcoin’s core rules. These approaches preserve Bitcoin’s fundamental design principles while addressing practical concerns. What Happens Next: Three Possible Scenarios
Smooth Activation with Community Support
In this scenario, BIP-110 gains broad ecosystem support. Node operators, exchanges, and the broader community recognize the spam problem as serious enough to warrant action. Miner signaling improves. The proposal activates with minimal friction.
The temporary nature of BIP-110 (one year, with possibility of extension) and its backward-compatibility design allow skeptical users to coexist peacefully. Opponents work on solving the underlying issues during this period. This scenario requires the Bitcoin spam problem to be serious enough that ecosystem actors prioritize it over other concerns. Current weak miner signaling suggests this is unlikely, but community sentiment could shift.
Contentious Fork and Network Split
In this scenario, BIP-110 proponents push for activation despite weak support. They activate via UASF mechanics, forcing the rule change without broad miner backing or community consensus.
This triggers a chain split. Bitcoin divides into two competing networks. Users and exchanges face pressure to choose which is the “real Bitcoin.” Confusion and uncertainty tank Bitcoin’s price. Adoption slows. The cryptocurrency loses credibility. This scenario represents an existential threat to Bitcoin and would be catastrophic for everyone invested in Bitcoin’s success. Adam Back’s warnings are specifically about preventing this outcome.
Community Recognizes the Risks
In this scenario, the Bitcoin community steps back and reconsiders. Developers, miners, and users recognize that consensus-level data restrictions introduce more problems than they solve. The risks of chain splits and damaged governance processes outweigh the benefits of fighting spam. The community shifts focus to node-level filtering, fee market mechanisms, and other approaches that address spam without compromising Bitcoin’s fundamental design. Bitcoin’s governance processes evolve to better balance innovation and preservation.
Key Takeaways: What This Debate Means for You
If you use Bitcoin, this debate affects you directly. Here’s what matters: BIP-110 could reduce Bitcoin transaction fees if it activates. With more block space devoted to actual payments, fees might fall. But this benefit only materializes if the proposal actually eliminates spam—which critics question. Your Bitcoin wouldn’t be frozen or lost. The grandfathering protections ensure existing Bitcoin remains fully spendable. But if BIP-110 activates before you move coins created after activation, those coins might face restrictions when spending.
Bitcoin’s governance could be damaged if this isn’t handled carefully. A contentious fork would harm Bitcoin’s credibility for years. Even if avoided, forcing changes without consensus could undermine confidence in Bitcoin as neutral money. The broader principle matters more than this specific proposal. This debate is ultimately about whether Bitcoin remains permissionless and neutral, or whether majority coalitions can restrict transaction types they dislike. That principle shapes Bitcoin’s future far more than any single spam problem.
Conclusion
Luke Dashjr’s firm backing of BIP-110 marks a critical moment in Bitcoin’s identity debate. The proposal itself represents a serious attempt to address real concerns about network bloat and growing node operating costs. Dashjr’s technical credibility ensures BIP-110 receives serious consideration as a potential upgrade path.
Yet enthusiasm from BIP-110’s core supporters stands in stark contrast to weak miner signaling, lack of broad community consensus, and serious warnings from respected figures like Adam Back about chain fork risks. The proposal’s temporary, limited-scope design shows genuine effort to balance innovation with preservation. However, activating consensus rule changes via UASF mechanisms without broad backing introduces dangers that may exceed the problems it solves.
The bitcoin spam fight ultimately reflects a community learning to govern itself through decentralized processes. This debate will continue shaping how Bitcoin evolves, whether the network accommodates both monetary and data-heavy use cases, and how seriously the community takes permissionlessness versus focused design.
For Bitcoin users, holders, and participants, staying informed about BIP-110’s development and understanding both technical and philosophical dimensions represents essential due diligence. The outcome affects not only transaction costs and network capacity but Bitcoin’s fundamental nature as sound money and how the network will be governed for years to come.
