# The Article
Bitcoin's next big fight isn't about block size or transaction fees. It's about who gets to decide what Bitcoin actually does—and whether the protocol's most fundamental rule-making power belongs to a handful of developers or to the network itself.
Leonidas's DOG Mode client is forcing a conversation that should have happened years ago. By allowing nodes to relay transactions that Bitcoin Core currently blocks, DOG Mode reveals just how much power the default implementation holds over the entire ecosystem. That's not decentralization. That's governance by consensus among people who write code, not people who run nodes.
Here's what matters: Bitcoin Core is an implementation, not the law. When Core developers decide which transactions get relayed, which mempool policies get enforced, or which traffic patterns get filtered, they're making policy decisions that ripple across the entire network. Mining pools follow these defaults. Wallets follow these defaults. Node operators who don't understand the code just follow these defaults. Over time, defaults become de facto rules.
This is exactly backwards.
The original Bitcoin vision—the actual codebase—was designed so that individual nodes could set their own policies. Anyone running a node should be able to decide what transactions their hardware relays. But as Bitcoin matured, Core's relay policies became so entrenched that questioning them felt almost heretical. Deviate from Core's approach and you're suddenly "not really running Bitcoin" according to influential voices in the community.
DOG Mode isn't the answer to this problem. It's a wake-up call that we need better answers.
The real issue here is transparency and intentionality. If Bitcoin Core's relay policies are optimal—if they truly serve the network's security and efficiency—then they should survive open debate and competitive alternatives. Instead, we get gatekeeping language about "protocol correctness" and vague warnings about undefined risks. That's the rhetoric of institutions protecting turf, not engineers solving problems.
I'm not saying Leonidas has it completely right. Raw relay of every transaction creates its own problems. But the point isn't whether DOG Mode is the solution. The point is that Bitcoin's governance should be open enough that experiments like this can happen without triggering a panic.
Bitcoin thrives on the principle that anyone can challenge the rules. That applies to transaction validation, proof-of-work, and confirmation times. It should also apply to relay policies. If Core's defaults are genuinely better, prove it through data and debate—not through network effects and institutional inertia.
The cryptocurrency community spent fifteen years arguing that Bitcoin needed to be decentralized precisely because centralized systems make unilateral decisions behind closed doors. We should take that seriously when it comes to protocol governance too.
Bitcoin's strength has always been that its rules emerge from the network, not from any single authority. DOG Mode is annoying precisely because it reveals how far we've drifted from that ideal.
The question now is whether Bitcoin's developer community will treat this as a threat or an opportunity.