Bitcoin spam fight escalates as Dashjr backs BIP-110
Bitcoin’s latest fight is not about price, ETFs, or whether a random chart line can predict the next moonshot. It is about block space. Should Bitcoin keep accepting arbitrary on-chain data, or should it tighten the rules and push the network back toward payments first?
- BIP-110 is a temporary softfork proposal that limits certain kinds of on-chain data.
- Luke Dashjr is standing behind it despite criticism and calls to drop it.
- Ordinals and Runes sit at the center of the controversy over block space.
- The real dispute is simple: money network only, or neutral block space for anyone willing to pay?
At the center of the dispute is BIP-110, also called the Reduced Data Temporary Softfork. The proposal is meant to place temporary limits on certain forms of arbitrary data in Bitcoin transactions. Its supporters want the network to stay focused on what they see as Bitcoin’s core role, money, not a permanent storage layer for extra payloads.
That sounds simple until you remember Bitcoin governance is never just technical. Every rule change turns into a fight over values, incentives, and who gets to decide what “spam” even means. In Bitcoin, the politics are part of the protocol whether people like it or not.
The official BIP-110: Proposed Restrictions on Bitcoin Data Embedding page says the new rules would apply only to UTXOs created at or after activation, while older UTXOs would remain exempt. A UTXO, or Unspent Transaction Output, is spendable bitcoin waiting to be used in a future transaction. That detail matters because the proposal is aimed at future behavior without invalidating existing funds.
The proposal is broader than a simple anti-Ordinals complaint. According to the official BIP-110 text, it restricts several data-heavy paths, including smaller output limits, tighter OP_RETURN rules, caps on data pushes in scripts, limits on Taproot witness data, and restrictions on certain Tapscript behavior. In plain English: it is trying to make it harder to use Bitcoin like a cheap, permanent data dumpster.
Supporters argue that this is exactly the point. Bitcoin block space is scarce, and if it gets filled with non-financial data, ordinary transactions have to compete with inscriptions, token experiments, and whatever other byte-packed nonsense people decide to inscribe forever. The chain does not care whether the data is art, collectibles, or a meme with delusions of grandeur. It just counts bytes and charges fees.
There is a real argument behind that position. Data-heavy activity can increase storage demands, raise the burden on nodes, and make Bitcoin less focused on peer-to-peer payments. For maximalists, that is the whole ballgame. Bitcoin should do one thing and do it well.
Critics are not exactly wrong either. Their case is blunt: if users are paying the fee, why should anyone get to decide what kind of data they are allowed to put on-chain? From that angle, restrictions on arbitrary data look less like protection and more like a slippery slope toward content-based gatekeeping dressed up as technical stewardship.
That tension is the entire fight. Is Bitcoin a neutral settlement network where the highest fee wins block space, or a monetary system that should actively prioritize payments over everything else? Those are not the same thing, and Bitcoin’s current argument is what happens when people stop pretending they are.
Luke Dashjr has made it clear he is not backing away. The reported position is that he rejected calls to withdraw BIP-110 and remains firm behind it. In quotes cited in the material, Dashjr said:
“Saylor didn’t say anything about BIP110.”
“And no, it’s too late to cancel BIP110.”
Those lines are sharp, but the real story is governance, not the one-liner. Bitcoin does not run on swagger. It runs on adoption, which means miners, node operators, users, wallets, and businesses all deciding which rules they will actually enforce.
That is why activation details matter so much. The materials tied to BIP-110 describe it as a User-Activated Soft Fork, or UASF, with a flag day around August 2026. They also describe a miner fast-track path if 55% of blocks in a difficulty period signal support, 1, 109 out of 2, 016 blocks. The reference implementation cited is BIP-110 update: v0.4.1 release and implementation, while Bitcoin Core has not endorsed the proposal.
That means BIP-110 is still in an uncertain, early phase. It is not a done deal, and it is nowhere near universal consent. In Bitcoin terms, that is not a footnote. That is the whole battle.
The available signaling data also suggests the proposal is nowhere near a slam dunk. As described in the materials, early support has been very low, with only around 2-3% of daily blocks signaling. That is not the kind of number that screams “the network has spoken.” It screams “the argument has barely started.”
The official rationale for BIP-110 is not irrational. It argues that data storage competes with payments, increases costs for regular users, and can make Bitcoin more reliant on third parties. It also says reducing large data vectors helps keep node operation cheaper, which in theory supports decentralization.
That is classic Bitcoin logic. If block space gets clogged with arbitrary payloads, ordinary money transfers can get priced out. A block full of JPEG-shaped junk is still a block, and the chain does not care about your ideological purity when fees are due.
But the counterargument has teeth. Once consensus rules start judging which bytes are “acceptable, ” the network stops being purely neutral and starts making editorial choices. Maybe that is necessary. Maybe it is a very expensive way to invite future fights over who gets to define “legitimate” use.
Ordinals and Runes are the flashpoints, but the debate goes beyond either one. Ordinals are inscriptions of data attached to satoshis, while Runes are a Bitcoin-native token system used for issuing and transferring digital commodities through Bitcoin transactions. Together they turned Bitcoin block space into a battleground over whether the chain should serve only monetary transfers or also tolerate broader forms of on-chain expression and speculation.
That matters because Ordinals and Runes are no longer just theoretical annoyances. They have become part of Bitcoin’s fee market, which is exactly why this debate keeps getting louder. Fee markets are supposed to be brutally simple: pay up, get in. But Bitcoin also has a culture, and that culture has always been suspicious of turning scarce block space into a landfill for permanent data.
The wider market backdrop has only sharpened the argument. The materials note that Bitcoin has been under pressure near $64, 000, with ETF outflows and macro risks weighing on traders. They also point to renewed discussion around Michael Saylor’s view that Bitcoin scalability is not about turning the network into a feature soup, but about preserving the base layer’s monetary purpose.
Saylor’s quoted line fits the conservative side of this fight:
“Its purpose is not to move fast and break things. Its purpose is to move slowly and not break, ”
That framing captures the case for restraint. Don’t turn Bitcoin into a bloated feature parade. But weaker market conditions also tend to make internal governance fights more intense, because every technical dispute starts to look like a referendum on Bitcoin’s identity. Suddenly a proposal about data rules turns into a proxy war over who still “understands” the network.
The real risk is not just whether BIP-110 passes. It is what kind of precedent it sets. If the proposal gains traction, it could encourage more aggressive content restrictions at the consensus level. If it fails, Bitcoin keeps its current, more permissive posture where block space remains open to anyone willing to pay.
Either way, the network is being forced to answer a question it keeps circling without ever neatly settling it: is Bitcoin a money system that should defend its purpose, or a neutral ledger that should not care what people pay to write into it? That answer will shape fee markets, node policy, and the limits of Bitcoin governance for years to come.
Key questions and takeaways
-
What is BIP-110 trying to do?
It is a temporary softfork proposal that would restrict certain forms of arbitrary on-chain data and push Bitcoin back toward a payments-first design. -
Why is block space the center of the fight?
Bitcoin block space is limited, so every extra byte used for data-heavy activity competes directly with ordinary transactions. -
Does BIP-110 only target Ordinals?
No. The proposal is broader and affects several technical paths for embedding data, not just inscriptions. -
Why does the UTXO detail matter?
It means the new rules would apply only to outputs created after activation, while older outputs stay valid. That reduces the risk of breaking existing funds. -
Is BIP-110 guaranteed to activate?
No. The available signaling is still weak, and the outcome depends on miners, node operators, users, and broader economic support. -
What is the core philosophical split?
One side wants Bitcoin to prioritize money and reduce non-financial data use. The other side says block space should stay open to anyone who pays the fee, even if the use case is unpopular. -
Why does this debate matter beyond spam complaints?
Because it could shape future Bitcoin governance, fee market behavior, and whether consensus rules stay permissive or start drawing harder lines around acceptable use.
Bitcoin’s technical battles are rarely just technical. This one is about scarcity, governance, and the awkward fact that decentralization still has to make decisions. The network can tolerate a lot, but it cannot avoid choosing what it is for forever.
Further reading
A few closely related takes and follow-ups worth a look:
- Bitcoin spam fight escalates as Dashjr backs BIP-110
- Reuters report on Strategy’s valuation falling below its Bitcoin holdings
- BIP-110 soft fork sparks split fears as Jameson Lopp slams the proposal
- Bitcoin BIP-110 debate: Saylor warns of protocol risks amid community split
- Bitcoin dev Martin Habovštiak mocks BIP-110 with 66-KB blockchain image stunt
