pull down to refresh

10 sats \ 0 replies \ @Murch 22h \ parent \ on: Quick questions about OP_RETURN? Quick answers here. bitcoin
You appear to make several unstated assumptions. At least you seem to think that dropping the OP_RETURN limit will increase the total of OP_RETURN bytes added to the blockchain, that additional OP_RETURN bytes will increase the overall blockchain size, and that additional OP_RETURN data increases the cost for processing the blockchain.
  1. OP_RETURN data is cheap to validate, because it does not contain any signature operations.
  2. OP_RETURN data is not discounted, therefore an increased amount of OP_RETURN data probably displaces some witness data and would lead to overall smaller blocks.
I will grant that dropping the limit might increase the future OP_RETURN use, but it is not obvious to me that it would increase it beyond what would otherwise be embedded per inscriptions or fake pubkeys or fake pubkey hashes.
There are numerous off-chain solutions for arbitrary data storage that don't burden the Bitcoin network, including sidechains, layer 2 solutions, and purpose-built data storage blockchains. The proposal doesn't sufficiently explore why these alternatives are inadequate.
Storing data off-chain does not fulfill the criteria of on-chain data availability, so while it were preferable that data not be stored on-chain, it’s clearly not a replacement if on-chain data availability is a design goal.
write
preview