Bitcoin News: Who Will Win the “OP_RETURN” War?

Bitcoin developers are arguing over a proposal to remove the 83-byte limit currently set for the OP_RETURN function. Who will win? Will the network hard fork? The last time Bitcoin hard forked was in September 2017. 

There is a storm in the Bitcoin community that risks leading to another hard fork, a major one in nearly eight years. A technical debate over a single protocol feature is erupting into a full-blown ideological war. At the heart of this conflict is pull request 32359, which seeks to remove the 83-byte data limit on the Bitcoin OP_RETURN function.

DISCOVER: 20+ Next Crypto to Explode in 2025 

The “OP_RETURN” War: Who Will Win?

Since the activation of this data limit, Bitcoin transactions have been able to hold small amounts of non-financial data.

Now, a proposal aims to remove this limit, allowing files larger than 83 bytes to be embedded directly in Bitcoin transactions. This change would directly impact the size of the blockchain and node operations.

The discussion has spiraled into a public spectacle, with supporters and opponents clashing, each adamant that their position is best for the network.

Any change will either align Bitcoin with Satoshi Nakamoto’s vision as a financial layer or transform it into a general-purpose blockchain bloated with potentially useless files.

In this OP_RETURN War, rifts are emerging, reminiscent of the Bitcoin clash of September 2017, which birthed Bitcoin Cash after a hard fork. Although Bitcoin Cash has faded, it is still one of the best cryptos to buy in 2025.

To understand why this debate is crucial, one must know why the OP_RETURN function was introduced.

First implemented in 2014, this function was designed as a lightweight way to attach transaction data, such as timestamps, to Bitcoin transactions.

While part of the transaction, its goal was to keep the network “light” and unclogged. It was capped at 83 bytes to prioritize essential financial data. However, debates remain about whether this limit promotes utility, efficiency, or both.

Pull Request 32359, proposed by Peter Todd and Antoine Poinsot of Chaincode Labs, seeks to lift this cap. Instead of 83 bytes, anyone could embed files of any size, effectively storing them on-chain.

Which Way Bitcoin?

Supporters argue the limit is outdated, especially after the activation of Taproot enabled inscriptions and innovations like tokenization.

Additionally, private mempool broadcasting providers, such as MARA Slipstream, already allow larger files to be stored on-chain.

In a post on X, Todd stated that the limit makes Bitcoin “less efficient” and that lifting it would restructure OP_RETURN’s full-fee structure.

Meanwhile, Bitcoin purists, including core developer Luke Dashjr, call the proposal “utter insanity,” warning it could turn Bitcoin into a data dump.

They point to the inscriptions boom, which spiked transaction fees and strained nodes.

Removing the limit and adding non-essential data could undermine Bitcoin’s mission as “internet money” and make the network worthless.

This group urges the community to enforce strict regulations to preserve Bitcoin’s core purpose.

For now, everyone is curious how the community will receive this proposal. As Bitcoin is more than code: It is a movement worth over $1.88 trillion.

Therefore, the debate will only intensify with time, and interesting explanations will be forwarded. Still, whether or not a hard fork is on the cards remains to be seen.

DISCOVER: 7 Best Meme Coin ICOs & Presales to Invest in 2025

Bitcoin OP_RETURN War: Will There Be A Hard Fork?

  • Pull request 32359 proposes removing the 83-byte data limit set for the OP_RETURN function in Bitcoin 
  • Supporters think the limit is outdated and bypassed after Taproot activation 
  • Opposers maintain that lifting this limit will allow people to embed spam files 
  • Will this war lead to a hard fork? 

The post Bitcoin News: Who Will Win the “OP_RETURN” War? appeared first on 99Bitcoins.

editorial staff