Bitcoin Ordinals advocate Leonidas has proposed building an alternative open-source Bitcoin client designed to loosen specific protocol and relay constraints that, according to its creator, have limited certain “Runes” and “Ordinals” transaction patterns on the network.
In a post on X on Friday, Leonidas outlined what he calls “Bitcoin $DOG Mode,” arguing it would reduce barriers for sending inscriptions and Runes while challenging long-standing default settings used by widely deployed Bitcoin software.
Key takeaways
- Leonidas’ proposed “Bitcoin $DOG Mode” would raise the maximum individual transaction size to 3.9 million weight units (WU), versus Bitcoin Core’s 400,000 WU.
- The client would lower the dust limit to 1 satoshi, from Bitcoin Core’s commonly cited range of 294–546 sats, changing how small outputs can be handled economically.
- Supporters say these changes would make it easier to batch larger Ordinals inscriptions and Runes into single transactions, while critics have called such activity “spam.”
- Leonidas positions the proposal as an alternative to Bitcoin Core and Bitcoin Knots, aiming to force broader policy reconsideration through user adoption.
What Leonidas wants to change
Leonidas’ proposal centers on two rules he says are unnecessarily restrictive relative to what he views as Bitcoin’s intent. First, he targets the maximum size of an individual transaction. In his description, “Bitcoin $DOG Mode” would allow transactions up to 3.9 million WU, compared with Bitcoin Core’s 400,000 WU setting.
Second, he proposes reducing the dust limit to 1 satoshi. Leonidas frames this as a way to eliminate the need for users to pad outputs—an issue associated with whether certain tiny outputs remain economical to include and whether nodes relay them under default policies.
In the same post, Leonidas argued that these adjustments would directly improve usability for projects built around inscriptions and token-like transfers on Bitcoin, including Ordinals and Runes, which have been debated within the broader Bitcoin community.
Why transaction size and dust limits matter
For Ordinals and Runes, the practical challenge is often not just whether the network can technically include data or outputs, but whether standard relay and policy behaviors make certain transaction constructions inconvenient or difficult to broadcast.
Leonidas’ proposed higher transaction size limit would be particularly relevant for users who want to bundle much larger pieces of content into one transaction. The larger the single transaction the client permits, the more data can be placed into one on-chain action—potentially even nearing the capacity of an entire block.
On the relay side, lowering the dust limit is meant to change the economics and mechanics of outputs. Dust limits define the smallest output amounts that can be sent economically, typically tied to whether the network and default node software treat those outputs as non-viable or non-relayable. By pushing the dust threshold down to 1 satoshi, Leonidas suggests users would no longer have to add extra value to make transactions acceptable to default Bitcoin Core nodes.
“Rules that Bitcoin itself does not have,” Leonidas says
Leonidas’ argument is explicitly political as well as technical. He claims that Bitcoin Core and Bitcoin Knots—two of the most commonly used Bitcoin clients—have “spent years enforcing rules that Bitcoin itself does not have,” positioning his $DOG Mode as a corrective.
According to Leonidas, the initiative is not just about supporting Ordinals and Runes, but about removing what he characterizes as “permission” requirements imposed by mainstream software operators and maintainers. He casts the effort as a bid to widen the set of acceptable transaction behaviors without needing users to seek approval through existing default implementations.
While Ordinals and Runes are often described as Bitcoin’s approach to non-fungible and fungible token concepts, the methods have remained controversial. Critics have argued that large-scale inscription or runes-related activity resembles network “spam” and may degrade overall usefulness or impose additional burdens. Leonidas’ proposal directly targets the infrastructure choices that enable or limit such activity, turning a community debate into an engineering proposal.
A strategy to pressure Bitcoin Core policy
Leonidas said “Bitcoin $DOG Mode” is intended to operate as an alternative to Bitcoin Core and Bitcoin Knots. His stated goal goes beyond shipping a fork-like client: he wants to attract enough users that Bitcoin Core would eventually face pressure to loosen its own restrictions.
This approach matters because Bitcoin Core’s policy and configuration choices influence what transactions are easiest to propagate through the network, particularly for nodes using default settings. A competing client with meaningfully different limits could shift practical behavior: if more users and services adopt it, standard assumptions about what transactions can be relayed efficiently might change.
At the same time, the proposal raises questions readers may want to watch closely—especially around where boundaries would end. If larger transaction sizes and lower dust limits become widely used, it could lead to new tradeoffs involving bandwidth, verification workload, and network-level resource consumption. Leonidas’ plan also depends on adoption: without broad usage, Bitcoin Core’s policies may remain unchanged.
Next, investors and builders watching Bitcoin’s on-chain asset ecosystem should pay attention to whether $DOG Mode attracts real-world adoption and how the proposal is received by other parts of the Bitcoin software ecosystem, particularly around relay behavior and policy settings that affect everyday transaction broadcasting.
Be the first to comment