randomm

Bitcoin Core developers have merged a pull request to remove the long-standing 83-byte default limit for OP_RETURN data, with the mempool policy change set to take effect in the implementation's v30 release, scheduled for October.

Bitcoin Core is the reference implementation of the Bitcoin protocol, maintained by an open-source community of developers and widely used to run full nodes on the network. The new 100,000-byte limit will effectively uncap the amount of data that can be embedded in a transaction using OP_RETURN, with practical constraints now coming from the standard transaction size limit (approximately 400 KB) or the block size limit (4 MB weight). However, the old limits can still be manually enforced using the "-datacarriersize" option, which remains usable but is now deprecated, with no set timeline for removal.

Bitcoin Core developers have merged a pull request to remove the long-standing 83-byte default limit for OP_RETURN data, with the mempool policy change set to take effect in the implementation's v30 release, scheduled for October.

Bitcoin Core is the reference implementation of the Bitcoin protocol, maintained by an open-source community of developers and widely used to run full nodes on the network. The new 100,000-byte limit will effectively uncap the amount of data that can be embedded in a transaction using OP_RETURN, with practical constraints now coming from the standard transaction size limit (approximately 400 KB) or the block size limit (4 MB weight). However, the old limits can still be manually enforced using the "-datacarriersize" option, which remains usable but is now deprecated, with no set timeline for removal.

https://www.theblock.co/post/357594/bitcoin-core-devs-merge-controversial-op_return-policy-change-into-planned-october-release