Author: Claus Ehrenberg 2023-02-16 19:59:06
Published on: 2023-02-16T19:59:06+00:00
In a bitcoin-dev mailing list, Claus proposes to require all data to be in the op_return output and add a required op_return_hash field that is checked by consensus. This will allow nodes to re-validate the chain without having to store/download/look at the contents of op_return data. The benefit of this redundancy is that "content-sensitive" communities can ignore the data they don't like. Aymeric Vitte suggests a workaround for the 80-byte op_return limitation which involves bringing back bitcoin ten years ago. He further adds that if bitcoin folks do not understand the need for a one-transaction storage solution for the future, then let's bring back bitcoin into the past. Russell O'Connor suggests that since bytes in the witness are cheaper than bytes in the script pubkey, there is a crossover point in data size where it will simply be cheaper to use witness data. But he doesn't think it's worth the technical complexity trying to carefully argue a specific limit. Instead, users should decide for themselves how they want to use OpReturn.
Updated on: 2023-06-16T04:14:48.172540+00:00