A small share of Bitcoin nodes now signal support for BIP-110, a temporary soft fork that limits transaction data at the consensus level. Data shows 583 of 24,481 nodes (2.38%) run the proposal, and the primary implementation is Bitcoin Knots, according to The Bitcoin Portal.
The soft fork sets transaction output size to 34 bytes and caps OP_RETURN data at 83 bytes. The proposal is scheduled to deploy for one year, with possible changes after that, as stated on the proposal’s GitHub page.
A public timeline and deployment details are available on BIP-110.org. The change responds to debate over arbitrary data limits and network resource use.
The removal of an OP_RETURN cap in Bitcoin Core version 30 followed a controversial pull request first proposed in April 2025 and merged in October 2025, linked in the original pull request. Critics warn that uncapped arbitrary data can increase storage costs and centralize node operation, while some defenders argue filters offer limited protection.
Advocate Matthew Kratter warned about spam risks, saying “It’s like one of those parasitical plants, like ivy, completely covering a tree, eating up the tree, and then the inner scaffolding collapses, and the ivy collapses because it’s basically destroyed the structure. This is what spam has the potential to do to Bitcoin.” Other contributors, including Jameson Lopp, have publicly argued that filters do little to stop spam, as posted on X.
