Developers remove the deprecation warning for datacarriersize parameters following protests from Knots node operators.
Just hours before the scheduled release of Bitcoin Core v30, developers reversed course on the planned deprecation of OP_RETURN configuration options, one of the most debated changes in the update.
Pull request #33453 was merged into the main Bitcoin Core branch on GitHub yesterday evening thanks to maintainer Ava Chow. This move responds to community pressure, particularly from Knots node operators, who strongly opposed the planned removal of datacarriersize configurability.
According to many Knots node operators, most node mempools should automatically reject by default transactions containing large amounts of data unrelated to on-chain bitcoin transfers. Their goal is to avoid overburdening node operators with storing and propagating arbitrary data across the network for non-monetary uses of BTC.
What changes in version 30
Bitcoin Core v30 will continue to increase the default datacarriersize limit for OP_RETURN from roughly 80 bytes in the previous version to 100KB. Users could already manually adjust this parameter in previous versions, and they will still be able to do so in v30.
The key update from PR #33453 is the removal of the deprecation warning that had been included in the documentation. Originally, Bitcoin Core v30 was to include a message alerting users of the upcoming removal of the datacarrier and datacarriersize configuration options. With the integration of PR #33453, this warning has been removed, and the deprecation of these options is no longer planned.
