pull down to refresh
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.
echo chambers and group think
I couldn't resist not to post my old meme warning...
https://i.postimg.cc/Kz3vS74B/darth-cbdc-compliance.jpg
Published post about Bisq After one year of continuous use, this is my conclusion about BISQ (DE).
This right here is why you and the Devs f***ing rock. Rapid response, quick to clarify and quick to get onto fixes. All of you are awesome. 👊
Honestly, it is the routines it has in place that keeps me engaged n enthusiastic:
- Meme Monday
- Fun Fact Friday
- Weekend Book Recommendations
- Stacker Saloon
Every day I have something different to look forward to
The simplicity on the main chain is unchanged. The experimentation on higher layers is a good thing! The 'many projects and too few users' argument could literally be used for all start ups in every industry. That's just the nature of it.
Most of these experiments will fail and that's okay; the ones that work will make a huge impact