Pull-req to remove the arbitrary limits on OP_Return outputs



Summary:

OP_RETURN outputs are already pruned and not inserted into the UTXO database. Pruning in this context refers to removing or not inserting OP_RETURN from the UTXO database. The UTXO database is kept small to reduce lookups of spent UTXOs for faster validation. Archival nodes retain the raw OP_RETURN data as part of the block data to prove validity. Block-pruning nodes also retain this data to serve recent blocks that contain valid transactions with OP_RETURN. To prove a block's validity, OP_RETURN data must be provided to show the correctly formatted transaction and its txid in the Merkle tree. Block relay requires retaining OP_RETURN data for verification. Pruning in this context means not keeping OP_RETURN TXOs in the UTXO database.


Updated on: 2023-08-09T02:07:16.373335+00:00