Bitcoin Core v30 Lifts OP_RETURN Limit to Support BitVM, Not Ordinals

iconJinse
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy

Based on Jinse, Bitcoin Core v30 increased the OP_RETURN data limit, not to accommodate Ordinals, but to support BitVM development. Citrea's Clementine bridge, the first zkRollup on Bitcoin using BitVM, required 144 bytes of on-chain data for validation, exceeding the previous 83-byte limit. Due to Bitcoin Script limitations, this data had to be in scriptPubKey, not witness, leading to a workaround that created unspendable UTXOs. Core developers, recognizing the long-term importance of BitVM for Bitcoin's L1 innovation, opted to increase the OP_RETURN limit as a harm reduction strategy. This change reflects a proactive move to support future infrastructure needs, not speculative use cases like Ordinals.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.