Bitcoin Core v30 Launches with OP_RETURN Expansion, Dividing the Community
The release of Bitcoin Core version 30 has ignited a wave of debate and division within the Bitcoin ecosystem. Rolled out over the weekend, the update introduces a number of architectural, performance, and security enhancements for node operators. However, the most contentious change is the expansion of the OP_RETURN data field from 80 bytes to a staggering 100,000 bytes—an increase that many believe could reshape the way Bitcoin is used.
This change is not a protocol-level alteration, but it significantly impacts how data can be stored on the Bitcoin blockchain via OP_RETURN, a feature designed to embed arbitrary data in transactions. Supporters of the update see it as a step toward more complex decentralized applications (dApps) and broader blockchain utility. Critics, however, argue that this shift strays from Bitcoin’s original vision as a peer-to-peer digital cash system, raising fears about network congestion, rising operational costs, and legal liability for node operators.
New Features Highlighted in Bitcoin Core v30
Among the technical improvements in Bitcoin Core v30 are optional encrypted peer-to-peer connections, enhancing privacy between nodes. The developers also introduced performance upgrades and refined fee rate calculations. Additionally, the update marks the end of support for versions 27.x and older, which will no longer receive security patches or updates.
But it’s the OP_RETURN modification that has overshadowed these improvements. By raising the data limit to 100 KB, Bitcoin Core now allows significantly more non-financial information to be embedded in its blockchain—opening the door for richer applications, including NFTs, smart contracts, and identity systems directly on Bitcoin.
OP_RETURN: Innovation or Deviation?
Proponents of the change, such as Ark Labs’ ecosystem lead Alex Bergeron, see this as an opportunity to make Bitcoin more versatile—comparing the potential to Ethereum-like capabilities, but with Bitcoin’s security and decentralization. Bergeron stated his intention to fully utilize the expanded OP_RETURN space, suggesting this could usher in a new era of innovation within the Bitcoin ecosystem.
Satoshi Labs co-founder Pavol Rusnak also voiced support, stating that he had upgraded to v30 due to its “peer-reviewed code” and “solid engineering decisions.” From his perspective, the long-term benefits of increased data capacity outweigh the temporary discomfort.
However, not everyone shares that optimism. Critics argue that the original purpose of OP_RETURN was never to store large data payloads but to enable lightweight metadata or signaling. Expanding this field so dramatically, they argue, could lead to blockchain bloat—making it harder and costlier for individuals to run full nodes, thereby threatening Bitcoin’s decentralization.
Legal and Operational Concerns
One of the most vocal opponents of the update is cryptography pioneer Nick Szabo, who warned of potential legal consequences for node operators. He highlighted the risk of inadvertently storing illegal content on-chain, which could lead to criminal liability in jurisdictions that hold data hosts accountable.
Szabo recommended that node operators avoid upgrading to Bitcoin Core v30 and instead switch to alternative node software like Bitcoin Knots, which allows them to enforce the original 80-byte limit. He emphasized the need for mechanisms that would let archival node operators safely erase problematic data without compromising the integrity of the network.
Bitcoin Knots Gains Momentum
Bitcoin Knots, a fork of Bitcoin Core maintained by developer Luke Dashjr, has seen a growing user base in response to the v30 release. According to recent network data, Knots now accounts for over 21% of all active Bitcoin nodes, with more than 5,100 instances currently online.
Although Dashjr has not publicly commented on the v30 rollout, he has previously criticized the direction of recent Bitcoin Core updates. His software offers more conservative defaults and granular control over data policies—features that appeal to purists who want to preserve Bitcoin’s foundational principles.
Echoes of the 2017 Block Size Wars
The controversy surrounding the OP_RETURN expansion has rekindled memories of the 2017 block size debate, which culminated in the creation of Bitcoin Cash. Though the current dispute does not involve a hard fork—yet—the fundamental disagreement is similar: should Bitcoin prioritize minimalism and financial utility, or embrace broader use cases through increased data capacity?
Those in favor of the change argue that Bitcoin must evolve to remain competitive in a blockchain landscape increasingly dominated by platforms that support more complex functionality. Opponents warn that straying too far from Bitcoin’s core mission could erode its uniqueness and security model.
Implications for Decentralized Applications
Expanding OP_RETURN may unlock new use cases for Bitcoin, such as decentralized identity, timestamping services, and even on-chain messaging systems. Developers now have a much larger canvas for building data-driven protocols directly on Bitcoin’s secure infrastructure. However, scalability remains an open question, as larger transactions could contribute to mempool congestion and higher transaction fees.
Moreover, without consensus on how much non-financial data should be allowed on-chain, future updates could ignite even more intense debates, potentially leading to further fragmentation within the developer and node operator communities.
What Node Operators Should Consider
For those running Bitcoin nodes, the decision to upgrade to v30 isn’t straightforward. While the update brings clear technical improvements, the expanded OP_RETURN field introduces new risks—both technical and legal. Operators need to weigh the benefits of increased functionality against the potential downsides of hosting unwanted or illicit data.
One alternative is to use customizable node software like Knots, which allows for stricter data policies. This approach enables operators to participate in the network while maintaining control over what data they are willing to store.
Looking Ahead
As the dust settles around the Bitcoin Core v30 launch, the broader community faces a critical question: should Bitcoin remain narrowly focused on financial transactions, or embrace a multifunctional role in the blockchain ecosystem?
The answer may not come easily. But what’s clear is that Bitcoin’s path forward will continue to be shaped not just by code, but by the philosophical and ideological values of its global user base.
Whether v30 turns out to be a leap forward or a divisive misstep remains to be seen. What’s certain is that the debate it has sparked will influence Bitcoin’s development trajectory for years to come.