Bitcoin Core v30 Increases OP_RETURN Default Limit to 100,000 Bytes

Bitcoin Core v30.0 has raised the default allowable limit for OP_RETURN data to 100,000 bytes. This has reignited the debate over the use of block space. While the number of OP_RETURN outputs is approaching 700,000, actual usage remains unverified. OP_RETURN is a script command that allows data to be embedded in Bitcoin transactions, designed not to remain as typical unspent transaction outputs (UTXOs). According to the release notes for Bitcoin Core v30.0, the default '-datacarriersize' value has increased to 100,000 bytes, and transactions containing multiple OP_RETURN outputs are also permitted. To apply the previous default limit of 83 bytes, separate configuration is required. This adjustment does not change Bitcoin's consensus rules but alters the policy for nodes to relay unconfirmed transactions and include them in mining candidates. Runes utilize OP_RETURN for token protocol data recording, with a maximum of one runestone allowed per transaction. There is a conflict between the argument that block space should be prioritized for currency transfers and the emphasis on the data recording capabilities of OP_RETURN. Discussions related to OP_RETURN usage focus on how much data insertion and token protocols Bitcoin node policies will allow.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.