A brewing debate over how much non-financial data belongs on the Bitcoin blockchain has produced two starkly opposed responses: a formal proposal to tighten restrictions and a new client designed to sidestep them entirely.
## The Case for Restriction BIP 110 represents the camp that wants to curb the flow of arbitrary data onto Bitcoin's ledger. The proposal seeks to accomplish this through a consensus change, meaning it would require broad agreement across the network to take effect. So far, that support has been hard to come by.
Backers of the measure argue that Bitcoin's blockspace should prioritize monetary transactions rather than being clogged with images, text, and other non-financial payloads that have surged in popularity through inscription-style activity. Critics of that data view it as spam that bloats the chain and raises the cost of running a node.
One faction wants to slam the door on blockchain data, while the other is building a way to prop it wide open.
But a consensus change is a heavy lift. BIP 110 has attracted almost no miner backing, which effectively stalls its path forward. Without the hashpower to enforce new rules, the proposal remains more a statement of intent than an imminent shift in how Bitcoin behaves.
## The Permissionless Counterpunch On the other side sits DOG Mode, a Bitcoin client built to do the exact opposite. Rather than filtering or limiting data, it is engineered to bypass the kinds of restrictions that proposals like BIP 110 hope to impose.
Crucially, DOG Mode requires no vote and no consensus change to function. Because it operates as an alternative client that individual operators can choose to run, it sidesteps the network-wide agreement that formal proposals depend on. That makes it a far lighter path to influence how transactions and data move through the system.
The contrast highlights a defining tension in Bitcoin's design philosophy:
- Consensus changes need widespread buy-in and can be blocked by inaction, as BIP 110 illustrates.
- Client-level tools can shift behavior without any formal approval, giving individual users outsized leverage.
The standoff underscores how difficult it is to police data on a permissionless network. As long as node operators can pick their own software, efforts to restrict blockchain content may struggle against tools purpose-built to work around them.