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)로 연락주시면 즉시 삭제하도록 하겠습니다.
