Bitcoin Core v30: The Change that Threatens Network Unity

Must every change, even at the core of a reputedly stable ecosystem like Bitcoin’s, systematically trigger controversy? The release of Bitcoin Core version 30.0 has rekindled tensions between purists and innovators. While some applaud more flexible features, others see a threat to the very essence of the network. At the heart of the debate: OP_RETURN. This small command, trivial for some, explosive for others, has reignited a conflict as old as Bitcoin itself.

Bitcoin Core v30: a technical revolution dividing the community

With its major update, Bitcoin Core v30 introduces several new features, but one alone causes teeth-grinding: the increase of the OP_RETURN data size up to 100,000 bytes. In other words, the Bitcoin network can now accommodate far more non-financial information in its transactions. A revolution for some, heresy for others.

This feature, formerly limited to 80 bytes, was mainly used to mark transactions or include short messages. Now, it could allow inserting massive, even multimedia content. The result: part of the community fears a transformation of the network into a giant storage.

On X, Ox HaK does not mince words: 

Bitcoin Core v30 is a mistake. Removing the OP_RETURN limits opens the door to an overload of useless data, inscriptions, and a fee explosion that harms ordinary users. Bitcoin’s strength lies in its minimalism — not in turning its base layer into a playground for experiments.

What history reminds us: beware of déjà vu

This debate around version 30 painfully recalls the 2017 Blocksize Wars. Back then, a simple divergence over block size led to Bitcoin splitting into two distinct chains, giving birth to Bitcoin Cash. The spirit of division hovers again.

But this time, the change is not in the protocol consensus, but in the node software. And that changes everything. Purists feel betrayed. For them, the massive addition of data will bloat the chain, incur costs for nodes, and move Bitcoin away from its original mission.

Alex Bergeron, leader at Ark Labs, instead embraces a radically different vision: 

I fully intend to use all the extra space offered by OP_RETURN and I WILL USE IT to make Bitcoin more like Ethereum, but better.

Behind this provocative statement lies a fundamental conflict: Should Bitcoin remain a peer-to-peer electronic currency, or can it become a platform for complex applications? This dilemma is now head-on.

Bitcoin Knots, the refuge for those who refuse compromise

Faced with this shift, a growing portion of node operators choose not to follow. Their solution? The alternative software Bitcoin Knots, which maintains the old OP_RETURN limits at 80 bytes. A clear way to say “no” without leaving the network.

According to BitRef data, more than 21% of Bitcoin nodes already use Knots. A rising number.

Although Luke Dashjr, its creator, has remained quiet since v30’s release, he has shared numerous criticisms against the update, notably about legal risks related to hosting illicit content.

Nick Szabo, a historic figure in the sector, was among the first to warn about legal risks. According to him, without mechanisms enabling nodes to easily delete illegal content, operators could be held criminally liable.

Key takeaways of Bitcoin Core version 30

• The new default datacarriersize is 100,000 bytes, compared to 80 previously;
• OP_RETURN can now be used multiple times in the same transaction;
• Bitcoin Knots keeps the old limit at 80 bytes;
• 5 low-severity vulnerabilities were fixed in this version;
• Versions 27.x and earlier are now deprecated (EOL).

Already last May, the extension of OP_RETURN had sparked much ink. Several developers denounced a betrayal of Bitcoin’s principles. The return of the debate, with this version 30, shows how much this simple command remains an ideological battleground. Bitcoin advances, but not everyone wants to follow the same path.