Bitcoin Core version 30.0 has officially been released, representing a significant milestone for the network’s most widely used full node software. This update not only introduces several technical enhancements but also signals the retirement of legacy versions 27.x and earlier, which are now considered “End of Life” and will no longer receive updates or patches. The new version is available for download, with full release notes and documentation published by the Bitcoin Core development team.
One of the most discussed and controversial changes in v30 centers around the OP_RETURN script path—a feature that enables embedding arbitrary data in the blockchain via provably unspendable outputs. The update increases the default -datacarriersize limit to 100,000 bytes, a substantial jump from previous limits. Moreover, it now allows for multiple OP_RETURN outputs in a single transaction to be relayed and mined, a decision that has sparked debate among developers, miners, and node operators.
While the update offers flexibility by allowing node operators to revert to the previous 83-byte limit using the -datacarriersize=83 flag, the implications of this change have triggered heated discussions. Supporters argue that the move preserves decentralization by empowering individual operators with more control over their nodes’ behavior. On the other hand, critics are concerned that the relaxed constraints could encourage spammy or non-monetary uses of the blockchain, increasing storage demands and potentially undermining Bitcoin’s core purpose as a monetary system.
The broader question emerging from this update is philosophical: should Bitcoin’s infrastructure support arbitrary data storage, or should it strictly prioritize monetary transactions? This tension between flexibility and purity of function has long divided the Bitcoin community, and the changes in v30 have reignited that conversation.
Beyond the OP_RETURN modifications, Bitcoin Core v30 introduces a range of technical improvements across the network, wallet functionality, and developer tools. Notably, enhancements to the peer-to-peer (P2P) layer improve how transaction packages are relayed. Complex transaction structures, such as those involving grandparent-parent-child configurations, can now propagate more efficiently even when only one ancestor requires a fee bump.
The transaction orphanage system has also undergone a revamp. New denial-of-service (DoS) protections have been implemented by setting limits based on the total number and weight of orphan transactions per peer. This replaces the older -maxorphantx setting, offering a more robust and flexible approach to managing orphaned transactions in the mempool.
For miners, v30 introduces an experimental inter-process communication (IPC) mining interface. This new system is accessible via a consolidated “bitcoin” command that includes aliases such as “bitcoin node,” “bitcoin gui,” and “bitcoin rpc.” These additions aim to make the interface more user-friendly while maintaining backward compatibility with older binaries.
Another important technical fix in this release addresses an overflow bug in the coinstats index under default Signet conditions. This issue required a reworking of the index and necessitates a one-time resynchronization from users to align with the updated format.
Fee policy defaults have also been adjusted. The minimum block feerate (-blockmintxfee) is now set to 0.001 satoshis per virtual byte (sat/vB), while the minimum relay and incremental relay feerates have been set to 0.1 sat/vB. These changes are designed to encourage greater fee efficiency, but the developers caution that unless these new defaults are widely adopted across the network, there is no guarantee of successful propagation or confirmation of transactions. Notably, wallet feerates remain unchanged unless explicitly configured by the user.
The controversy surrounding OP_RETURN has spilled beyond technical forums and into broader public discourse. Prominent voices within the Bitcoin ecosystem, including long-standing contributors and editorial leaders, have taken opposing positions. While some hail the data-carrier size expansion as a necessary evolution of Bitcoin’s flexibility, others warn it could compromise the network’s financial integrity and even provoke a contentious hard fork in the future.
Critics are particularly worried about the potential rise of on-chain data inscriptions, such as NFTs and digital artifacts, which could lead to blockchain bloat. This, they argue, places an increased burden on node operators who must store and validate this additional data, potentially raising the barrier to entry for running a full node and weakening decentralization over time.
Supporters, however, counter that Bitcoin should remain a neutral protocol that doesn’t discriminate against different transaction types. By allowing more complex data structures, they believe the network can support innovation, such as Layer 2 solutions, enhanced privacy tools, and new forms of digital ownership—all without compromising the base protocol’s security and reliability.
From a broader perspective, the v30 release underscores the dynamic tension between innovation and conservatism in Bitcoin’s development. As the protocol matures, decisions like the OP_RETURN expansion will likely continue to test the balance between flexibility and focus, decentralization and discipline.
In addition, the release sets the stage for further experimentation in Bitcoin node software. The introduction of modular commands and a cleaner interface hints at a future where running a Bitcoin node becomes more accessible to non-technical users. This aligns with the long-term vision of empowering individuals to participate in the network without relying on centralized intermediaries.
Looking forward, the impact of these changes will depend heavily on how miners, exchanges, and individual node operators choose to configure their systems. Since many of Bitcoin Core’s policies are adjustable at the node level, the actual network-wide behavior will emerge organically based on collective choices rather than centralized mandates.
In essence, Bitcoin Core v30 is more than just a software update—it’s a reflection of the ongoing dialogue about what Bitcoin is and what it should become. As the ecosystem continues to evolve, future releases will undoubtedly build on this foundation, shaping the trajectory of the world’s largest decentralized monetary network.