Bitcoin Core v30 Sparks Debate Over Data Limits and Fork Rumors

The latest version of Bitcoin’s reference software, Bitcoin Core v30.0, has officially launched—bringing major performance upgrades, lower fees, and a wave of controversy. While the update introduces technical improvements across nodes and wallets, one change has sharply divided developers: an expanded data limit that some fear could expose the Bitcoin network to legal and ethical risks.

The new release allows OP_RETURN outputs—the function enabling users to embed data in Bitcoin transactions—to store up to 100 kilobytes, a dramatic jump from the previous 83-byte cap. Developers say the change improves functionality for on-chain metadata such as digital certificates or art references. Critics, however, warn that it could also be used to insert harmful or illegal content directly into Bitcoin’s immutable ledger.

Bitcoin Core maintainers emphasize that the update affects only mempool policy, not Bitcoin’s consensus rules, meaning that no hard fork is required for compatibility. Nodes can still choose to lower their individual OP_RETURN limits. Yet the concern remains that, if widely adopted, larger data allowances could increase blockchain bloat and expose node operators to liability for hosting banned material.

Beyond OP_RETURN, Bitcoin Core v30 brings several key upgrades. Transaction fees can now drop as low as 0.1 sat/vB, reducing costs for users and improving efficiency. Legacy BerkeleyDB (BDB) wallets are no longer supported, replaced by more secure descriptor wallets with simplified backup and import commands. The update also introduces TRUC transactions, designed to minimize conflicts while pending confirmations.

The release adds a streamlined command-line interface—now unified under thecode>bitcoin/code> command—and enhances miner connectivity through a new PC Mining Interface, allowing faster block template requests. Visual improvements include a transition from Qt5 to Qt6 for the graphical interface, new dark mode support for Windows, and optimized Metal graphics for macOS.

The rollout, however, has reignited old philosophical divisions within the Bitcoin community. Veteran developer Luke Dashjr, who leads the alternativeBitcoin Knotsproject, voiced strong opposition to the expanded data capacity, arguing that Bitcoin should “prioritize financial utility, not file storage.” Following leaked messages alleging he might launch a hard fork to resist the changes, Dashjr dismissed the claims as “fake news,” reiterating that “there is no fork” planned—though he maintained his criticism of what he called “Core30 apologists.”

After initial backlash, Bitcoin Core maintainer Ava Chow reintroduced configurability for OP_RETURN limits just before the release, easing concerns that node operators would be forced to accept larger data sizes. Still, the controversy underscores a recurring tension within the Bitcoin ecosystem: how to balance innovation with purity, and scalability with the network’s original monetary focus.

For now, the long-awaited upgrade is live, and Bitcoin’s blockchain remains unified. Whether v30 becomes a benchmark for progress or a cautionary tale of overreach will depend on how the global network chooses to adopt—or resist—its new capabilities.