pull down to refresh
I think all three of these are already covered here:
Why is the 80-byte OP_RETURN limit being removed, and what are the main risks and benefits of this change?
Will node operators still be able to set their own OP_RETURN size limits, or is the configuration option also being removed?
How does removing the OP_RETURN limit impact UTXO set bloat and network health compared to current workarounds?
reply
Why is the 80-byte OP_RETURN limit being removed, and what are the main risks and benefits of this change?Why is the 80-byte OP_RETURN limit being removed, and what are the main risks and benefits of this change?
Will node operators still be able to set their own OP_RETURN size limits, or is the configuration option also being removed?Will node operators still be able to set their own OP_RETURN size limits, or is the configuration option also being removed?
How does removing the OP_RETURN limit impact UTXO set bloat and network health compared to current workarounds?How does removing the OP_RETURN limit impact UTXO set bloat and network health compared to current workarounds?