Bitcoin nodes signal support for BIP-110

TLDR

Bitcoin node support for BIP-110 is growing but still small, and it has opened a fresh governance fight over how much non-monetary data should be allowed on the network.

1. BIP-110 is a temporary soft fork that caps arbitrary transaction data, currently signaled by about 2.38% of Bitcoin nodes.
2. The proposal aims to fight spam from inscriptions and other non-monetary uses, but critics say it risks censorship and protocol churn.
3. What matters next is whether more nodes and miners adopt BIP-110 and whether it converges with, or collides with, Bitcoin Cores roadmap.

Deep Dive

1. What BIP-110 Actually Does

BIP-110 is a Bitcoin Improvement Proposal that introduces a temporary soft fork to limit how much arbitrary data can be embedded in each transaction at the consensus layer.

Reports say it sets a maximum size for certain transaction outputs at 34 bytes and restores an 83-byte cap on OP_RETURN data, reversing limits that Bitcoin Core v30 recently removed.

Current support is modest. Around 2.38% of Bitcoin nodes, or roughly 583 out of 24,481, are running BIP-110 code, mainly via the Bitcoin Knots client, so this is an early signaling phase rather than a near-term activation.

2. Why It Is Controversial

BIP-110 is part of a broader fight over inscriptions, Ordinals, and other non-monetary uses that stuff large blobs of data into Bitcoin transactions. Supporters frame this as spam that raises node costs and threatens decentralization.

Backers argue that capping data at the consensus level protects home node operators from ballooning disk and bandwidth needs, keeping Bitcoin closer to a lean sound money system.

Opponents, including some high-profile industry figures, counter that aggressive protocol changes to restrict data are themselves a bigger risk, potentially enabling de facto censorship of valid transactions and undermining the norm of minimal changes to Bitcoins rules.

3. What To Watch From Here

First, watch the share of nodes running BIP-110. If it remains a small minority, it stays a pressure signal rather than a path to activation. A noticeable rise would increase coordination pressure on miners and Core.

Second, monitor whether miners adopt BIP-110 code. For a soft fork to become effective, a sufficiently large share of hash rate needs to enforce the new rules, otherwise it remains a niche policy.

Third, observe how Bitcoin Core maintainers respond. Core v30 already removed the old OP_RETURN cap, so there is now a visible split between uncap and let fees decide and reimpose caps via BIP-110. Any attempt to reconcile those approaches will shape future governance norms around Bitcoin upgrades.

Conclusion

BIP-110 shows that a non-trivial minority of the Bitcoin ecosystem wants to clamp down on non-monetary data at the protocol level, rebalancing toward conservative, payment-centric usage.

Whether it stays a niche experiment or becomes a real consensus change depends on node and miner adoption and on how it interacts with the existing Bitcoin Core roadmap. For users, the main practical stakes lie in how future upgrades treat inscriptions, data-heavy use cases, and the cost of running a full node.