Bitcoin Core currently considers a single OP_RETURN output with 80 bytes data standard. Above 143 bytes, it’s cheaper to use inscriptions.

There may be some use case that needs multiple OP_RETURN outputs which previously used several transactions instead of doing a single transaction. If they would have created let’s say three transactions instead of a single transaction with three OP_RETURN outputs, they can achieve the same thing with less blockspace, so they pay a bit less, but they also demand less blockspace.

It might open up the avenue for some people creating larger OP_RETURNs that wouldn’t have bothered to do so if it were non-standard even though they could have just submitted it to Mara’s Slipstream before.

Overall, I think the novelty will wear off, and in the long run, valuable payment transactions will price out frivolous data transactions. We cannot really prevent data transactions that are very valuable to their senders either way.

Hah, thanks for your support. I’m not sure I’d be the right guy, I’d feel bad golfing so much.