126 sats \ 2 replies \ @mononautical 2 Jul \ parent \ on: Analysis of 0xB10C's weird bitcoin transaction bitcoin
the transaction is actually completely standard, and in fact was observed in mempool.space's mempool before it was mined.
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
"bc1pfeessrawgf" is the correct address rendering for this output, since it is a valid segwit v1 witness program, even though the combination of witness version & program length does not correspond to any defined spending rules.
(although the 2-byte
0x4e73 output script does match a proposal for ephemeral outputs).Fun fact: undefined segwit outputs like this are completely standard to create, and only non-standard to spend.
However, this transaction did prompt us to fix a bug on mempool.space that calculated the dust limit incorrectly for this kind of output, which caused the transaction to be falsely labeled as non-standard for a short time.
Great feedback, thank you!
Links to a more fully-featured explorer for additional details would definitely be useful.
The address truncation is actually only visual, you should still be able to copy and paste the full address if you select across both sides of the '...'
GENESIS