pull down to refresh

I've seen this before and it's almost certainly developer/transaction construction error. One of the things I make sure to teach about Bitcoin transactions is that you have to send the change back to yourself or it ends up as a fee (tx outputs have only two states, spent and unspent). I suspect that's what happened here. That person made a tx without a change output.

It's not uncommon and has happened quite a few times in Bitcoin history.

Painful lesson in this case.

reply

Pain is the best teacher 😂💯

reply

Only if you survive it :(

reply

I take it back. I agree with Jameson that it's bad software from what's probably an exchange: https://twitter.com/lopp/status/1700985810714239222?s=20

reply

will be interesting to know how this transaction has been done, which wallet has been used 🤔

reply

This makes a lot of sense. But wouldn't a wallet at least warn, or show that the fee is way off the charts?