Post
Topic
Board Bitcoin Technical Support
Merits 2 from 2 users
Re: Bitcoin core, can’t send my BTC (not in memory pool)
by
HCP
on 20/04/2019, 22:15:54 UTC
⭐ Merited by LoyceV (1) ,ETFbitcoin (1)
No... It would appear the addresses posted DID receive dust (a lot of 0.00001000 btc UTXOs back in 2015)...

1NwUfBG7kKNKjtoTbj8557Ty8MYiGXYupV
1NzGg6KKApR6M5SKSWGjfScsokVZK68yEc
1P2SjcwEJ1hrgWPjdFRfNiDvEpq6DJ8S8A
1P5JGtjq65L7mcW5B2ESHe8RCqQfW5KNE6
1P5QtTVmTYyPwqGU8BHJxQyndbgQ3gFzK1

However, they were all effectively "burned" in "null data" transactions that used the 0.00001000 btc as a transaction fee.

An example is decoded here: https://api.blockcypher.com/v1/btc/main/txs/99967491afcdddb7e1b695ec19f14cd4093d8eb4304de7f120209f392a5c9ab6?limit=50&includeHex=true

You can see the null data output:
Quote
 "outputs": [
    {
      "value": 0,
      "script": "6a",
      "addresses": null,
      "script_type": "null-data"
    }
  ]
Outputs like this are able to be "ignored" by a node... That is to say, they don't get stored in the UTXO set.

Normally, you would use this for arbitrary "data storage"... But nothing is being stored here, the "script" is simply "6a" (aka OP_RETURN). So the dust is just being burned. Maybe to reduce the dust clutter in the UTXO set... Or maybe just piss off the wallet owner and destroy all their coins? Huh

I'd say that unless the "real" owner (or at least the person who created these null transactions) comes forward... We'll likely never know.