<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>data cap Archives - Coin Engineer</title>
	<atom:link href="https://coinengineer.net/blog/tag/data-cap/feed/" rel="self" type="application/rss+xml" />
	<link>https://coinengineer.net/blog/tag/data-cap/</link>
	<description>Btc, Coins, Pre-Sale, DeFi, NFT</description>
	<lastBuildDate>Tue, 06 May 2025 14:21:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://coinengineer.net/blog/wp-content/uploads/2024/04/cropped-Coin-Engineer-Logo-Favicon-2-32x32.png</url>
	<title>data cap Archives - Coin Engineer</title>
	<link>https://coinengineer.net/blog/tag/data-cap/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Bitcoin Core Removes Controversial OP_RETURN Limit</title>
		<link>https://coinengineer.net/blog/bitcoin-core-removes-controversial-op_return-limit/</link>
					<comments>https://coinengineer.net/blog/bitcoin-core-removes-controversial-op_return-limit/#respond</comments>
		
		<dc:creator><![CDATA[Yigit Taha OZTURK]]></dc:creator>
		<pubDate>Tue, 06 May 2025 16:30:38 +0000</pubDate>
				<category><![CDATA[Crypto News]]></category>
		<category><![CDATA[EN]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[bitcoin]]></category>
		<category><![CDATA[Bitcoin Core]]></category>
		<category><![CDATA[Bitcoin upgrade]]></category>
		<category><![CDATA[blockchain]]></category>
		<category><![CDATA[btc]]></category>
		<category><![CDATA[Chaincode Labs]]></category>
		<category><![CDATA[cryptocurrency]]></category>
		<category><![CDATA[data cap]]></category>
		<category><![CDATA[eth]]></category>
		<category><![CDATA[ethereum]]></category>
		<category><![CDATA[Greg Sanders]]></category>
		<category><![CDATA[network upgrade]]></category>
		<category><![CDATA[OP_RETURN]]></category>
		<category><![CDATA[ordinals]]></category>
		<category><![CDATA[Peter Todd]]></category>
		<category><![CDATA[protocol debate]]></category>
		<category><![CDATA[Samson Mow]]></category>
		<category><![CDATA[UTXO]]></category>
		<guid isPermaLink="false">https://coinengineer.net/blog/?p=41805</guid>

					<description><![CDATA[<p>Bitcoin Core developers are preparing to lift the long-standing OP_RETURN data cap in the upcoming network upgrade. According to a statement by Greg Sanders, transactions containing OP_RETURN outputs larger than 80 bytes will now be relayed and mined by default. Originally, this restriction aimed to discourage excessive use of block space for non-payment purposes. However,</p>
<p>The post <a href="https://coinengineer.net/blog/bitcoin-core-removes-controversial-op_return-limit/">Bitcoin Core Removes Controversial OP_RETURN Limit</a> appeared first on <a href="https://coinengineer.net/blog">Coin Engineer</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="" data-start="2758" data-end="3036"><strong data-start="2758" data-end="2774">Bitcoin Core</strong> developers are preparing to lift the long-standing <strong data-start="2826" data-end="2839">OP_RETURN</strong> data cap in the upcoming network upgrade. According to a statement by <strong data-start="2910" data-end="2926">Greg Sanders</strong>, transactions containing OP_RETURN outputs larger than <strong data-start="2982" data-end="2994">80 bytes</strong> will now be relayed and mined by default.</p>
<p class="" data-start="3038" data-end="3284">Originally, this restriction aimed to discourage excessive use of block space for non-payment purposes. However, developers now say the limit no longer serves a purpose and that its removal will lead to a more efficient and transparent data flow.</p>
<h2 data-start="3286" data-end="3337">What Is the Impact of Removing OP_RETURN?</h2>
<p class="" data-start="3338" data-end="3612"><strong data-start="3338" data-end="3351">OP_RETURN</strong> is a special transaction output that allows small pieces of data to be stored on the <strong data-start="3437" data-end="3448">Bitcoin</strong> blockchain. It gained popularity during the <strong data-start="3493" data-end="3505">ordinals</strong> hype in early 2024. Unlike standard outputs, OP_RETURN data is unspendable and doesn&#8217;t bloat the UTXO set.</p>
<hr />
<p data-start="3614" data-end="3890"><strong><em>You Might Be Interested In: <a href="https://coinengineer.net/blog/elon-musk-talks-about-the-name-of-a-new-memecoin/">Elon Musk Talks About the Name of a New Memecoin!</a></em></strong></p>
<hr />
<p class="" data-start="3614" data-end="3890">Users had already found ways to bypass the restriction, often using fake output addresses that were more damaging to the network. Developers argue that lifting the limit will promote <strong data-start="3797" data-end="3820">network consistency</strong>, a <strong data-start="3824" data-end="3844">cleaner UTXO set</strong>, and better reflect real-world Bitcoin usage.</p>
<h2 data-start="3892" data-end="3936">Mixed Reactions from the Community</h2>
<p class="" data-start="3937" data-end="4211">The change is not without controversy. Well-known Bitcoiner <strong data-start="3997" data-end="4011">Samson Mow</strong> commented that users could simply stick with version <strong data-start="4065" data-end="4073">29.0</strong> or use an alternative client. Others criticized the lack of proper consensus, suggesting the update was rushed without broader agreement.</p>
<p class="" data-start="4213" data-end="4366">The decision reignites a long-standing debate: Is <strong data-start="4263" data-end="4274">Bitcoin</strong> solely a financial tool, or should it also function as a decentralized publishing platform?</p>
<p data-start="4213" data-end="4366"><img fetchpriority="high" decoding="async" class="aligncenter wp-image-155250 " src="https://coinmuhendisi.com/blog/wp-content/uploads/2025/05/bitcoin-core.jpeg" alt="bitcoin core" width="593" height="578" /></p>
<hr />
<p data-start="4213" data-end="4366"><em>You can also freely share your thoughts and comments about the topic in the comment section. Additionally, don’t forget to follow us on our <a href="https://t.me/coinengineernews" target="_blank" rel="noreferrer noopener nofollow"><strong>Telegram, </strong></a><a href="https://www.youtube.com/@CoinEngineer" target="_blank" rel="noreferrer noopener nofollow"><strong>YouTube</strong></a>, and <a href="https://twitter.com/coinengineers" target="_blank" rel="nofollow noopener"><strong>Twitter</strong></a> channels for the latest <a title="News" href="https://coinengineer.net/blog/news/" data-internallinksmanager029f6b8e52c="7">news</a> and updates.</em></p>
<p>The post <a href="https://coinengineer.net/blog/bitcoin-core-removes-controversial-op_return-limit/">Bitcoin Core Removes Controversial OP_RETURN Limit</a> appeared first on <a href="https://coinengineer.net/blog">Coin Engineer</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://coinengineer.net/blog/bitcoin-core-removes-controversial-op_return-limit/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url='https://coinengineer.net/blog/wp-content/uploads/2025/01/bitcoin_ce-1.png' type='image/webp' medium='image' width='1920' height='1080'><media:title type='plain'> <![CDATA[USA]]></media:title><media:thumbnail url='https://coinengineer.net/blog/wp-content/uploads/2025/01/bitcoin_ce-1.png' width='58' height='33' /></media:content>	</item>
	</channel>
</rss>
