Author

Topic: Blockchain.info wallet import "reversed" my transaction change. (Read 954 times)

legendary
Activity: 3472
Merit: 4801
Figured it out.

pywallet.py --dumpwallet

Then paste the output into "Import Wallet" in blockchain.info.

Another option would have been to send the entire balance from your -QT wallet to a single receive address in your -QT wallet prior to importing.  That way none of the balance would have been associated with a "change" address.  I'm surprised that the import doesn't recognize "change" addresses.  Hopefully Piuk fixes that in the near future.  It sure seems like an oversight on his part.
legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
copper member
Activity: 3948
Merit: 2201
Verified awesomeness ✔
So I think somehow blockchain.info missed the "return addresses" (what are these called anyway?) during the import.

PS: Why are the return addresses for the change unique addresses, and not just the originating address?

They are called change addresses and are used to increase security and anonymity.
sr. member
Activity: 322
Merit: 250
Figured it out.

pywallet.py --dumpwallet

Then paste the output into "Import Wallet" in blockchain.info.
sr. member
Activity: 322
Merit: 250
I've imported a bitcoin-qt wallet.dat into blockchain.info.

For some reason, blockchain.info ignore the "change" that you get as part of a transaction. So now the balance is way off.

E.g if you look at:
https://blockchain.info/tx/2f2b2b49523fe9c964115efdf7fc2254caa52dba33055f1ab500cccae900ccbd

I spent BTC 0.25 from an address with BTC 1 in it, so I got BTC 0.75 in change. Yeah, BlockChain.info just see it as I spent BTC 1. Uhh...  Roll Eyes

So I think somehow blockchain.info missed the "return addresses" (what are these called anyway?) during the import.

How do I fix it?


PS: Why are the return addresses for the change unique addresses, and not just the originating address?
Jump to: