Bitget App
Trade smarter
Buy cryptoMarketsTradeFuturesEarnWeb3SquareMore
Trade
Spot
Buy and sell crypto with ease
Margin
Amplify your capital and maximize fund efficiency
Onchain
Going Onchain, without going Onchain!
Convert
Zero fees, no slippage
Explore
Launchhub
Gain the edge early and start winning
Copy
Copy elite trader with one click
Bots
Simple, fast, and reliable AI trading bot
Trade
USDT-M Futures
Futures settled in USDT
USDC-M Futures
Futures settled in USDC
Coin-M Futures
Futures settled in cryptocurrencies
Explore
Futures guide
A beginner-to-advanced journey in futures trading
Futures promotions
Generous rewards await
Overview
A variety of products to grow your assets
Simple Earn
Deposit and withdraw anytime to earn flexible returns with zero risk
On-chain Earn
Earn profits daily without risking principal
Structured Earn
Robust financial innovation to navigate market swings
VIP and Wealth Management
Premium services for smart wealth management
Loans
Flexible borrowing with high fund security
Bitcoin community split over OP_Return limit removal plan from Core devs

Bitcoin community split over OP_Return limit removal plan from Core devs

The BlockThe Block2025/05/05 16:00
By:By Naga Avan-Nomayo

Quick Take Bitcoin core developers said the 80-byte cap is already constantly side-stepped by spammers in a way that bloats and abuses the network. The plan received backlash for not gaining consensus and community support.

Bitcoin community split over OP_Return limit removal plan from Core devs image 0

Bitcoin Core developers plan to remove the long-standing 80-byte size limit on OP_RETURN outputs in an upcoming software release, a move that has sparked disagreement within the development community.

OP_RETURN allows small amounts of data to be embedded into Bitcoin transactions with an unspendable output (UXTO). The concept grew in popularity during the early 2024 ordinals and inscription boom.

According to Bitcoin Core contributor Greg Sanders, the update would completely eliminate the current 80-byte limit and “allow any number of these outputs." In a May 5 GitHub post , Sanders said that the restriction had outlasted its purpose and lifting the cap would encourage less harmful onchain behavior.

“The cap merely channels them into more opaque forms that cause damage to the network,” Sanders wrote, referring to large-data inscriptions and other participants that bypass the 80-byte threshold. “When the polite avenue is blocked, determined users turn to impolite ones. Some use bare multisig or craft fake output public keys that do enter the UTXO set, exactly the outcome OP_RETURN was invented to avoid."

Developers considered three options: keep the cap, raise it, or remove it entirely. The first two were deemed arbitrary and ineffective, while the third option garnered broad — though not unanimous — support, according to the GitHub discussion.

Sanders argued that lifting the cap would help maintain a cleaner UTXO set, reduce transaction burdens, and reaffirm simple, transparent rules within Bitcoin’s protocol.

Not everyone agrees. Critics including JAN3 CEO Samson Mow called the removal an “undesirable change for a number of reasons.” Marty Bent, managing partner at Ten31 Fund, noted on X that the proposal lacks broad consensus. Some community members worry the change could incentivize spam on the Bitcoin network, while others surmised that removing the 80-byte limit was performative and seemingly coercive .

The debate continues across GitHub and social media. Bitcoin Core developers have not set a release date for the proposed update.


0

Disclaimer: The content of this article solely reflects the author's opinion and does not represent the platform in any capacity. This article is not intended to serve as a reference for making investment decisions.

PoolX: Locked for new tokens.
APR up to 10%. Always on, always get airdrop.
Lock now!