That’s true, but there’s a difference between people using an exploit that is not natively supported vs using op_return which is a feature with the purpose to allow arbitrary data.
By increasing the op_return limit you are now signalling that relaying large blobs of continuous data is a feature supported by the network. In contrast, shoving split up chunks of data into the witness section where it is not designed to be is not an intended use of the network.
The argument is that: now relaying large continuous chunks of data is natively supported, any legal/regulatory plausible deniability is gone.
From a technical standpoint this change also makes it easier for bad actors / criminals as they don’t have to split their files into multiple chunks.
Login to reply
Replies (1)
Is there some rule I don't get? (Likely) You can put in 100k vbytes now and you don't need to split them?

Bitcoin Stack Exchange
What is the maximum size transaction that will be relayed by bitcoin nodes using the default configuration?
I understand that the actual size limit of a transaction is determined by the block size, as we can see from this absolute unit. But transactions t...