The debate over Bitcoin’s OP_RETURN heats up, as developers of Bitcoin Core – the most popular node software – said they plan to scrap OP_RETURN entirely in the next release.
The OP_RETURN limit is an 80-byte cap on the amount of arbitrary data that can be embedded in a Bitcoin transaction using a special, unspendable output field.
“Large-data inscriptions are happening regardless and can be done in more or less abusive ways,” said Core contributor and Engineer at Blockstream Greg Sanders, known as ‘instagibbs,’ in a post on Github announcing the removal. “The cap merely channels them into more opaque forms that cause damage to the network.”
The debate centered on whether lifting the 80-byte OP_RETURN limit promotes transparency and simplifies data use on Bitcoin, or whether it opens the door to abuse, spam, and a shift away from Bitcoin’s financial focus.
On Github, Sanders added that enforcing the cap has created perverse incentives pushing users to embed data in fake public keys or spendable scripts. Removing the limit, he argues, “yields at least two tangible benefits: a cleaner UTXO set and more consistent default behavior.”
Not everyone is convinced. Core developer Luke Dashjr has long viewed inscriptions and other data storage as spam, and warned in April 2025 that this change was “utter insanity.”
Amid the controversy, Bitcoin Knots, also maintained by Dashjr, has seen growing adoption, hitting approximately 5% share of all nodes.
Bitcoin Knots, a more customizable fork of Bitcoin Core, appeals to users seeking greater control over what their nodes relay or store, including allowing users to reject non-payment transactions like inscriptions.
Some prominent thought leaders in the industry, like Samson Mow, are encouraging node operators not to upgrade their version of Bitcoin Core, or use Knots instead.
Sanders defended the removal of the cap as aligned with Bitcoin’s ethos: minimal, transparent rules.
“By retiring a deterrent that no longer deters,” he wrote, “Bitcoin Core lets the fee market arbitrate competing demands.”
But that isn’t bringing much consensus.
“This marks a fundamental shift in the direction of Bitcoin,” one commenter warned on GitHub.
“This is the largest mistake Core can make at this juncture,” another on Github added. “I want to be on the record saying that.”
CORRECT: (May 6, 08:14 UTC): Removes “former” developer from seventh paragraph.
