In a significant moment for Bitcoin’s protocol, Bitcoin Core v30 has officially launched after months of strong arguments and division within the community.
This update removes a long-standing restriction on the amount of arbitrary data that can be included in transactions, and it’s already changing the conversation about Bitcoin’s purpose, neutrality, and governance.
What the v30 Update Changes
At the heart of it all is OP_RETURN, a script opcode that enables bitcoin transactions to include arbitrary (read: non-spendable) data in the blockchain.
Bitcoin Core had a default cap of about 80 bytes for OP_RETURN payloads for a long time as a very primitive defense against bloat, spam, and abuse.
However, with the launch of version 30, that 80-byte cap has been lifted.
Now, by default, nodes can accept OP_RETURN outputs with much larger payloads—essentially uncapped—up to the limits set by transaction or block sizes (which can be close to 4 MB) in various configurations.
The configuration parameters (-datacarrier / -datacarriersize) are still available, allowing operators to set their own limits if they choose.
Additionally, version 30 relaxes earlier limits on how many OP_RETURN outputs can be included in a transaction.
It also changes the way data-heavy transactions are accepted into the mempool and updates the standard rules for including “nonfinancial” data.
The aim, as highlighted by supporters within the core development team, is to make default node policies more in line with how miners already handle large data payloads.
Thereby reducing the temptation to circumvent the public mempool through private miner agreements.
More News: Meanwhile, Bitcoin Life Insurer Raises $82M to Expand Savings
Criticism and Fears
It’s no wonder that this change has triggered a strong backlash and revealed the ideological splits within the Bitcoin community.
Critics are anxious that loosening or getting rid of the OP_RETURN cap might lead to a surge of non-financial data—think images, documents, metadata, and possibly even worse.
Nodes could be bombarded with “data spam” if there aren’t strict relay rules, which would put pressure on bandwidth, storage, and consensus processes.
One of the most prominent voices against this change is Luke Dashjr, the lead developer of the Bitcoin Knots client.
He argues that by using Core v30, node operators might unwittingly become part of the issue, helping to store and spread illegal content like CSAM (child sexual abuse material). He warns that this could seriously harm Bitcoin’s credibility and how the public views it.
Beyond the technical concerns, this discussion really touches on the essence of Bitcoin’s identity.
Purists believe Bitcoin should stick to being a straightforward monetary layer—simple, minimal, and focused solely on peer-to-peer value transfer.
They see the inclusion of large arbitrary data as a deviation from its core mission.
On the bright side, supporters argue that flexibility is key, pointing out that Bitcoin is already being utilized for more complex data-driven protocols (like layer-2 validation and cross-chain proofs).
They see this change as a way to encourage new ideas, allowing users to pay for block space and embed data as they see fit, rather than having the software impose restrictions.
Some critics, however, feel this shift aligns too closely with corporate interests or layer-2 solutions (like rollups), which they believe contradicts Bitcoin’s decentralized spirit.
The Bigger Picture
When we look at the bigger picture of Bitcoin’s development, v30 could be a pivotal moment—not merely a technical upgrade.
However, it marks a significant shift in the community’s approach to balancing its values of resistance to censorship, neutrality, innovation, and a focus on monetary aspects. The next few months will reveal whether v30 will bolster Bitcoin or deepen a fundamental divide.