Bitcoin (BTC) developers have removed the default 80-byte limit on OP_RETURN outputs in an upcoming release of Bitcoin Core, enabling the insertion of larger data payloads and multiple OP_RETURN entries within a single transaction.
The change follows a prolonged debate within the Bitcoin community over whether the existing cap, introduced in 2014, has outlived its usefulness.
As of May 12, 2025, Bitcoin Core had not merged any pull requests related to altering OP_RETURN limits and proposals remain open for review.
What Is OP_RETURN?
OP_RETURN is a script opcode that allows users to append up to 80 bytes of arbitrary information—such as text, hashes, or protocol indicators—to transactions. Unlike spendable outputs, which are stored in the unspent transaction output (UTXO) set, OP_RETURN outputs are provably unspendable, allowing nodes to prune them without loss of funds.
This capability supports nonpayment applications, including timestamping ownership proofs, embedding metadata for layer-two (L2) protocols or intentionally burning coins in targeted use cases.output
免責事項:info@kdj.com
提供される情報は取引に関するアドバイスではありません。 kdj.com は、この記事で提供される情報に基づいて行われた投資に対して一切の責任を負いません。暗号通貨は変動性が高いため、十分な調査を行った上で慎重に投資することを強くお勧めします。
このウェブサイトで使用されているコンテンツが著作権を侵害していると思われる場合は、直ちに当社 (info@kdj.com) までご連絡ください。速やかに削除させていただきます。
