Bitcoin Core devs schedule OP_RETURN change for October

Bitcoin Core developers have scheduled the release of version 30 for October, which will significantly increase the default OP_RETURN data carrier limit in the mempool from 84 bytes to nearly 4MB. This change, led by developers like Antoine Poinsot and Peter Todd, has sparked controversy, with conservatives like Luke Dashjr arguing that it prioritizes data storage over BTC movement validation, potentially bloating the blockchain; while node operators can manually adjust the setting, the default change is expected to be widely adopted.

Analysis

A significant technical change is scheduled for Bitcoin Core with the October release of version 30, which will increase the default OP_RETURN data carrier limit from under 84 bytes to nearly 4MB. This modification, spearheaded by 'progressive' developers like Antoine Poinsot and Peter Todd, aims to allow larger amounts of non-financial data to be more easily queued across nodes. However, this move has been met with strong opposition from 'conservative' developers such as Luke Dashjr, who argue that it is antithetical to Bitcoin's primary purpose of validating BTC movement and could lead to irresponsible data storage and blockchain bloat. While the new version will allow node operators to manually adjust the -datacarrier and -datacarriersize parameters, the change in the default setting is crucial, as most operators are expected to use default configurations. This internal dispute, characterized by strong rhetoric from both sides, reflects a fundamental disagreement on Bitcoin's utility and operational priorities. The 'mixed' sentiment and 'uncertain' tone indicated by signals underscore the contentious nature of this update and its potential, yet unclear, ramifications for the network's future functionality and the broader Bitcoin ecosystem.

Key Decisions for Investors

• Investors should closely monitor the October release of Bitcoin Core version 30 and its adoption, as the substantially increased default OP_RETURN data limit could introduce new use-cases for data storage on Bitcoin but also potential network performance issues or philosophical divergences.
• Consider the long-term implications of increased data embedding on the Bitcoin blockchain, including potential for chain bloat, higher operational costs for node runners which might affect decentralization, and the impact on transaction fees and confirmation times.