Bitcoin’s OP_RETURN Limit Removal Renews An Old Debate

Editorial Note: While we adhere to strict Editorial Integrity, this post may contain references to products from our partners. Here's an explanation for How We Make Money. None of the data and information on this webpage constitutes investment advice according to our Disclaimer.

Recently, a pull request in the Bitcoin Core GitHub repository caused some Bitcoin users to become angry with the software project that accounts for the vast majority of the nodes on the network. The change involved the removal of a size limit on the OP_RETURN functionality found in Bitcoin, and it brought forth one of the most contentious technical debates in Bitcoin since the block size controversy of the mid-2010s.

Developers and users have debated their views on this potential change, which still has not been accepted into the Bitcoin Core codebase, on social media and various other channels. And some users have gone as far as to switch from Bitcoin Core to an alternative Bitcoin full node implementation known as Bitcoin Knots.

While the current debate has revolved around a technical tweak to the Bitcoin Core software client, the reality is this is really part of a greater debate regarding the use cases that should be allowed on the Bitcoin network. Should Bitcoin operate strictly as a monetary network at the base layer or is there room for some alternative use cases that have mostly been found on other crypto networks, such as Ethereum and Solana, up to this point? Let’s take a closer look at the latest controversy and the history of this long standing debate amongst Bitcoin users.

Risk warning: Cryptocurrency markets are highly volatile, with sharp price swings and regulatory uncertainties. Research indicates that 75-90% of traders face losses. Only invest discretionary funds and consult an experienced financial advisor.

Is Bitcoin just money or can it be something else?

While the key area of contention during Bitcoin’s block size war was regarding whether or not small-value payments should be made directly on the base blockchain, another related area of debate revolved around whether exploration of alternative blockchain use cases should be allowed through additional opcodes or a more expressive scripting language. Many of those who were supportive of a hard-forking (not backwards compatible) increase to Bitcoin’s block size limit were also interested in the sort of crypto experimentation that was happening on Ethereum at the time, and they wanted to see those alternative use cases make their way back to Bitcoin.

However, the opposing view was that a key part of bitcoin’s value proposition was that it was extremely hard to change, which protected the system’s unwavering monetary policy that had been “set in stone” by Bitcoin creator Satoshi Nakamoto when the network launched in 2009. Additionally, a more flexible base layer could open the system up to more bugs and unintended consequences.

For example, Ethereum has been criticized for the outsized influence centralized stablecoins, such as Tether USD (USDT) and USD Coin (USDC), could have on the protocol rules. Additionally, systems that allow alternative tokens to be created, such as the aforementioned stablecoins, increase costs for those who wish to use the crypto network’s native token by bidding up the price of block space.

This is the key area of debate related to the recent Bitcoin Core pull requests related to OP_RETURN: Bitcoin as a monetary asset against Bitcoin as a development platform. This gets into the concept of spam on the network as well, as some Bitcoin users view transactions unrelated to using bitcoin as money as spam. For example, around 20% of the transactions on the Bitcoin network at one point were related to a system called Veriblock that allowed alternative crypto networks to hash checkpoints of their current blockchain state into the Bitcoin blockchain.

This specific debate has been on the rise over the past couple of years, as newer tokenization protocols, such as Ordinals and Runes, have led to sharp rises in Bitcoin transaction fees on multiple occasions. For some, it’s obvious that Bitcoin would be healthier if these sorts of non-bitcoin transactions were not allowed to proliferate.

How OP_RETURN comes into play

OP_RETURN is an opcode in Bitcoin that allows arbitrary data to be stored on the blockchain in a prunable manner. Storing data in the blockchain is useful for the sorts of alternative Bitcoin use cases discussed above that some users view as spam. The key aspect of the OP_RETURN opcode is that it tells nodes that the outputs associated with these transactions are unspendable, which means they do not necessarily need to be stored as part of the unspent transaction output (UTXO) set.

In 2014, a new meta protocol called Counterparty was launched. The idea was to enable the sorts of use cases found in other crypto networks today such as non-fundible tokens (NFTs) and alternative cryptocurrencies. There was some debate over how much data systems like Counterparty should be able to put into the blockchain, and the OP_RETURN limit was eventually raised to 80 bytes from the initial 40 bytes limit.

However, the contributors to Bitcoin Core were careful to not explicitly endorse the placement of arbitrary data in the blockchain.”Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere,” state the release notes from Bitcoin Core 0.9.0.

