The recent release of Bitcoin Core v30.0 has ignited a significant discussion within the Bitcoin community, sparking controversy and dividing opinions among prominent figures. While the update brings various changes, one particular alteration has become the central point of contention, leading some to strongly advise against upgrading.
The Core of the Controversy
The main point of disagreement surrounding Bitcoin Core v30.0 stems from its increase in the OP_RETURN data limit, expanding beyond the previous 80-byte cap. The new release defaults the datacarriersize to 100,000 bytes, a substantial increase. This change has drawn sharp criticism from notable figures like Bitcoin pioneer Nick Szabo, who explicitly recommended against upgrading to v30, instead suggesting the use of alternatives such as "Knots" as a temporary measure. Several other community members have echoed his concerns, viewing the expanded data allowance as potentially problematic for the network.
Clarifying OP_RETURN's Origins
Amidst the community split, Bitcoin pioneer and Blockstream CEO Adam Back provided a crucial clarification regarding OP_RETURN. Countering the narrative that this function is a new or problematic addition, Back highlighted that OP_RETURN is, in fact, an "old" Satoshi feature, dating back 15 years. This function serves as a special data storage mechanism within blockchain transactions, allowing users to attach additional information. Back's statement suggests that while the increased limits in v30.0 might be a concern for some, the underlying OP_RETURN functionality itself is an integral and long-standing part of Bitcoin's design.
