Leonidas proposes “Bitcoin $DOG Mode” client to loosen Ordinals and Runes relay limits
The plan targets a 3.9M WU per-transaction cap and a 1-sat dust limit to pressure default policy changes via adoption.
Ordinals advocate Leonidas proposed a new open-source Bitcoin client, “Bitcoin $DOG Mode,” designed to relax default relay policies that affect Runes and Ordinals transactions. The pitch centers on raising the maximum individual transaction size to 3.9 million weight units and lowering the dust limit to 1 satoshi, with adoption framed as leverage on Bitcoin Core’s defaults.
Key Takeaways
- A new open-source Bitcoin client concept, “Bitcoin $DOG Mode,” was floated as a way to remove relay restrictions impacting Ordinals inscriptions and Runes.
- The proposal targets a 3.9 million weight unit per-transaction limit, far above Bitcoin Core’s 400,000 WU default.
- A 1-satoshi dust limit is part of the plan, down from a cited 294–546 sats range.
- The stated strategy is to win enough user adoption that Bitcoin Core loosens its own default transaction policies.
Leonidas Pitches “Bitcoin $DOG Mode” as an Alternative Client for Ordinals and Runes
Leonidas, a prominent Ordinals advocate, proposed developing a new open-source Bitcoin client called “Bitcoin $DOG Mode” in a post to X on Friday. The client is framed as an alternative to Bitcoin Core and Bitcoin Knots, with the explicit goal of changing what transactions are relayed and accepted by default for Ordinals inscriptions and Runes activity.
Leonidas cast the effort as a response to policy constraints imposed by existing clients rather than anything inherent to Bitcoin’s base rules. “Bitcoin Core and Bitcoin Knots have spent years enforcing rules that Bitcoin itself does not have,” Leonidas said. He also framed the move as a break from trying to win approval inside existing maintainer circles: “The $DOG Army is done asking for permission. It is time to remove even more of these frivolous restrictions.”
For traders, the important framing is that this is a policy-layer challenge, not a consensus change. The pitch is about what nodes will propagate and miners will see in their mempools by default, which is where practical throughput for inscription-style traffic often gets decided.
The Two Policy Targets: 3.9M WU Transactions and a 1-Sat Dust Limit
The proposal’s two concrete parameters are straightforward.
First, $DOG Mode would lift the maximum individual transaction size to 3.9 million weight units (WU), compared with Bitcoin Core’s 400,000 WU. Leonidas argued this would make it easier for Ordinals users to place much larger files or collections into a single transaction, including transactions that could take up nearly an entire block.
Second, the client would lower the dust limit to 1 satoshi from 294–546 sats. The dust limit is described as a policy rule defining the smallest output value, or UTXO, that can be economically sent. Lowering it is positioned as a usability change for small outputs, reducing the need to “pad” outputs just to get a transaction broadcast on default Bitcoin Core nodes.
Why Relay Policy Is the Battleground for Ordinals and Runes
Ordinals inscriptions and Runes are described as Bitcoin’s take on non-fungible and fungible tokens, respectively. They remain politically contentious inside Bitcoin, with critics labeling the activity “spam” that consumes blockspace.
That dispute has increasingly concentrated around relay and mempool defaults. Client policy can filter what propagates efficiently across the network even when transactions are valid under consensus rules. In practice, that means policy can shape which transaction types are easy to get mined without bespoke routing, direct miner relationships, or specialized infrastructure.
Leonidas is explicit that adoption is the pressure mechanism. “Over time the economic incentives will drive $DOG Mode’s adoption and force Bitcoin Core to stop gatekeeping and allow these completely valid transactions,” he said. That is a market-structure claim: if enough nodes, wallets, and miners treat these transactions as normal, the default policy center of gravity can shift.
Next Signals: Code, Adoption, and Any Response From Core/Knots
The immediate tell is whether $DOG Mode becomes more than a parameter list. A public code repository or initial release would clarify whether the 3.9M WU per-transaction policy and 1-sat dust limit are implemented as described.
The second signal is political and technical response. Any public counter-proposal or pushback from Bitcoin Core or Bitcoin Knots maintainers on relay defaults for Ordinals and Runes-style activity would indicate whether this is being treated as a credible challenge or dismissed as noise.
The third is adoption evidence that can actually move relay behavior: node counts, miner or pool relay behavior, and wallet support. Without those, the proposal cannot meaningfully change what reaches mempools at scale.
Finally, on-chain patterns matter. If the client gains traction, traders would expect to see transaction patterns consistent with larger single-transaction inscriptions, including more very-large transactions approaching the proposed 3.9M WU cap.
A Proposal With Clear Parameters, but No Proof of Execution Yet
I treat $DOG Mode as a cleanly specified pressure play, not a network event. The numbers are the story, and they are unambiguous: 3.9M WU per transaction and 1-sat dust are designed to normalize token-like Bitcoin usage at the relay layer without touching consensus.
The threshold that matters is adoption that changes default propagation, not the rhetoric. If code ships and measurable node, wallet, or miner uptake follows, the setup starts to look structural rather than narrative-driven, and that is when Ordinals and Runes fee-market spillovers become a real variable again.
