Ordinal developers propose new Bitcoin client with "$DOG model"

Bitcoin Ordinals advocates propose a new client solution: "$DOG model"

Well-known Bitcoin Ordinals advocate Leonidas proposed to develop an alternative open source Bitcoin client aimed at relaxing current protocol layer restrictions affecting the transfer of Ordinals inscriptions and Runes-style tokens. The proposal, discussed in an article on the X Platform on Friday, aims to reduce the "licensing" requirements imposed on what Leonidas called widely used node software.

Leonidas's plan-known as the "Bitcoin $DOG model"-if implemented, would increase the maximum size of individual transactions and lower the network's dust threshold. Proponents believe the changes will make it more practical to package larger token and inscription activities into fewer transactions, while critics have long accused Ordinals and Runes of creating "spam" on the Bitcoin foundation.

Key Points

·The "Bitcoin $DOG Model" proposes a new open source client to relax restrictions that Leonidas believes hinder Ordinals inscription and Runes transactions.
·The goal is to significantly increase the maximum transaction size to 3.9 million weighted units, while the core Bitcoin client is 400,000 WUs.
·Reduce the dust limit from the current range of 294-546 Cong to 1 Cong, reducing output fill requirements.
·The approach is positioned as a competitive solution: the client will become a replacement for Bitcoin core and Bitcoin node software, aiming to promote wider adoption to relax restrictions.

Specific changes proposed by Leonidas

In the announcement of the X platform, Leonidas listed two specific operational adjustments. First, the proposal increases the maximum allowed size of a single transaction to 3.9 million weight units, compared with 400,000 WUs for Bitcoin's core client. Second, it lowered the dust limit-the minimum amount of UTXO considered economically expendable-from the range of 294-546 CSC to 1 CSC.

Leonidas gave the reason that Bitcoin's rules and culture are broader than current popular client-side implementations allow. He believes that Bitcoin Core and Bitcoin Node software have been implementing policies for years that exceed protocol requirements, particularly in terms of complicating the formatting and relaying of Ordinals and Runes activities between nodes.

"Bitcoin Core and Bitcoin Node software have been enforcing rules for years that Bitcoin itself does not prescribe,"Leonidas said in a statement, describing the initiative as a response to what he called excessive restrictions.

Importance of trading restrictions to Ordinals and Runes

Ordinals and Runes are often seen as Bitcoin's response to asset classes typically associated with token standards outside of Bitcoin-inscriptions for non-homogeneous representations and Runes for similar homogeneous token transfers. Although controversial, they both face a practical challenge: embedding complex data and structured token transfers into transactions that meet standard limits.

Leonidas emphasized that increasing the transaction size cap will make it easier for Ordinals users to put larger files or collections into a single transaction. Under the proposed settings, he said it was possible to create transactions that consumed a large amount of block space (close to the entire block) without being subject to maximum limits imposed by the client.

Changes to dust limits are also intended to address daily friction. Dust rules determine the minimum output that can be economically processed. If the dust is too high, users may need to create additional output padding to ensure that their transactions can be relayed and processed smoothly by the default Bitcoin core node. Leonidas's proposal reduces this requirement by lowering the economically "uneconomical" threshold to 1.

From an end-user perspective, these adjustments mean fewer restrictions when building inscription-or token-intensive transactions-potentially allowing for more efficient packaging and less waste of output structures.

Alternative client strategies-and the conditions needed to drive the market

Leonidas positions the $DOG model as an alternative to Bitcoin's core rather than a patch. In his description, the new client is designed to compete with the two most widely used Bitcoin node implementations-Bitcoin Core and Bitcoin Node Software.

The broader bet is that if enough users are running the new client, Bitcoin Core may eventually be forced to rethink its policy limitations in practice. Leonidas said the goal was to establish enough adoption rates for Bitcoin core to "eventually" have to relax its stance.

The strategy reflects a key tension in the Bitcoin ecosystem: Software default settings strongly influence what constitutes "normal" network behavior. Even though community debate centers on whether certain restrictions are truly required by Bitcoin fundamentals, the reality for users is that mainstream clients determine what traders can actually submit and disseminate without encountering relays or policy frictions.

It remains unclear whether a competing client can achieve the adoption rates Leonidas is targeting. Adoption depends not only on technological change-it also requires trust in client security, compatibility, and network behavior. The effectiveness of the proposal also depends on how other nodes in the ecosystem process and standardize transactions generated by the $DOG model.

Continuing debate over "spam" and the direction of Bitcoin

The move comes amid ongoing debate in the community. Leonidas's comments clearly touched on a familiar criticism: Ordinals and Runes could increase on-chain activity by embedding additional data and structure into transactions. Opponents have repeatedly believed that this use is "spam" that burdens the network and obscures the purpose of Bitcoin.

Proponents often counter that Bitcoin's permission-free nature allows for diverse uses, and that clients should not restrict how data and token-like activities are expressed on the chain when the underlying protocol can accommodate it.

Leonidas's client proposal is essentially a technical expression of this philosophical controversy. By changing parameters for transaction sizes and dust thresholds, the $DOG model aims to make controversial activities easier to execute and spread-without relying on licensing from mainstream clients.

Readers should focus next on whether Leonidas and supporters can launch a viable open source implementation of the "Bitcoin $DOG Model" and if so, how quickly it will be adopted among users and node operators. Equally important is whether the proposed parameter changes will trigger clearer policy changes from Bitcoin's core or other major clients, or whether the ecosystem will continue to split into competing operating norms.