Bitcoin Core builders reversed their plan to deprecate the person configurability of OP_RETURN’s default datacarriersize simply hours earlier than the scheduled launch of Core model 30 (v30), one of the crucial controversial and broadly publicized modifications to Bitcoin’s dominant software program for 1000’s of node operators.
Pull request (PR) 33453 was merged by Core maintainer Ava Chow into Bitcoin Core’s grasp department by way of GitHub yesterday night New York time.
The eleventh-hour lodging signaled a slight victory for a dissident motion led by Knots node operators who’ve vocally protested Core’s easements of OP_RETURN’s datacarriersize.
Within the view of many Knots node operators, most nodes’ reminiscence swimming pools (mempools) ought to reject transactions by default carrying giant quantities of information unrelated to the on-chain motion of bitcoin (BTC).
Relatively than burden node operators with storing and relaying arbitrary information across the community for non-currency makes use of of BTC, defaults ought to deter such arbitrary information storage in OP_RETURN outputs.
Though Core v30 software program will nonetheless improve OP_RETURN’s datacarriersize from lower than 90 bytes to 100KB for its default mempool, v30 will retain and never plan to deprecate the flexibility for customers to manually modify that cap on the amount of arbitrary information that OP_RETURN outputs will carry.
Deprecation of datacarrier and datacarriersize configuration choices was initially deliberate for launch this October in Core v30.
Nonetheless, because of the profitable assessment and merge of PR 33453, deprecation of person configurability is now on maintain indefinitely.
The last-minute coverage reversal doesn’t undo all the controversial modifications from v29 going into v30.
