A new wave of support for Bitcoin Improvement Proposal 110 (BIP-110) is transforming the landscape of technical discussions within Bitcoin. Current data shows that 583 out of a total of 24,481 active nodes are now running this protocol, representing 2.38% of the complex global Bitcoin network.
How Many Nodes Have Adopted Standard 110?
According to Cointelegraph reports, Bitcoin Knots has become the main software implementation driving the adoption of BIP-110 during the ongoing soft fork phase. Standard 110 is specifically designed to: limit transaction output size to a maximum of 34 bytes while setting the OP_RETURN data limit at 83 bytes. This temporary implementation phase is scheduled to last for the next twelve months, with possible modifications or extensions depending on community response and network monitoring results, as outlined on the official proposal’s GitHub page.
What Is the Root of the Dispute: OP_RETURN and Spam Concerns?
The OP_RETURN script code, which allows embedding arbitrary data within the blockchain, has become a hot topic of intense debate within the Bitcoin ecosystem. This conflict has escalated sharply since the release of Bitcoin Core version 30, which made a controversial decision: removing the previous OP_RETURN data limit of 83 bytes.
This innovative pull request—first proposed in April 2025—triggered a wave of significant rejection from various community segments. When the update was finally launched in October 2025, harsh criticisms questioned the consequences of removing the arbitrary data restrictions. Opponents warned that lifting this limit would open wide avenues for mass spam on the already full Bitcoin ledger.
Centralization: A Long-Term Threat to Bitcoin’s Decentralization
Deeper concerns go beyond simple spam issues. A significant increase in arbitrary data volume would raise storage burdens for every user running a full Bitcoin node. Growing infrastructure costs could potentially push network power consolidation into the hands of a few large-resource players.
Bitcoin’s fundamental value proposition lies in its ability to operate on standard consumer hardware—ordinary personal computers owned by average users. However, if technical requirements continue to rise, Bitcoin’s vision as a truly decentralized monetary system will be compromised. An analogy made by one commentator, Matthew Kratter, is very illustrative: spam acts like parasitic plants draining their host trees, gradually weakening the fundamental structure of the network itself.
A Different Voice: The Pro-Data Unlimited Perspective
On the opposite end of the spectrum, leading Bitcoin Core contributor Jameson Lopp takes a different stance. Lopp suggests that OP_RETURN limits are ineffective in preventing spam in practice. His argument indicates that such technical filters only provide superficial protection without addressing the root problem.
This debate reflects a deep tension within the Bitcoin community between those prioritizing data flexibility and those concerned about long-term network integrity. The fate of BIP-110 will set an important precedent for how the Bitcoin community balances innovation with sustainability. The decisions made in the coming months will determine whether the Bitcoin ecosystem remains true to its decentralization commitments or gradually shifts toward concentration.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Proposal BIP-110 Bitcoin Gains Continued Support from Nodes Amid Community Tensions
A new wave of support for Bitcoin Improvement Proposal 110 (BIP-110) is transforming the landscape of technical discussions within Bitcoin. Current data shows that 583 out of a total of 24,481 active nodes are now running this protocol, representing 2.38% of the complex global Bitcoin network.
How Many Nodes Have Adopted Standard 110?
According to Cointelegraph reports, Bitcoin Knots has become the main software implementation driving the adoption of BIP-110 during the ongoing soft fork phase. Standard 110 is specifically designed to: limit transaction output size to a maximum of 34 bytes while setting the OP_RETURN data limit at 83 bytes. This temporary implementation phase is scheduled to last for the next twelve months, with possible modifications or extensions depending on community response and network monitoring results, as outlined on the official proposal’s GitHub page.
What Is the Root of the Dispute: OP_RETURN and Spam Concerns?
The OP_RETURN script code, which allows embedding arbitrary data within the blockchain, has become a hot topic of intense debate within the Bitcoin ecosystem. This conflict has escalated sharply since the release of Bitcoin Core version 30, which made a controversial decision: removing the previous OP_RETURN data limit of 83 bytes.
This innovative pull request—first proposed in April 2025—triggered a wave of significant rejection from various community segments. When the update was finally launched in October 2025, harsh criticisms questioned the consequences of removing the arbitrary data restrictions. Opponents warned that lifting this limit would open wide avenues for mass spam on the already full Bitcoin ledger.
Centralization: A Long-Term Threat to Bitcoin’s Decentralization
Deeper concerns go beyond simple spam issues. A significant increase in arbitrary data volume would raise storage burdens for every user running a full Bitcoin node. Growing infrastructure costs could potentially push network power consolidation into the hands of a few large-resource players.
Bitcoin’s fundamental value proposition lies in its ability to operate on standard consumer hardware—ordinary personal computers owned by average users. However, if technical requirements continue to rise, Bitcoin’s vision as a truly decentralized monetary system will be compromised. An analogy made by one commentator, Matthew Kratter, is very illustrative: spam acts like parasitic plants draining their host trees, gradually weakening the fundamental structure of the network itself.
A Different Voice: The Pro-Data Unlimited Perspective
On the opposite end of the spectrum, leading Bitcoin Core contributor Jameson Lopp takes a different stance. Lopp suggests that OP_RETURN limits are ineffective in preventing spam in practice. His argument indicates that such technical filters only provide superficial protection without addressing the root problem.
This debate reflects a deep tension within the Bitcoin community between those prioritizing data flexibility and those concerned about long-term network integrity. The fate of BIP-110 will set an important precedent for how the Bitcoin community balances innovation with sustainability. The decisions made in the coming months will determine whether the Bitcoin ecosystem remains true to its decentralization commitments or gradually shifts toward concentration.