Please describe the feature you’d like to see added.
Bitcoin currently restricts transactions to a single OP_RETURN output of 80 bytes. This is too limiting for practical use cases like cross-chain swaps and DeFi, where OP_RETURN serves as a lightweight log (e.g. destination token addresses, proofs, parameters).
The restriction also creates inequality: miners with custom policies already accept multiple or larger OP_RETURNs, while standard users cannot. This is similar to MEV and reduces neutrality.
Recent discussions (e.g. Bitcoin Core PR #32359, v30 policy changes) show growing support for lifting or relaxing these limits, since current workarounds (fake outputs, non-standard scripts) are worse for the UTXO set than using proper OP_RETURN.
Proposal:
Allow more than one OP_RETURN per transaction, or
Increase payload size (e.g. 160–256 bytes, or more in line with v30 updates).
This would improve interoperability, fairness, and reduce reliance on hacks for metadata.
Is your feature related to a problem, if so please describe it.
No response
Describe the solution you’d like
No response
Describe any alternatives you’ve considered
No response
Please leave any additional context
No response
