Ordinals supporter Leonidas launches new Bitcoin client: "$DOG model"

Bitcoin serial number supporter Leonidas proposes to build an alternative open source Bitcoin client

Bitcoin serial number supporter Leonidas proposes to build an alternative open source Bitcoin client aimed at relaxing certain protocols and forwarding restrictions. According to him, these restrictions have affected the operation of some "rune" and "serial number" trading models on the Internet.

In a post posted on Friday, Leonidas outlined what he called the "Bitcoin $DOG model" and argued that it would lower the threshold for sending inscriptions and runes, while challenging the default settings long used by widely deployed Bitcoin software.

Core Points

The "Bitcoin $DOG Model" proposed by Leonidas increases the maximum volume of a single transaction to 3.9 million weight units, while the limit of Bitcoin's core software is 400,000 weight units.

The client reduced the dust limit from the range of 294 to 546 Cats common in Bitcoin core software to 1 Cats, thereby changing the economic treatment of small exports.

Proponents of the changes argue that the changes make it easier to package large serial number inscriptions and runes into individual transactions in batches, while critics call such activities "spam."

Leonidas positioned the proposal as an alternative to Bitcoin's core software and Bitcoin nodes, aiming to drive broader policy reflection through user adoption.

What does Leonidas want to change

Leonidas's proposal focuses on two rules. According to him, these rules are overly restrictive compared to Bitcoin's original intention. First, he targeted the maximum volume of a single transaction. According to his description, the "Bitcoin $DOG model" will allow transaction volumes up to 3.9 million weight units, while the Bitcoin core software is set to 400,000 weight units.

Second, he proposed reducing the dust limit to 1 Cong. Leonidas sees this as a way to eliminate the need for users to populate output, a problem that is linked to whether certain extremely small outputs are still economically feasible and whether nodes forward those outputs under default policies.

In the same post, Leonidas argued that these adjustments would directly improve the usability of projects based on inscriptions and bitcoin transfers (including serial numbers and runes) that have been controversial within the broader Bitcoin community.

Why transaction volumes and dust limits matter

For serial numbers and symbols, the practical challenge is often not only whether the network can technically contain data or output, but also whether standard forwarding and behavioral policies make certain transaction constructs inconvenient or difficult to broadcast.

Leonidas 'higher transaction volume limit is particularly critical for users who want to bundle larger content into a single transaction. The larger a single transaction the client allows, the more data a single on-chain operation can accommodate-possibly even close to the capacity of the entire block.

In terms of forwarding, reducing dust quotas aims to change the economics and mechanisms of export. Dust limits define the minimum amount of output that can be economically sent and are usually related to whether the network and default node software regard these outputs as infeasible or non-transferable. Leonidas said that by lowering the dust threshold to 1 Cong, users will no longer need to add additional value to have transactions accepted by the default Bitcoin core node.

Leonidas stated: "Bitcoin itself does not have these rules."

Leonidas's argument involves both technical and clear political aspects. He claimed that Bitcoin core software and Bitcoin nodes (the two most commonly used Bitcoin clients)"have been enforcing rules that Bitcoin itself does not have for years," and positioned his $DOG model as a fix.

According to Leonidas, the move is not only to support serial numbers and runes, but also to eliminate what he describes as "licensing" requirements imposed by mainstream software operators and maintainers. He views the effort as an attempt to broaden the scope of acceptable trading behavior without requiring users to seek approval through existing default implementations.

Although serial numbers and symbols are often described as Bitcoin's practice of non-homogeneous and homogeneous token concepts, these methods have been controversial. Critics believe that large-scale inscription or rune-related activities are similar to online "spam" and may reduce overall usability or add additional burdens. Leonidas's proposal directly targets infrastructure options that facilitate or restrict such activities, transforming community debate into engineering proposals.

Strategies to put pressure on Bitcoin's core policies

Leonidas said that the "Bitcoin $DOG model" is designed to operate as an alternative to Bitcoin's core software and Bitcoin nodes. His clear goal goes beyond releasing a forked client: He hopes to attract enough users so that Bitcoin's core software will eventually come under pressure to relax its own restrictions.

This approach is important because the policy and configuration choices of Bitcoin's core software affect which transactions are most likely to spread across the network, especially for nodes using default settings. A competing client with significantly different restrictions may change actual behavior: if more users and services adopt it, standard assumptions about which transactions can be effectively forwarded may change.

At the same time, the proposal also raises questions that deserve readers 'close attention-especially where the border will be located. If larger transaction volumes and lower dust limits are widely adopted, new trade-offs could arise involving bandwidth, verification workload, and resource consumption at the network level. Leonidas's plan also relies on adoption: without widespread use, policies on Bitcoin's core software may remain unchanged.

Next, investors and builders who are concerned about the asset ecosystem of the Bitcoin chain should pay attention to whether the $DOG model has actually been adopted and how the proposal is accepted in other parts of the Bitcoin software ecosystem, especially forwarding behaviors and policy settings that affect daily transaction broadcasts.