DOG Mode opens a new front in Bitcoin’s governance fight

Bitcoin Ordinals advocate Leonidas has introduced DOG Mode, an alternative open-source Bitcoin client that changes how nodes relay certain valid transactions without altering Bitcoin’s consensus rules.

Summary

• DOG Mode removes default relay limits while keeping Bitcoin’s existing consensus rules completely unchanged today.
• Leonidas says fee-paying users should access block space without Bitcoin Core deciding transaction purposes beforehand.
• BIP 110 takes opposite approach, proposing temporary consensus restrictions on several data-heavy Bitcoin transaction types.

The project adds a new layer to the dispute over Ordinals, Runes and the use of Bitcoin block space.

In his DOG Mode announcement, Leonidas argued that Bitcoin Core and Bitcoin Knots enforce policy restrictions that Bitcoin’s consensus rules do not require. He said a transaction can remain valid under consensus while default nodes still refuse to relay it across the peer-to-peer network.

DOG Mode targets relay policy, not Bitcoin consensus

DOG Mode would raise the maximum individual transaction size allowed under its relay policy to 3.9 million weight units. Bitcoin Core’s default policy currently limits individual standard transactions to 400,000 weight units. The client would also lower the dust threshold to one satoshi for small transaction outputs.

As reported by crypto.news, DOG Mode does not require a Bitcoin fork because it works within existing consensus rules. Nodes can choose to run the software and relay transactions that other clients may treat as non-standard, while miners still decide which valid transactions they include in blocks.

Ordinals and Runes return to the governance debate

The proposal centers on a long-running dispute over whether Bitcoin should treat every valid, fee-paying transaction equally. Leonidas supports a market-based model in which users compete for block space through fees rather than software developers deciding which transaction structures should receive default relay support.

DOG Mode could make it easier to propagate large Ordinals inscriptions and small outputs used by some Bitcoin-native token protocols. However, different relay policies could also leave nodes with different views of unconfirmed transactions before miners add them to blocks. Bitcoin’s consensus rules would remain unchanged even if node mempools differed.

DOG Mode takes a different path from BIP 110

The DOG Mode approach contrasts with BIP 110, which proposes temporary consensus restrictions on several forms of transaction data. As reported by crypto.news, Bitcoin developer Luke Dashjr has continued to support the proposal despite opposition from users who view the restrictions as censorship.

BIP 110 supporters argue that data-heavy transactions raise storage costs and consume scarce block space. Critics argue that changing consensus rules to restrict currently valid transactions could create a broader precedent. Michael Saylor and Adam Back have opposed BIP 110, as reported by crypto.news, while miner signaling remained far below its proposed 55% activation threshold in mid-July.

Bitcoin users decide which policies gain adoption

DOG Mode also raises questions about how Bitcoin governance works outside formal protocol changes. Bitcoin Core developers can set default relay policies, but node operators remain free to run other software. Miners can also receive transactions through direct channels instead of the public peer-to-peer relay network.

That distinction means DOG Mode does not need broad agreement to begin operating. Its influence will depend on whether node operators, miners and Bitcoin users choose to adopt its policies. Leonidas said the longer-term aim is for wider use to push existing Bitcoin clients to reconsider restrictions that he views as unnecessary.

The debate now presents two different approaches to disputed Bitcoin activity. BIP 110 seeks new consensus restrictions, while DOG Mode removes some default policy limits without changing consensus. The outcome will depend on which software users choose to run and which transactions miners choose to process.