{"id":25472,"date":"2025-05-06T19:32:00","date_gmt":"2025-05-06T19:32:00","guid":{"rendered":"https:\/\/dogewisperer.com\/?p=25472"},"modified":"2025-05-06T19:32:00","modified_gmt":"2025-05-06T19:32:00","slug":"bitcoin-core-to-remove-op_return-limit-in-next-upgrade","status":"publish","type":"post","link":"https:\/\/dogewisperer.com\/?p=25472","title":{"rendered":"Bitcoin Core to Remove OP_RETURN Limit in Next Upgrade"},"content":{"rendered":"
\n

Bitcoin Core developers have confirmed that the next software release will lift the long-standing 80-byte restriction on OP_RETURN transaction outputs.<\/p>\n

The decision was met with concern in the crypto space as users expressed dissatisfaction with the move.<\/p>\n

OP_RETURN Has Outlived Its Purpose<\/h2>\n

The information was relayed in a May 5 GitHub announcement<\/a> by Bitcoin developer Gregory Sanders, which read:<\/p>\n

\n

\u201cBitcoin Core\u2019s next release will, by default, relay and mine transactions whose OP_RETURN outputs exceed 80 bytes and allow any number of these outputs.\u201d<\/p>\n<\/blockquote>\n

Sanders explained that the 80-byte limit was originally a \u201cgentle signal that block space should be used sparingly for non-payment proof of publication data,\u201d but that it has now outlived its usefulness.<\/p>\n

OP_RETURN is a type of Bitcoin transaction output that allows <\/a>small amounts of data to be stored on the blockchain. Unlike regular outputs, they are unspendable and therefore don\u2019t contribute to unspent transaction outputs (UTXOs).<\/p>\n

Developers noted that many private mining accelerators already ignore the limit, and users often find workarounds. Instead of stopping misuse, they have started embedding data in more complex ways, such as crafting fake output public keys or using spendable scripts to hide data. This makes the network harder to manage and less efficient.<\/p>\n

Some proposed introducing blacklists to stop these tricks, but the developers rejected that idea. They argued that blacklists are unreliable, hard to maintain, and could even lead to innocent people losing funds.<\/p>\n

Sanders also clarified that removing the restriction doesn\u2019t weaken Bitcoin\u2019s security. Rules like the 4 million weight unit block limit and other safeguards remain in place. However, the change brings some improvements, such as a cleaner UTXO set and more consistent behavior across the network.<\/p>\n

He explained that developers considered three options before reaching a decision: keeping the cap, raising it, or removing it entirely. According to him, the third option received \u201cbroad, though not unanimous support.\u201d<\/p>\n

Community Debate<\/h2>\n

The announcement has started a debate in the crypto community. Bitcoin Knots maintainer Luke Dashjr described the removal as \u201cutter insanity.\u201d Bitcoiner Samson Mow said<\/a> on X on May 5 that users \u201ccan refuse to upgrade and stay on 29.0 or run another implementation,\u201d referring to Knots.<\/p>\n

Critics also argued <\/a>that the proposal was introduced without a proper decision-making process. \u201cI think one thing is pretty clear: there is no consensus at the moment on this OP_RETURN issue,\u201d said Ten31 Fund managing partner Marty Bent.<\/p>\n

Meanwhile, Sanders has defended the removal of the cap as aligned with Bitcoin\u2019s ethos of\u00a0 \u201cminimal and transparent rules.\u201d<\/p>\n

Despite these assurances, the community still doesn\u2019t agree. \u201cThis marks a fundamental shift in the direction of Bitcoin,\u201d one commenter warned on GitHub. \u201cThis is the largest mistake Core can make at this juncture,\u201d another added.<\/p>\n

The post Bitcoin Core to Remove OP_RETURN Limit in Next Upgrade<\/a> appeared first on CryptoPotato<\/a>.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Bitcoin Core developers have confirmed that the next software release will lift the long-standing 80-byte restriction on OP_RETURN transaction outputs. The decision was met with concern in the crypto space as users expressed dissatisfaction with the move. OP_RETURN Has Outlived Its Purpose The information was relayed in a May 5 GitHub announcement by Bitcoin developer […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[2],"tags":[3,4,5],"class_list":["post-25472","post","type-post","status-publish","format-standard","hentry","category-news","tag-crypto","tag-doge","tag-news"],"_links":{"self":[{"href":"https:\/\/dogewisperer.com\/index.php?rest_route=\/wp\/v2\/posts\/25472","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dogewisperer.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dogewisperer.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dogewisperer.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dogewisperer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=25472"}],"version-history":[{"count":0,"href":"https:\/\/dogewisperer.com\/index.php?rest_route=\/wp\/v2\/posts\/25472\/revisions"}],"wp:attachment":[{"href":"https:\/\/dogewisperer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=25472"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dogewisperer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=25472"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dogewisperer.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=25472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}