that nonstandard address should appear on bitcoin explorers as the plain text term "non-standard" but the transaction author knew that mempool.space has a naive/buggy address parser and exploited that to make the address look like a valid-but-incredibly-short segwit address
I believe that address is actually an ephemeral anchor output: https://github.com/bitcoin/bitcoin/pull/30352/files
IIUC they are standard to create at the moment. It's spending them that is non-standard.
Fascinating! But that pull request is still pending right? I don't think they will be standard as outputs til it is merged
reply