Market Cap: $3.2672T -0.710%
Volume(24h): $102.3379B -6.020%
  • Market Cap: $3.2672T -0.710%
  • Volume(24h): $102.3379B -6.020%
  • Fear & Greed Index:
  • Market Cap: $3.2672T -0.710%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top News
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
bitcoin
bitcoin

$107295.810621 USD

-0.60%

ethereum
ethereum

$2438.191256 USD

-2.24%

tether
tether

$1.000355 USD

0.01%

xrp
xrp

$2.107400 USD

-4.14%

bnb
bnb

$645.196047 USD

-0.58%

solana
solana

$140.861296 USD

-3.48%

usd-coin
usd-coin

$0.999977 USD

0.05%

tron
tron

$0.271724 USD

-0.74%

dogecoin
dogecoin

$0.162450 USD

-2.18%

cardano
cardano

$0.559765 USD

-2.72%

hyperliquid
hyperliquid

$36.577660 USD

-2.60%

bitcoin-cash
bitcoin-cash

$491.980353 USD

1.63%

sui
sui

$2.645087 USD

-4.57%

chainlink
chainlink

$13.061914 USD

-2.28%

unus-sed-leo
unus-sed-leo

$9.014317 USD

0.12%

Cryptocurrency News Articles

Bitcoin Core 30 Update Will Significantly Increase the Data Limit for the OP_RETURN Function

Jun 11, 2025 at 09:39 pm

The upcoming Bitcoin Core 30 update, scheduled for release in October, will significantly increase the data limit for the OP_RETURN function — a special operational code that allows users to embed arbitrary data in Bitcoin transactions.

Bitcoin Core 30 Update Will Significantly Increase the Data Limit for the OP_RETURN Function

The upcoming Bitcoin Core v30 release, anticipated for October, will introduce a substantial increase in the data limit for the OP_RETURN function. This special operational code allows users to embed arbitrary data in Bitcoin transactions, with the current constraint set at 80 bytes.

The integration of this change is part of the broader v30 release, which is currently undergoing testing on the testnet ahead of the mainnet launch in the fall.

According to developers, the default OP_RETURN data limit will be adjusted from 80 bytes to approximately 4MB, aligning with Bitcoin's existing block size limits.

The modification aims to address issues encountered with data storage techniques and the unspent transaction output set, which becomes densely packed with outputs smaller than 80 bytes.

As reported by Bitcoin developer Aben Ryley on GitHub, the data limit for OP_RETURN can be set at startup, with a default value of 4,194,209 (2^22 + 1) bytes.

This startup setting will also determine the data limit for P2SH programs.

The minimum unspent transaction output size will be set to 55 bytes, and the minimum input size will be set to 137 bytes.

The developers explained that the unspent transaction output set becomes densely packed with outputs smaller than 80 bytes, leading to issues with data structures and storage techniques used by testers.

Moreover, lower unspent transaction output sizes can be problematic for testers using low-memory devices.

The OP_RETURN data limit can be adjusted at startup, with a maximum limit of 2^32 - 1.

The startup setting will also determine the data limit for P2SH programs.

This change is part of the broader v30 release, which is currently testing on the testnet ahead of the mainnet launch in the fall.

The v30 release will bring several new features to Bitcoin, including the introduction of a new P2TR (Pay to Relayer Trust) output type and updates to the coinbase transaction.

It will also set the stage for the development of the next Bitcoin Core release, v31, which is expected to focus on privacy-enhancing technologies.output: The upcoming Bitcoin Core v30 release, anticipated for October, will introduce a substantial increase in the data limit for the OP_RETURN function. This special operational code allows users to embed arbitrary data in Bitcoin transactions, with the current constraint set at 80 bytes.

The integration of this change is part of the broader v30 release, which is currently undergoing testing on the testnet ahead of the mainnet launch in the fall.

According to developers, the default OP_RETURN data limit will be adjusted from 80 bytes to approximately 4MB, aligning with Bitcoin's existing block size limits.

The modification aims to address issues encountered with data storage techniques and the unspent transaction output set, which becomes densely packed with outputs smaller than 80 bytes.

As reported by Bitcoin developer Aben Ryley on GitHub, the data limit for OP_RETURN can be set at startup, with a default value of 4,194,209 (2^22 + 1) bytes.

This startup setting will also determine the data limit for P2SH programs.

The minimum unspent transaction output size will be set to 55 bytes, and the minimum input size will be set to 137 bytes.

The developers explained that the unspent transaction output set becomes densely packed with outputs smaller than 80 bytes, leading to issues with data structures and storage techniques used by testers.

Moreover, lower unspent transaction output sizes can be problematic for testers using low-memory devices.

The OP_RETURN data limit can be adjusted at startup, with a maximum limit of 2^32 - 1.

The startup setting will also determine the data limit for P2SH programs.

This change is part of the broader v30 release, which is currently testing on the testnet ahead of the mainnet launch in the fall.

The v30 release will bring several new features to Bitcoin, including the introduction of a new P2TR (Pay to Relayer Trust) output type and updates to the coinbase transaction.

It will also set the stage for the development of the next Bitcoin Core release, v31, which is expected to focus on privacy-enhancing technologies.

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.

Other articles published on Jun 28, 2025