Bitcoin Core to Lift OP_RETURN Guardrails in Next Update: Move Is 'Aligned With Bitcoin's Ethos'

A recent statement from the Bitcoin Core team revealed that the controversial change to lift the current guardrails on OP_RETURN restrictions will be implemented in the next version. The statement explains that the decision was made because it aligns with the current bitcoin ethos.

Bitcoin Core Decides to Lift OP_RETURN Guardrails Even After Controversy

The Bitcoin Core team has decided to move ahead with one of the most controversial changes proposed in years. According to a statement prepared by developer Gregory Sanders, made in the name of the whole Bitcoin Core team, the next version of the node software will “by default, relay and mine transactions whose OP_RETURN outputs exceed 80 bytes and allow any number of these outputs.”

Sanders specified that the limit had outlived its utility, explaining that the team was determined to lift this cap as it was counterproductive, ineffective, and “damaging.”

As it was explained by some core contributors several times during this public debate, the current guardrails were being outsmarted in several ways, including the utilization of private mining accelerators that don’t enforce these policies.

“Large-data inscriptions are happening regardless and can be done in more or less abusive ways; the cap merely channels them into more opaque forms that cause damage to the network,” Sanders explained.

For this reason, the core team chose to lift the OP_RETURN cap, as it “aligns default policy with actual network practice, minimises incentives for harmful workarounds, and simplifies the relay path.”

Knots, an alternative bitcoin client, has experienced a rise in its implementation, recently reaching 1,572 listening nodes. Nonetheless, Bitcoin Core remains the most widely used bitcoin software, driving 20,193 public listening nodes according to Coin Dance numbers.

However, the core team acknowledges that the decision earned broad but not unanimous support, and encouraged dissenters to run their own modified software to enforce new and stricter policies. The debate before the change encompassed accusations of developers colluding with companies and the rise of the discussion of what constitutes “spam” in the context of the bitcoin blockchain.

Read more: Facilitating Spam Attacks or Nothing Burger? Drama Ensues Over Changes to This Bitcoin Guardrail Feature

Read more: OP_RETURN Conflict: Ocean Mining Accuses Core Developers of Colluding to Fill Bitcoin With ‘Spam’