One justification for removing the OP_RETURN policy limit is that arbitrary data is “unstoppable” and will always find its way onto the blockchain. At the same time, not all data vectors have the s...

Stack Exchange - Bitcoin

14.09.2025

op return - How do v30’s changes to OP_RETURN rules and datacarriersize impact mempool cohesion and node operator autonomy? - Bitcoin Stack Exchange

Bitcoin Core v30 will for the first time allow transactions into the default mempool with more than one OP_RETURN output. The datacarriersize= setting is being repurposed so that numeric limits now...

Stack Exchange - Bitcoin

14.09.2025

op return - If OP_RETURN needed more room, why was the 80-byte cap removed instead of being raised to 160? - Bitcoin Stack Exchange

Bitcoin originally limited OP_RETURN outputs to 80 bytes to discourage arbitrary data storage and keep the chain focused on monetary use. Recently this cap was removed, with the argument that some

Stack Exchange - Bitcoin

14.09.2025

mempool - What are the worst-case stress scenarios from uncapped OP_RETURNs in Bitcoin Core v30? - Bitcoin Stack Exchange

With Bitcoin Core v30 removing the 80-byte OP_RETURN relay cap, transactions with very large OP_RETURN payloads can now propagate by default, up to block weight limits. In a stress-test context, I’...

home›Stack Exchange - Bitcoin

Stack Exchange - Bitcoin

Cryptocurrency

mempool - If arbitrary data is inevitable, does removing OP_RETURN limits shift demand toward more harmful storage methods (like UTXO-inflating addresses)? - Bitcoin Stack Exchange

op return - How do v30’s changes to OP_RETURN rules and datacarriersize impact mempool cohesion and node operator autonomy? - Bitcoin Stack Exchange

op return - If OP_RETURN needed more room, why was the 80-byte cap removed instead of being raised to 160? - Bitcoin Stack Exchange

mempool - What are the worst-case stress scenarios from uncapped OP_RETURNs in Bitcoin Core v30? - Bitcoin Stack Exchange

home
›
Stack Exchange - Bitcoin