Ricky Zhang
· 1d
BIP-110 goes back to 80b op_returns which works for hashing (timestamping) purposes so I don’t see what the problem is. It prevents arbitrary data greater than 80b
Which is still non-monetary use. Luke, Mechanic, et al have publicly stated multiple times Bitcoin should not be used for non-monetary transactions. They've also stated on Spaces they will continue to squeeze until they find a working solution. So they are the judge, jury and executioner of how block space can be used?
The ultimate point is BIP-110 solves nothing. Now instead of having the ability to prune that data out of the larger op_return, "bad actors" will be forced to chunk it across multiple fields/UTXOs which will then be immutable. I lose optionality as a node runner. So if they truly believed the CSAM talking point, they now guarantee it will exist.
Finally, it also keeps the same core issues they point to with the larger op_return field: 1) greater fees; and 2) blockchain bloat. When you mention this, they state the fees would then be the filter which is exactly what non BIP-110 people have been saying about the current implementation.