Leonidas Unveils Bitcoin DOG Mode to Ease Relay Rules

Leonidas shared the news on X early Friday. The $DOG Army project targets policy filters, not Bitcoin’s consensus rules. So no fork is needed.

What Bitcoin DOG Mode Changes

DOG Mode proposes two narrow changes. Importantly, both affect relay policy, also called standardness. Neither changes the consensus rules that determine whether a block is valid.

First, DOG Mode would raise the standard transaction size limit. Today, most nodes cap standard transactions at 400,000 weight units. Under the proposal, however, that ceiling would increase to 3,900,000 weight units.

As a result, the client could relay near-4MB transactions, which supporters call “four meggers.” At the same time, the proposal leaves roughly 100,000 weight units of headroom for coinbase data and other overhead.

Second, DOG Mode would reduce the dust limit to 1 satoshi. Currently, nodes reject tiny outputs below roughly 294 to 546 sats, depending on the output type. Therefore, the change would allow much smaller outputs to circulate through the public relay network.

Relay Rules Are Not Consensus Rules

The distinction matters because consensus rules act as Bitcoin’s mandatory laws. Every node and miner must enforce them. Otherwise, the network rejects the block.

Standardness rules work differently. Instead, they function as optional defaults that determine which transactions a node accepts into its mempool and relays to peers.

Therefore, a transaction can remain fully valid under Bitcoin’s consensus rules while still being classified as non-standard. Miners can include it in a block, but most nodes may refuse to relay it publicly.

As a result, some users send large or non-standard transactions directly to miners. Leonidas describes this system as a private “black market” for transactions that Bitcoin itself considers valid.

Running DOG Mode would only change what an individual node accepts and relays. It would not change Bitcoin’s consensus rules. Moreover, other nodes could still ignore transactions relayed by DOG Mode nodes.

The Filtering War Behind the Launch

The launch extends a dispute that has intensified since 2023. That year, Ordinals introduced inscriptions to Bitcoin and triggered a sharp increase in data-heavy transactions.

Then, Runes launched during the 2024 Bitcoin halving. Notably, $DOG became Rune #3 and was etched in block 840000 at a fee rate of nearly 1.26 million sats per vByte.

Bitcoin Knots, maintained primarily by Luke Dashjr, takes a stricter approach to this activity. Its operators cite blockchain spam, higher resource costs and a preference for monetary transactions as reasons for applying stronger filters.

Bitcoin Core, however, has moved in the opposite direction. Its version 30 release expanded datacarrier limits, permitted multiple OP_RETURN outputs and lowered the minimum relay fee.

According to Leonidas, Core introduced these changes only after Runes and memecoin activity forced developers to reconsider existing relay policies. Consequently, the $DOG Army now wants to stop waiting for further policy changes.

“The $DOG Army is done asking for permission,” Leonidas wrote on X. “It is time to remove even more of these frivolous restrictions.”

Four Meggers and a $25 Million Dust Claim

The two parameters carry real stakes for Ordinals and Runes users. Bigger standard transactions would let large inscriptions travel through the public mempool.

The 1-sat dust rule targets a different problem. Runes transactions often pad outputs with small amounts of sats just to stay standard.

Leonidas estimates roughly $25 million in sats sits locked in that padding. He argues a 1-sat limit could return much of it to the ecosystem. Still, that figure remains an unverified estimate.

For context, past $DOG Army transactions bypassed public relay entirely. The Runestone inscription, near 3.99 MB, reached a block only through Marathon’s direct submission channel.

A Bitcoin DOG Mode Client With No Code Yet

One detail tempers the excitement. As of the announcement, no public code exists.

There is no GitHub repository, no release tag, and no commits to review. Instead, Leonidas asked developers to contact him directly to help build the first release.

So it is a proposal and a rallying cry, not yet running software. Node adoption sits at zero for now, since nobody can run it.

No security audit has been mentioned either. Until code appears, every claim about the client rests on the announcement alone.

The Filter Camp Pushes Back

Not everyone welcomes looser relay rules. The “filter” camp views heavy Ordinals and Runes activity as spam that bloats the chain.

These operators, often aligned with Knots and Luke Dashjr, warn about denial-of-service risks. Larger transactions and dust floods could strain node memory and bandwidth.

They also see stricter defaults as a feature, not a bug. In their view, permissive relay subsidizes low-value data and raises the cost of running a node.

Supporters counter that every fee-paying, valid transaction deserves relay. Meanwhile, no major Core or Knots developer had responded publicly to DOG MOde by the time of writing.

What Comes Next for Bitcoin DOG Mode

The next milestone is simple. A public repository would let developers verify the exact policy changes and test them.

Adoption would then depend on economics. Miners earn more from relayable high-fee transactions, so some may choose to run a permissive client.

History offers a hint. Core already relaxed several filters after community pressure, so this effort could nudge those defaults again.

For now, the story is a plan with momentum and no software. This article is not financial advice, so treat any $DOG token angle with care.