I was sending a test transaction from my Blue Wallet (watch only) wallet which is linked to the jade wallet , to my Coinbase wallet.
I created the transaction in Blue Wallet and put my Coinbase wallet id in the TO field. I sent a small amount of btc, say $5.
When I scanned the QR code on my jade to sign it I noticed there were two outputs. One showed my Coinbase wallet ID and the $5 amount I was attempting to send.
The second output was for the remaining amount of btc on the source wallet and the to wallet id was unfamiliar to me.
I know that UXTO might require that I send and receive “change” back, so maybe that is expected. But when I look at the wallet ID in that second larger transaction, it is not one of the wallets I see in my Blue Wallet app when I look at all the “receivable” wallet ids listed, about 10 of them.
I know there is some obfuscation built in to the uxto process to retain anonymity but I was expecting the to address to be one of the ones listed in the wallet app.
How can I confirm that the TO wallet for the second transaction is mapped back to my original wallet, and isn’t just some attacker somehow injecting their own wallet into the transaction somehow?
Sorry if this is a dumb question this is my first time learning and testing this out. I want to feel confident I know how this process works. Any help is much appreciated.
Edit: just in advance: this is a throwaway, I won’t be responding to any PMs, and also there is no significant money here I am just testing things out.
Posted by Aggressive-Wave-3311
1 Comment
>How can I confirm that the TO wallet for the second transaction is mapped back to my original wallet, and isn’t just some attacker somehow injecting their own wallet into the transaction somehow?
Currently travelling but from the top of my head, you can scan the address QR code(?) by the air-gapped jade and the device should confirm if the address is yours or not.