A fistfight is brewing in the digital town square. On one side, you have developers and purists who claim the network is being choked to death by digital garbage—JPEGs, audio files, and memes clogging up the world’s most pristine monetary ledger. On the other, you have cypherpunk veterans accusing the clean-up crew of staging a “lynch mob” that could burn the whole house down. At the center of this storm is BIP-110, and depending on who you ask, it’s either a necessary emergency brake or a reckless act of sabotage that threatens Bitcoin’s credibility as a store of value.

What is BIP-110 and Why Was It Proposed?

Introduced in December 2025 by a developer known as Dathon Ohm, with strong backing from Bitcoin Knots maintainer Luke Dashjr, BIP-110 is technically a temporary soft fork. In plain English, it’s a proposal to put a strict diet on the amount of data a single Bitcoin transaction can carry for one year. The primary targets are Ordinals inscriptions and BRC-20 tokens—the ability to embed images, videos, and arbitrary data directly onto the blockchain.

The proposal sets specific limits: transaction output data is capped at 34 bytes, OP_RETURN (a common data carrier) is limited to 83 bytes, and inscriptions using the SegWit protocol are restricted to 256 bytes. The rationale is simple: spam. Since a controversial update to Bitcoin Core v30 in October 2025 removed the long-standing 80-byte limit on OP_RETURN, the door was effectively kicked open for non-financial data to flood the network.

Supporters argue this “data bloat” increases the hardware requirements for running a node. If running a node becomes too expensive for the average user, we lose decentralization. And if we lose decentralization, we lose Bitcoin. Researcher Matthew Kratter painted a grim picture, comparing the spam to a parasitic plant: “It’s like one of those parasitic plants… that completely covers a tree, consuming it and destroying its internal structure. The ivy itself also dies. That’s what spam can do to bitcoin”.

The Heavyweight Opposition: Adam Back’s “Lynch Mob”

If Luke Dashjr is the spiritual leader of the anti-spam crusade, then Adam Back, the CEO of Blockstream and a figure cited in the original Bitcoin whitepaper, is the general of the opposition. And he is not holding back.

Back’s critique isn’t about the existence of spam; it’s about the method of removing it. He views tampering with consensus rules to police content—even annoying content—as a dangerous precedent. On February 15, he took to X (formerly Twitter) to unload on the proposal.

“It’s worse as it is an attack on bitcoin’s credibility as a store of value, its security credibility, and a lynch mob attempt to push changes there is not consensus for,” Back warned. He argues that spam is merely “an annoyance,” not a security threat, and that “it all definitionally fits within the block-size”.

Back’s core fear is that the “cure” is worse than the disease. He points out that the proposed changes risk “freezing UTXOs” (unspent transaction outputs), essentially making users’ funds unspendable, and breaking existing functionality for regular users. For him, Bitcoin’s strength lies in its permissionless, censorship-resistant nature. “permissionless censorship-resistant, decentralized systems are hard to censor. by design. bip110 doesn’t change that, it is reckless and breaks multiple things for regular users,” he posted, underscoring that the system should remain neutral to whatever data users want to attach, as long as they pay the fee.

The Battle Lines Are Drawn

The numbers tell the story of a deeply fractured community. Data from late January shows that only about 3% to 7.5% of Bitcoin nodes are currently signaling support for BIP-110—far below the 55% threshold required for activation. Notably, none of the top 20 mining pools have expressed interest.

However, the political landscape is shifting. The debate has caused a massive migration in node software. Bitcoin Core’s dominance has slipped from nearly 98% to about 77.2% , while the more conservative Bitcoin Knots (which implements stricter data limits) has surged to over 22% market share. This is the digital equivalent of voters switching parties.

Proponents of BIP-110, like Luke Dashjr, maintain that arbitrary data embedding “creates additional strain on node operators and diverts resources from the ‘real mission’ of the first cryptocurrency—improving the financial system”. They see the influx of memes and tokens as an exploitation of a bug (CVE-2023-50428) that was never intended to be used this way.

On the other side, advocates for the Ordinals ecosystem argue they are securing the network by paying massive fees—over $500 million in transaction fees have been attributed to this activity, a crucial buffer as block subsidies dwindle. They view the proposal not as a technical fix, but as a puritanical attack on how they choose to use the block space they paid for.

Summary: A Fight for the Soul of Bitcoin

In my experience covering these cycles of technological angst, this isn’t really about bytes or OP_RETURN limits. It’s about identity. BIP-110 has become a proxy war for the ultimate question: What is Bitcoin for?

Is it a rigid, immutable financial settlement network, where every kilobyte should be optimized for monetary transactions? Or is it a neutral, permissionless space where anyone can inscribe anything, as long as they can pay the miner fee?

Adam Back fears that forcing through a contentious soft fork with “mob” tactics destroys the social consensus that keeps Bitcoin secure. The BIP-110 supporters fear that doing nothing allows the network to slowly asphyxiate under the weight of JPEGs, pricing out the very home users who make it decentralized.

The current lack of miner support suggests BIP-110 is likely dead in the water for now. But the surge in Bitcoin Knots adoption tells me the sentiment isn’t going away. Whether it’s this BIP or the next, the community will have to eventually reconcile these two visions. Until then, the “annoyance” of spam and the “attack” of fixing it will continue to be two sides of the same, very volatile, coin.

What are your thoughts?