As Bitcoin Core developers have begun to propose a controversial increase in data storage capacity for Bitcoin script operation codes, the number of node operators whose changes have reached an all-time high is
Full node of Internet connection propagating knot-tagged blocks that reject proposed data limits It's doubled OP_Return since War began last month.
Core has 19,662 reachable nodes, and Knots is the second most popular client with 1,464.
On April 17th, Antoine Poinsot from ChainCode Labs reintroduced Peter Todd's Pull Request (PR) 28130. This asked core contributors to lift the approximate 80 bytes limit for DataCarrier Limit Op_Return Outputs.
The core contributors showed a willingness to move forward with the changes, software downloads, knots, and soared on another full-node client.
As the discrepancy split the Bitcoin community, Peter Todd eventually officially made this request as PR 32359. Plans to implement PR 32359 within a few days.
Knots' default Mempool does not lift the data carrier limit for OP_Return, even if Core decides. Therefore, according to Tracker Coin.Dance, reaching an all-time high of 6.5% yesterday, the growth of reachable knot nodes is a proxy for measuring resistance motion.
Bitcoin excellence and corporate profits
For larger data limit camps, an increase in DataCarrier in OP_RETURN simply normalizes the on-chain data storage limit by other methods of storing any data in a Bitcoin transaction, such as witness output.
Removing the 80-byte cap in op_return is, according to rhetoric, a simple and inconspicuous upgrade.
For many data-limited camps that run knots, the proposal is evidence that there are core developers of Bitcoin succumb to the profits of businesses and venture capital We use Bitcoin's largest Mempool as our distributed database.
Allowing easy proliferation and verification of images, music, games, contracts, and non-traditional data is a slippery gradient that undermines Bitcoin's primary purpose of replacing Fiat.
Read more: Moderator censored bitcoin developers get angry at op_return war
Bitcoin's 2025 op_return war decision time
A major conference for Bitcoin developers begins today in Austin. The main topics of discussion are PR 32359 and Mempool policy, with final decisions on the proposal being predicted instantaneously.
New comments arrive every hour on the Bitcoin-Dev mailing list, Github, Stackernews and X.
Bitcoin Full Node Operators can select the software client to validate and propagate transactions. The core is the main version with 19,662 reachable nodes at the time of publicationKnott, on the other hand, is the second most popular client with 1,464.
Other clients include BTCD, Bitcore, and UASF.
There are hundreds of thousands of full node operators around the world, but it is impossible to quantify the number of full nodes that actually exist. Bitcoin is dedicated to serving nodes with intermittent internet access, and nodes can always join their networks for free and depart.
Reachable node trackers such as Coin.Dance, Bitnodes, and Clark Moody use various types of internet monitoring tools to estimate the number of nodes that can be reached at any time.
