good chance this is a perfect encapsulation of the entire messy issue
Login to reply
Replies (1)
the original point was “op_return was easier” for some cases where you needed just a little bit more data, as you did not need 2 txs.
it was never cheaper or better compared to inscriptions for mass data storage, and was in fact a major step back on that front
now all of this is moot because taproot annex exists which does the best of both worlds and is even more “prunable” as it is guaranteed useless
the fact that the limit was increased beyond a few KB feels even after user feedback feels like there is no regard for sensibility, and nuking op_return to 40 bytes like with knots is also pointless as it can’t fit enough data for some use cases
all this has done is one of the leading implementations being open arms to data storage which will encourage it, while leaving people with 2 shit choices
I also do not understand why some people feel the need to defend use cases they have no involvement in