Introducing the latest release of the Bitcoin Core software: version 30.0! This updated version signifies a significant leap forward in the development of the Bitcoin network, following the previous release of v29. The previous versions, especially those in the 27.x series and older, are now officially considered “End of Life.” Users can find complete release details in the release notes, which inform users that no further updates will be provided for these legacy versions. The Bitcoin community has also shared news about the launch on X.
Unveiling Bitcoin Core Version 30
A particularly notable change in v30 is the revised approach to the OP_RETURN function. This feature enables the inclusion of provably unspendable outputs containing arbitrary data. The update raises the default limit of -datacarriersize to a robust 100,000 bytes and allows for multiple OP_RETURN outputs in a single transaction, enhancing efficiency in data handling. For those who prefer the previous default setting, transitioning back is simple: “By applying -datacarriersize=83, users can revert to the limits established in earlier versions.” The new aggregate size limit pertains to all OP_RETURN outputs within a transaction.
This increase in size has ignited discussions among developers and node operators regarding the direction of Bitcoin’s policy framework. Proponents of the change see it as a neutral upgrade that gives operators the freedom to manage data size according to their needs. Critics argue that this may open the door to unwanted non-monetary uses and increase the risk of network congestion, thus impacting storage and verification for nodes.
Version 30 also introduces a variety of enhancements related to network performance, wallet functionalities, and user tools. The peer-to-peer (P2P) layer has seen improvements, particularly in the realm of package relay, which now supports common configurations like grandparent-parent-child setups, ensuring better reliability when only a single ancestor transaction requires a fee increase. The new transaction orphanage system introduces elevated DoS limits based on total entries and weighted contributions across peers, replacing the older -maxorphantx parameter.
For miners, this update brings forth an experimental IPC mining interface through the new umbrella bitcoin command, alongside convenience aliases such as “bitcoin node,” “bitcoin gui,” and “bitcoin rpc.” These enhancements also ensure that existing binaries remain functional. Users on Windows can once again utilize external signing, and adjustments to the coinstats index have been made to prevent overflow issues previously observed on the default Signet, necessitating a one-time resync.
Fee policies are also evolving with this update. The default minimum block feerate is now set to 0.001 sat/vB, while both minimum relay and incremental relay feerates default to 0.1 sat/vB. It is critical to note that widespread adoption of these new defaults is essential for successful propagation and confirmations; wallets themselves do not automatically adjust feerates without manual adjustments.
The discourse surrounding the OP_RETURN modifications has permeated public discussions, drawing attention from seasoned contributors and publication editors alike. While advocates view Bitcoin Core 30.0’s expanded data-carrier limit and the newly permitted multiple OP_RETURN outputs as adjustable policies, detractors warn of potential misuse that could detract from Bitcoin’s fundamental monetary purpose, potentially leading to a hard fork.
As of the latest market updates, BTC was trading at $114,455.
