|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cryptocurrency News Articles
Bitcoin Core developers remove 80-byte limit on OP_RETURN outputs, enabling more data in a more efficient way
May 06, 2025 at 02:08 pm

Bitcoin Core developers have decided to remove a limit on transaction data in the next network upgrade, enabling more data to be included in a more efficient way.
“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,” announced Bitcoin developer Greg Sanders on GitHub on May 5.
The long-standing limit was originally a “gentle signal that block space should be used sparingly for non-payment proof of publication data,” which has outlived its utility, he added.
The proposal (PR 32359) was created by Bitcoin pioneer Peter Todd at the request of Chaincode Labs.
OP_RETURN is a special type of Bitcoin (BTC) transaction output that allows storing small amounts of data on the blockchain, popularized during the ordinals inscriptions craze in early 2024.
Unlike regular transaction outputs, OP_RETURN outputs are not spendable and don’t bloat unspent transaction outputs (UTXOs).
The original limit is no longer effective as people found ways around it, such as using fake output addresses, which are actually worse for the network, while some mining services were already ignoring the limit, Sanders said.
Benefits of removing the limit include a cleaner UTXO set, or database of spendable outputs, more consistent behavior across the network, and better alignment with how Bitcoin is actually being used, he added.
Three possible paths were considered: keeping the cap, raising the cap and removing the cap, which was ultimately decided upon after earning “broad, though not perhaps unanimous, support.”
A controversial change to Bitcoin
“Many users find this to be an undesirable change for a number of reasons,” said Bitcoiner Samson Mow.
Users “can refuse to upgrade and stay on 29.0 or run another implementation” of the network, he added.
Critics said that the proposal was introduced without a proper consensus process.
“I think one thing is pretty clear, there is no moment at on this OP_RETURN issue,” said Ten31 Fund managing partner Marty Bent.
Some also expressed concerns about deprioritizing Bitcoin’s financial utility and raised questions about undisclosed conflicts of interest.
Disclaimer:info@kdj.com
The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!
If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.
-
-
- Keystone Breach: Customer Data Leak Ignites Hardware Wallet Security Concerns
- Oct 26, 2026 at 11:55 am
- Keystone's recent data breach, exposing customer shipping information, underscores escalating security risks for crypto hardware wallet users and sparks critical questions about data retention and user safety.
-
-
-
- AI Agents, ETH Glamsterdam Fork, and the 'Steal My Bitcoin' Saga: A Deep Dive into Crypto's Evolving Security Landscape
- Oct 26, 2026 at 07:55 am
- Ethereum's Glamsterdam hard fork faces delays, while AI agents revolutionize vulnerability scanning, and the 'Steal My Bitcoin' site tests PHP2Shell resilience, highlighting crypto's dynamic security evolution.
-
-
-
- AI Agents, ETH Glamsterdam Fork, and the 'Steal My Bitcoin' Saga: A New York Minute on Crypto Security
- Oct 26, 2026 at 07:15 am
- AI agents are stepping up to secure crypto, as seen with the ETH Glamsterdam fork's rescue, while the 'Steal My Bitcoin' challenge tests an old vulnerability, highlighting a dynamic era for digital asset safety.
-
- GMO Trading Cloud Breach Raises Server Risk Concerns, Echoing Past Data Incidents
- Oct 26, 2026 at 07:15 am
- A significant server risk event at GMO Trading Cloud, potentially affecting 26,739 servers, highlights ongoing data breach vulnerabilities in the financial tech sector. This news follows similar incidents, underscoring the need for robust security.

































