- Bitcoin Core developers reversed a plan to remove user control over OP_RETURN’s datacarriersize hours before releasing version 30.
- The change means node operators can still configure how much data their nodes accept in OP_RETURN transactions.
- This policy update came after a pull request was merged by maintainer Ava Chow on GitHub.
- The reversal follows pressure from a group led by Knots node operators, who opposed the move to limit configurability.
- Version 30 of Bitcoin Core will still raise the default datacarriersize limit to 100KB, but the option to change it remains available.
Bitcoin Core developers have decided to keep user configurability of the OP_RETURN datacarriersize after widespread debate, just hours ahead of the planned release for Core version 30. This decision reverses an earlier plan that would have removed the ability for node operators to manually set the limit on data stored inside OP_RETURN transactions.
The updated plan became official when Core maintainer Ava Chow merged the pull request into the master branch of Bitcoin Core on GitHub. This change keeps the existing configuration options for thousands of node operators, despite the original schedule to phase them out with the v30 release in October.
This late change is considered a partial win for node operators supporting the Knots branch, who argued against what they described as a relaxation on the rules for OP_RETURN data limits. Knots operators said that, by default, node networks should “reject transactions by default carrying large amounts of data unrelated to the on-chain movement of bitcoin (BTC).” They worry that large volumes of arbitrary data could require operators to process unnecessary or even inappropriate content.
Core version 30 will still increase the default OP_RETURN datacarriersize limit from under 90 bytes to 100KB, allowing larger pieces of data to be stored within Bitcoin transactions. However, according to the latest update, the ability for individual node operators to set their own datacarriersize will remain, and plans to remove this configurability have been put on hold indefinitely.
Deprecation of the datacarrier and datacarriersize configuration options, once scheduled for October’s v30 release, will no longer move forward as previously planned. While the new default limits and other changes from Core version 29 remain, this policy shift means node operators retain direct control over the data accepted by their network mempools.
For more technical details or to see the official code change, view the pull request on GitHub. The latest version reflects a balance between streamlining network operations and maintaining flexibility for node operators.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- BitMEX CEO: DEX Hype May Fade as Incentive Models Prove Fragile
- BRICS Accelerates Dollar Alternatives With Gold, New Payment Systems
- Pfizer Shares Jump After Trump Deal for Discounted Drug Sales
- Sei Expands in Asia With Japan License, Eyes Institutional Growth
- Federal Government Shuts Down as Senate Deadlocks on Funding
