The argument is that, at the end of the day, you can’t stop spam. But there are better and worse versions of it. If we fight it, it’s more likely we have to deal with the worse version.
As such, it makes sense to allow it through OP_RETURN as a way to reduce harm. This was always the argument for allowing OP_RETURN, even >10 years ago.
But you probably know that already.
Not true and you know it. Spam can be reduced. OP_RETURN kept it at 80 Bytes for > 10 years. Ordnials problem can also be solved.
we as a network are opening the door and welcoming more spam, in a easier, more harmful in content that will be stored forever because of a spam attack that was a fad that is basically dead already. Core should be the standard of what we as a network (nodes) want and accept, large arbitrary data contents are not desirable, and Core should represent that, even if it happens anyway in a smaller scale, thats the definition of spam, it will always exist, even in Core 30 there is zero guarantees that the same utxo spam will not be done by bad actors.
