Bitcoin's spam fight splits in two: BIP 110 vs DOG Mode

On 17 July 2026, two rival visions for handling non-financial data on Bitcoin advanced on parallel tracks, and the gap between them widened. One is BIP 110, a proposal that would change Bitcoin's consensus rules to restrict how much arbitrary data can ride inside transactions. The other is DOG Mode, a client-side filter pitched by a co-founder of the Runestone project that requires no miner vote at all.

The split is not a technicality. It is a fork in political economy: a slow, contested rewrite of the chain's rules versus a fast, opt-in redefinition of what a node will relay and accept. One path concentrates power in miners and the BIP process. The other diffuses it across anyone willing to run a different piece of software. Bitcoin's spam fight has, in effect, become a debate about who gets to define the network.

The consensus path, and why it has stalled

BIP 110 is the establishment route. To become binding, it would need broad miner signalling, a coordination mechanism the Bitcoin community has used before for soft forks. According to CoinDesk's 17 July 2026 coverage, BIP 110 has almost no miner support, a striking position for a proposal that depends on the very constituency whose blessing it requires. Without that signal, the proposal cannot activate under the standard soft-fork process, and its sponsors face the choice of either waiting out a multi-year coordination cycle or abandoning the consensus path entirely.

The technical complaint is familiar. Bitcoin's base layer has carried a growing share of inscriptions, image files, and other non-payment payloads, often via witness data and SegWit-style tricks. Critics argue this bloats the UTXO set, inflates fees for ordinary payments, and turns full-node operators into unwilling hosts for content they did not opt to store. Supporters counter that demand for blockspace is exactly what a fee-pressured chain needs, and that censoring data at the consensus layer sets a precedent for future political interference.

The impasse is procedural as much as substantive. Miner signalling reflects an economic calculation: any operator running hardware that competes on transaction fees benefits from a fuller fee market, even when that market is fed by data rather than payments. A consensus rule that throttles that demand faces a structural headwind regardless of its technical merits.

DOG Mode, and what changes if no vote is required

DOG Mode takes a different exit. Rather than rewrite what Bitcoin will accept, it changes what DOG Mode clients will relay. A node running DOG Mode filters out the kind of data-bearing transactions its operators consider noise and propagates only traffic that meets their definition of legitimate payment activity. Because the filter lives at the policy layer rather than the consensus layer, it does not require miner activation, a supermajority signal, or any change to Bitcoin's protocol rules.

The framing is ideological as much as it is technical. The proposal treats block validation and block propagation as separate problems. Miners can still include whatever transactions they wish, and earn whatever fees those transactions carry. Users running DOG Mode simply decline to relay or store the rest. If enough economic nodes adopt the filter, an empirical standard emerges without anyone having to win a vote.

The pitch, as reported by CryptoBriefing on 17 July 2026, comes from a co-founder of Runestone, an early Bitcoin-native fungible-token protocol. That positioning matters. Runestone is one of the projects that popularised non-payment use of Bitcoin blockspace; its co-founder's turn toward filtering that same activity signals that the boundary between financial and non-financial use of Bitcoin is now contested even by some of the actors who benefited from blurring it.

Two governance logics, one ledger

The deeper story is about who decides. BIP 110 concentrates the decision in a coalition: miners signalling, developers maintaining reference implementations, and the implicit veto of large pools. DOG Mode distributes the decision across anyone who runs a node and accepts the consequences: a partial eclipse of certain transactions, possibly reduced fee revenue for miners who mine into a DOG-Mode mempool, and a clearer line between what counts as payment and what counts as content.

Each path carries a different failure mode. A consensus change that fails to activate wastes years of coordination effort and leaves the underlying problem in place. A client-side filter that succeeds at scale creates a de facto two-tier network: a chain of record that includes everything miners will produce, and a propagated view of that chain that excludes what node operators will not relay. That is not a fork in the cryptographic sense, but it is a fork in the social sense. Two communities running two policies against one ledger is a familiar shape from Ethereum's post-The DAO debates and from the long tail of Bitcoin Knots versus Bitcoin Core skirmishes.

There is a counter-reading worth taking seriously. The alarm over non-payment data may be overstated. Block space remains finite, fees continue to clear the market, and any operator who finds inscriptions intolerable can already run a policy of non-relay at the margins. DOG Mode may amount to a label for what disciplined node operators were already doing, formalised into a single client. On that reading, the most consequential thing about the proposal is not what it filters but the precedent it sets: contentious policy decisions migrating from consensus governance to client-side defaults.

What to watch next

Three indicators will tell whether DOG Mode is a realignment or a press release. First, the share of economically relevant nodes adopting the filter, observable through their mempool composition and peer behaviour. Second, miner response: if pools begin producing blocks that prioritise DOG-Mode-compatible transactions for fee reasons, the filter has crossed from policy into market structure. Third, whether BIP 110's sponsors treat DOG Mode as a substitute, a rival, or a complementary track, and whether their supporters can be reconciled behind a single answer.

The sources do not specify miner adoption figures for DOG Mode, the size of the Runestone co-founder's platform reach, or whether any major pool has publicly responded to the proposal. Those gaps are themselves part of the story: a governance moment unfolding faster than the data infrastructure to track it.

How Monexus framed this: the wire coverage treated DOG Mode as a technical rebuttal to BIP 110; Monexus reads the proposal as a governance event with market-structure consequences, and surfaces the Runestone co-founder's positioning because the actors behind a filter determine what it filters.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/CryptoBriefing