A prominent Bitcoin Ordinals advocate, Leonidas, has proposed building an alternative open-source Bitcoin client aimed at easing protocol-level limits that currently affect Ordinals inscriptions and Runes-style token transfers. The proposal, discussed in a Friday post on X, is framed as a way to reduce what Leonidas calls unnecessary “permission” requirements enforced by widely used node software.
Leonidas’ plan—described as “Bitcoin $DOG Mode”—would, if implemented, increase the maximum individual transaction size and reduce the network’s dust threshold. Supporters argue these changes would make it more practical to package larger token and inscription activity into fewer transactions, while critics have long accused Ordinals and Runes of contributing to “spam” on Bitcoin’s base layer.
Key takeaways
- “Bitcoin $DOG Mode” proposes a new open-source client to relax limits that Leonidas says hinder Ordinals inscriptions and Runes transactions.
- It targets a much higher max transaction size—3.9 million weight units versus Bitcoin Core’s 400,000 WU.
- It would lower the dust limit to 1 satoshi from the current range of 294–546 sats, reducing output padding requirements.
- The approach is positioned as competitive: the client would be an alternative to Bitcoin Core and Bitcoin Knots, with the goal of pressuring broader adoption to loosen restrictions.
What Leonidas says would change
In his announcement on X, Leonidas set out two specific operational tweaks. First, the proposal would lift the maximum allowed size for an individual transaction to 3.9 million weight units, compared with 400,000 WU under Bitcoin Core. Second, it would reduce the dust limit—the minimum UTXO amount considered economically spendable—to 1 satoshi, down from a 294–546 satoshi range.
Leonidas’ stated reasoning is that Bitcoin’s rules and culture are broader than what popular client implementations currently permit. He argues that Bitcoin Core and Bitcoin Knots have spent years applying policies that go beyond what he believes the protocol requires, particularly in ways that complicate how Ordinals and Runes activity is formatted and relayed across nodes.
“Bitcoin Core and Bitcoin Knots have spent years enforcing rules that Bitcoin itself does not have,” Leonidas said in a statement, describing the initiative as a response to what he calls excessive restrictions.
Why transaction limits matter for Ordinals and Runes
Both Ordinals and Runes are often discussed as Bitcoin’s answer to categories of assets usually associated with token standards outside Bitcoin—inscriptions for non-fungible representations and Runes for fungible token-like transfers. Even though they’re controversial, they share a practical challenge: getting complex data and structured token transfers into transactions that fit within standard limits.
Leonidas emphasized that increasing the transaction size ceiling would make it easier for Ordinals users to fit much larger files or collections into a single transaction. Under the proposed settings, he said it could be possible to create transactions that consume a large share of block space—transactions approaching nearly an entire block—without being blocked by client-imposed maximums.
The dust-limit change would also target day-to-day friction. Dust rules determine the smallest outputs that are economical to handle. If dust is too high, users may need to create extra output padding to ensure their transactions get relayed and processed smoothly by default Bitcoin Core nodes. Leonidas’ proposal would reduce that requirement by lowering the economically “uneconomical” floor to 1 satoshi.
From an end-user perspective, those adjustments translate into fewer constraints when forming inscription-heavy or token-heavy transactions—potentially enabling more efficient packaging and less waste in output structure.
Alternative client strategy—and what it would take to move the market
Leonidas positioned $DOG Mode not as a patch to Bitcoin Core, but as an alternative open-source client. In his description, the new client is meant to compete with two of the most widely used Bitcoin node implementations: Bitcoin Core and Bitcoin Knots.
The broader bet is that if enough users run the new client, Bitcoin Core may eventually be forced to reconsider its own policy restrictions in practice. Leonidas said the objective is to build enough adoption that Bitcoin Core would “eventually” have to loosen its stance.
That strategy reflects a key tension in Bitcoin’s ecosystem: software defaults strongly influence what is considered “normal” network behavior. Even when community debate centers on whether certain limitations are truly required by Bitcoin’s fundamentals, the reality for users is that mainstream clients shape what transactors can practically submit and propagate without running into relay or policy friction.
Whether a competing client can achieve the kind of uptake Leonidas is targeting remains unclear. Adoption depends on more than technical changes—it requires trust in the client’s security, compatibility, and network behavior. The proposal’s effectiveness would also hinge on how other nodes in the ecosystem handle and standardize the transactions produced by $DOG Mode.
An ongoing debate over “spam” and Bitcoin’s direction
The move lands in the middle of a continuing community argument. Leonidas’ remarks explicitly tap into a familiar criticism: that Ordinals and Runes can increase on-chain activity by embedding additional data and structures into transactions. Detractors have repeatedly argued that this kind of usage is “spam” that burdens the network and obscures Bitcoin’s purpose.
Supporters generally counter that Bitcoin’s permissionless nature allows diverse usage, and that clients should not restrict how data and token-like activity can be expressed on-chain when the underlying protocol can accommodate it.
Leonidas’ client proposal is essentially a technological expression of that philosophical dispute. By altering parameters around transaction size and dust thresholds, $DOG Mode would aim to make controversial activity easier to execute and easier to propagate—without relying on permission from the dominant clients.
Earlier coverage from Cointelegraph has discussed the conservative node client landscape as part of this broader context, underscoring how different implementations can influence what users can do on Bitcoin without friction.
Earlier Cointelegraph reporting has also highlighted how conservative approaches can restrict certain inscription activity, reinforcing why Leonidas’ focus on client-enforced rules is central to this proposal.
What readers should watch next is whether Leonidas and supporters produce a working open-source implementation of “Bitcoin $DOG Mode,” and—if they do—how quickly it gains traction among users and node operators. Equally important will be whether the proposed parameter changes trigger more explicit policy adjustments from Bitcoin Core or other major clients, or whether the ecosystem continues to split into competing operational norms.
Be the first to comment