Debates and disputes about Bitcoin’s governance often pivot on the rules baked into the world’s original blockchain network’s code. The latest dispute suggests the reality is more nuanced.
The alternative Bitcoin client “DOG Mode”, introduced by Bitcoin developer “Leonidas”, doesn't attempt to rewrite Bitcoin's consensus rules. Instead, it targets the default relay policies used by Bitcoin Core and other node software. These are in effect the settings that determine which valid transactions are forwarded around the network before miners include them in a block.
In doing so, the developer is reopening a philosophical debate over censorship, free markets and who really governs the network.
Leonidas is an advocate of the Ordinals protocol, which allows data to be stored on the Bitcoin blockchain, often in the form of images or texts to essentially create a version of non-fungible tokens (NFTs).
The Bitcoin Improvement Proposal (BIP) 110 sought to tighten the network’s rules to make such transactions more difficult, prompting accusations of censorship from its critics.
Bitcoin consensus rule changes are rare, hence why attempts to alter them seem so seismic. In many ways, DOG Mode represents the philosophical mirror image of BIP-110.
Supporters of BIP-110 view Bitcoin as a public utility whose scarce block space should be reserved primarily for monetary settlement. Inscriptions and other data-heavy applications represent consumption of a limited resource that should be protected for financial transactions, even if doing so requires introducing new consensus rules.
DOG Mode starts from the opposite premise.
Leonidas argued Bitcoin should remain a neutral marketplace for block space, where any valid transaction is equally legitimate provided the sender pays the prevailing fee. From that perspective, there is no objective distinction between a bitcoin payment and an Ordinals inscription.
Rather than seeking permission through a protocol upgrade, the intention for DOG Mode is to remove policy restrictions that its supporters argue Bitcoin itself never required.
The proposal also raises a more subtle question about Bitcoin's infrastructure.
If enough nodes begin running different policy software, the network's mempool — the collection of unconfirmed transactions waiting to be mined — could become increasingly fragmented. Consensus would remain intact, but different parts of the network could relay different transactions, affecting fee estimation and how quickly some transactions reach miners.
Source
This article is syndicated for educational reading. For the latest updates, visit the original publisher.
Read on coindesk.com