However, the current 80 bytes limit on OP_RETURN data is simply the default allowed by Bitcoin Core nodes and not a consensus rule. This means the limit could technically be avoided by a user bypassing the peer-to-peer network and communicating directly with a miner. A number of these sorts of non-standard transactions have been mined, and some miners and mining pools, such as Marathon with their Slipstream feature, have openly embraced these sorts of transactions in an effort to maximize revenue. At the recent Bitcoin 2025 conference in Las Vegas, three mining pools went as far as to make a commitment to mine nonstandard Bitcoin transactions in an effort to bring more use cases to Bitcoin via BitVM.

Without getting too deep into the technical weeds, the recent pull request made in Bitcoin Core would effectively remove the 80 bytes limit associated with OP_RETURN transactions. This would allow these previously non-standard transactions, which some users view as spam, to more easily proliferate around the Bitcoin network and find their way into blocks.

While much of the focus in the current debate has been on the potential for this change to enable more perceived spam to find its way into the Bitcoin blockchain, the reality is this change could also be somewhat helpful for layer-two networks that improve the monetary and financial use of bitcoin. Citrea is a commonly-referenced example here. And currently, the OP_RETURN size limit forces these protocols to find workarounds that can actually be seen as more wasteful to the Bitcoin network’s limited resources. Remember, OP_RETURN transactions are prunable and do not bloat the UTXO set.

In fact, many of the people who support the removal of the OP_RETURN size limit from Bitcoin Core do not support doing things like embedding images into the blockchain, as is the case with Ordinals-based Inscriptions. The problem is it can be difficult to filter out specific types of transactions on a network that is supposed to be permissionless and resistant to censorship.

What will happen next?

For now, the most likely path forward appears to be that Bitcoin Core will at least increase the OP_RETURN limit, although things are still very much up in the air. Whether it is removed completely or simply raised to allow some use cases, such as Citrea’s, to operate more efficiently is unclear.

Additionally, users may retain control over the ability to filter out larger OP_RETURN transactions; however, as previously stated, these transactions can still easily find their way into blocks through direct communication with miners. Whatever happens, those who wish to filter out larger OP_RETURN transactions can still alter their own Bitcoin Core node or run alternative software like Bitcoin Knots. However, it’s also clear the standard practices can be heavily influenced by the default settings in Bitcoin Core.

This debate over the OP_RETURN bytes limit may also be a precursor to future conversations around various covenants-related soft fork proposals. If layer-two Bitcoin networks that use OP_RETURN gain some popularity, there could be more demand for one of these soft forks due to their ability to improve the overall security model of some layer-two protocols. Discover what the proposed CTV and CSFS soft fork means for Bitcoin’s future scalability, security, and programmability.

With all this said, those who have been strongly opposed to the removal of the OP_RETURN limit are correct that users must remain vigilant in stomping out the unintended consequences of enabling more use cases on Bitcoin that have less to do with the bitcoin asset itself. Right now, the potential negative side effects of having a hugely-influential and centralized stablecoin issued on a crypto network are becoming less theoretical, as Ripple is attempting to acquire USDC-issuer Circle. Additionally, there are concerns that the financialization of bitcoin via the development of decentralized finance (DeFi) protocols on top of Bitcoin could lead to more frequent chain reorganizations at the base layer due to the phenomenon of maximum extractable value (MEV).

Bitcoin must retain the properties that differentiate itself from both the traditional financial system and the rest of the crypto market. It is the level of decentralization that the network has maintained and the difficulties associated with changing the protocol rules that underpin the crypto asset’s key value proposition as an apolitical, digital store of value. Other crypto systems that have taken endless shortcuts away from decentralization to attract users and have become increasingly built around centralized stablecoins have many competitors, but there’s only one Bitcoin.

We should prioritize protocol stability and cautious innovation

As someone deeply involved in Bitcoin infrastructure, I see the current OP_RETURN debate not just as a technical adjustment but as a reflection of Bitcoin’s ongoing identity challenge. This is less about data limits and more about direction: should Bitcoin remain focused on monetary utility, or open itself further to alternative use cases?

While the removal of the OP_RETURN limit might offer efficiencies for certain Layer 2 protocols, it also risks opening the network to misuse that could undermine its core value as a censorship-resistant store of value. Expanding functionality without clear boundaries can dilute the very qualities that make Bitcoin unique.

