Based on the transactions history of the address you sent the coins to, It seems you are always following some kind of pattern.
This is the address you sent the coins to:
https://mempool.space/fr/address/bc1qhvppc7apsykmas05aj46xs6ws6qm8h5ytmtg7fI don’t know why but it seems there is a kind of pattern: you usually send exactly 330 sats (which happens to be the dust amount for taproot transactions) to that address and the change goes back to the sending address.
Afaik,
it’s not possible to disable the change address in Sparrow. So, you need to do that manually by adding the sending address as an output.
Not sure what has gone wrong this time, but if you tell us how you create those transaction (do you use some kind of automated tools?..) then someone may help you figure out what happened.
edit: I believe this has something to do with Ordinals.No, I didn’t send any 330 sats. What happened is actually more ironic, given that I’m a student at a German university of applied sciences studying computer science. I have experience with crypto and wouldn’t make a simple mistake with the fee. I understand how it works in the background. I also have experience with Linux and usually sign all transactions on an Ubuntu Live system without internet access. I did the same this time using Sparrow Wallet 1.9.1. It’s always been the same wallet software. I broadcasted the signed transaction on my regular system with internet access.
Originally, I had 0.99145586 BTC in address bc1plulf79mdaq5zs2murey923vl3uvj4xnhgg0y64ggxgrvrem6mxqql8hple. I signed a transaction to send 0.2 BTC to my other address bc1q86gqjatdx8hftz34muezq6afjsj90tjlze9vnh. The remaining 0.79145160 BTC was supposed to return to my change address bc1pvxn38z656zd0e3mflyzxx9lu3s0mtgej3d9xndd3f8jwwk7twe5s4zaf0l. It did.
However, a few minutes later, I realized I’d left the SD card with the unencrypted seed phrase in the card reader and system was online. For safety, I decided to move the entire change to a new address derived from another seed phrase that wasn’t potentially compromised. Since the old seed was available on my system with internet access, I skipped the usual offline signing process and sent the transaction directly.
That’s when things went wrong. Although the address I entered was correct, I received a transaction error. I tried again, and it worked. After completing the transaction, I noticed the recipient address was not mine. In a panic, I tried to cancel the transaction. Sparrow Wallet allows this, but I’m not sure what fee I selected—I think the fee slider was set to about $10 with a 1-block confirmation. I confirmed, but Sparrow Wallet gave me a transaction error. I switched to another broadcasting server in the properties and tried again, but the same error occurred. By then, the transaction was already confirmed.
I’m not entirely sure what happened or what the recipient’s address was, but it definitely wasn’t mine. The 330 sats you mentioned are not in my wallet, and I don’t know whose wallet they are in. I’ve attached some screenshots if that helps.
This is my wallet:
https://i.postimg.cc/T2K9XQW9/1.pngThese are receiving and change addresses I had in my wallet:
https://i.postimg.cc/G36j3YF1/2.pngThis is my original transaction of 0.2 btc to my wallet:
https://i.postimg.cc/9z3z3cwv/3.pngThis is the transaction of the change
https://i.postimg.cc/7hB879wX/4.pngAlso, just noticed this post from Binance...
https://x.com/binance/status/1834834513702117720Could it be my case?
