Weird Segwit Transactions

So I've been noticing some transactions popping up with nonstandard Segwit outputs. Check these out: https://mempool.space/tx/e57619adbb62c2e8add13eb2694010f3ba337cf5007ca3674224c272feffb097 https://mempool.space/tx/9a9d955dff45c6cef6f4e41a12052dde21179069a2e17fe8f381f6c75e112b6a The output scripts look pretty odd, like they’re doing something weird with OP_PUSH. Anyone else seen this?

Yeah, I've seen this too. Sending coins to new Segwit addresses has always been fine, but spending from them is where it gets tricky. Like, if they introduce a new address type, it could get messy with old clients rejecting them. Here’s an example of a nonstandard address that gets funky when trying to spend: https://mempool.space/pl/address/bc1sw50qgdz25j. Old wallets just don’t adapt well. Just take a look at Taproot too, it’s tricky for older clients to handle it. But hey, there are always limits; can't have a Segwit address with more than certain things.

I totally get it but honestly, why bother sending to these weird addresses? Just feels pointless, like why are we just increasing the UTXO set for no reason? It’s like throwing away small amounts for fun or something. Seems to me these transactions are just from some faulty system. Can't we just tweak the core client rules to prevent this crap from happening? That would save everyone a lot of trouble.