Unshackling Bitcoin: The Lifting of the 80-byte OP_RETURN Restriction
Increasing OP_RETURN Limit in Upcoming Bitcoin Core Update
There's a storm brewing in the world of cryptocurrency as Bitcoin Core developers plan to dismantle a longstanding limitation on transaction outputs with the next software update.
Say hello to freedom, folks, because OP_RETURN is breaking free from its chains! In a May 5 GitHub announcement, Bitcoin developer Gregory Sanders declared:
"Bitcoin Core's next release will, by default, relay and mine transactions whose OP_RETURN outputs exceed 80 bytes and allow any number of these outputs."
This revelation has sent ripples through the crypto community, with many users expressing skepticism and discontent towards this move.
The Signal That Time Forgot
The 80-byte restriction on OP_RETURN, originally a gentle nudge toward using block space responsibly for non-payment proof of publication data, is now seen as irrelevant by the developers. OP_RETURN, a type of Bitcoin transaction output, allows small data to be stored on the blockchain, unlike regular outputs which are spendable.
Developers pointed out that private mining accelerators have been ignoring the limit for quite some time, with users often finding creative workarounds. Instead of smothering misuse, they have begun embedding data in increasingly complex ways, such as fabricating output public keys or hiding data behind spendable scripts. This only makes the network more chaotic and inefficient.
Some suggested implementing blacklists to thwart these tricks, but the developers declined this idea, stating that blacklists are unreliable, cumbersome, and may even result in innocent individuals losing their funds.
Sanders clarified that eliminating the restriction won't compromise Bitcoin's security, as safeguards like the 4 million weight unit block limit remain in effect. However, the change does bring benefits, such as a cleaner unspent transaction output (UTXO) set and more consistent network behavior.
After considering three options – keeping the cap, raising it or eliminating it entirely – the team decided on the latter, but not without objections:
"The third option received 'broad, though not unanimous support,'" according to Sanders.
The Crypto Community at Odds
The announcement has sparked a heated debate in the crypto sphere. Luke Dashjr, Bitcoin Knots maintainer, labeled the move as "utter insanity." Bitcoiner Samson Mow said on Twitter that users "can refuse to upgrade and stay on 29.0 or run another implementation," referring to Knots.
Critics also claimed that the proposal was rushed and lacked a proper decision-making process. "I think one thing is pretty clear - there is no consensus at the moment on this OP_RETURN issue," said Ten31 Fund managing partner Marty Bent.
On the flip side, Sanders defended the removal of the cap as staying true to Bitcoin's ideology of minimal, transparent rules. Despite his assurances, the community remains divided:
"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," added another.
Claim your Binance welcome bonus here!
Unlock a $500 free position on Bybit here!
Join Bitcoin's social media universe: Facebook | Twitter | LinkedIn | Telegram
- The Bitcoin Core developers are planning to lift the 80-byte OP_RETURN restriction in their next software update, allowing transactions with OP_RETURN outputs exceeding 80 bytes.
- Gregory Sanders, a Bitcoin developer, shared this announcement on GitHub, stating that Bitcoin Core will, by default, relay and mine transactions with expanded OP_RETURN outputs.
- The crypto community has reacted with skepticism and discontent towards this move, with some users expressing concerns about the potential chaos and inefficiency it may cause.
- The developers considered three options for OP_RETURN and ultimately decided to eliminate the restriction entirely, despite objections from a few members of the community.
- The lifting of the OP_RETURN restriction has sparked a heated debate in the crypto sphere, with some expressing concern that this could be a major mistake for Bitcoin, while others agree with the move as a reflection of Bitcoin's minimal, transparent rules.