My view is simple: we should prioritize protocol stability and cautious innovation. Those who care about Bitcoin’s future should stay engaged, understand the implications of proposed changes, and participate actively in the consensus process.

Conclusion

Despite what some say, the removal of Bitcoin Core’s OP_RETURN limit from its transaction relay policy does not mean the end is near for the world’s largest and most popular cryptocurrency. However, Bitcoin users must understand what makes the system valuable in the first place for it to succeed over the long term, and those who are against the removal of the limit are making the case that the Bitcoin network will be healthier if it remains focused on the bitcoin asset itself. This desire to avoid mission creep and protect bitcoin’s fundamental value proposition will continue to shape technical debates in the future, and anyone who cares about the future of the cryptocurrency should educate themselves and get involved with the consensus process.

FAQs

What is OP_RETURN in Bitcoin?

OP_RETURN is an opcode in Bitcoin that allows users to store arbitrary data in the blockchain in the least harmful way possible. This opcode was introduced to Bitcoin in the early days, and it marks the outputs associated with a transaction as unspendable.

What is Bitcoin’s OP_RETURN limit?

There is no limit on the amount of arbitrary data that can be placed in an OP_RETURN transaction in Bitcoin. However, the Bitcoin Core OP_RETURN limit will not allow transactions that are larger than 83 bytes, 80 of which are available to the user for arbitrary data.

What is a Bitcoin opcode?

A Bitcoin opcode is a part of Bitcoin Script that handles transaction processing via specific instructions. For example, OP_CHECKSIG is the command that validates the signature on a transaction.

Is Bitcoin Script Turing complete?

No, Bitcoin creator Satoshi Nakamoto specifically limited the capabilities of Bitcoin Script for security reasons. This is in contrast to systems like Ethereum and Solana, which allow for more expressiveness and flexibility when writing applications.

Did you like the article?

Editors' Top Picks and Insights

8 hours ago Anastasiia Chabaniuk

Toncoin becomes Gram: Why Durov restored token's original name

#Pavel Durov #GRAM

1 day ago Kyle Torpey

Why Tether flipping Ethereum is a pivotal moment for crypto

#Tether #Ethereum

1 day ago Eugene Komchuk

MiCA deadline: Why crypto companies are leaving Europe

#Crypto #USDT

3 days ago Mikhail Vnuchkov

From “Holy Trinity” to WLD crash: How Arthur Hayes became a market-moving seller

#WLD #Arthur Hayes #Crypto #HYPE

4 days ago Eugene Komchuk

The world's first trillionaire: How Musk built his fortune on electric cars, space and AI

#Elon Musk #Crypto #AI #SpaceX #Tesla

5 days ago Ciaran Ryan

How precious-metals mining revival is reshaping portfolios in 2026

#Silver #Gold

All news

Team that worked on the article

Kyle began exploring Bitcoin in 2013, when public interest in cryptocurrencies was just beginning to grow. At first, it was more of a hobby.

Learn about our editorial policies

Chinmay Soni is a financial analyst with more than 5 years of experience in working with stocks, Forex, derivatives, and other assets. As a founder of a boutique research firm and an active researcher, he covers various industries and fields, providing insights backed by statistical data.

Mirjan Hipolito is a journalist and news editor at Traders Union. She is an expert crypto writer with five years of experience in the financial markets.

Ethereum

Ethereum is a decentralized blockchain platform and cryptocurrency that was proposed by Vitalik Buterin in late 2013 and development began in early 2014. It was designed as a versatile platform for creating decentralized applications (DApps) and smart contracts.

Cryptocurrency

Cryptocurrency is a type of digital or virtual currency that relies on cryptography for security. Unlike traditional currencies issued by governments (fiat currencies), cryptocurrencies operate on decentralized networks, typically based on blockchain technology.

CFD

CFD is a contract between an investor/trader and seller that demonstrates that the trader will need to pay the price difference between the current value of the asset and its value at the time of contract to the seller.

Index

Index in trading is the measure of the performance of a group of stocks, which can include the assets and securities in it.

Bitcoin

Bitcoin is a decentralized digital cryptocurrency that was created in 2009 by an anonymous individual or group using the pseudonym Satoshi Nakamoto. It operates on a technology called blockchain, which is a distributed ledger that records all transactions across a network of computers.

Top 5 companies for you