|
Title: Blockchain.info wallet import "reversed" my transaction change. Post by: dbbit on September 13, 2013, 10:41:40 AM 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... ::) 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? Title: Re: Blockchain.info wallet import "reversed" my transaction change. Post by: dbbit on September 13, 2013, 11:30:30 AM Figured it out.
pywallet.py --dumpwallet Then paste the output into "Import Wallet" in blockchain.info. Title: Re: Blockchain.info wallet import "reversed" my transaction change. Post by: Mitchell on September 13, 2013, 11:45:39 AM So I think somehow blockchain.info missed the "return addresses" (what are these called anyway?) during the import. They are called change addresses and are used to increase security and anonymity. PS: Why are the return addresses for the change unique addresses, and not just the originating address? Title: Re: Blockchain.info wallet import "reversed" my transaction change. Post by: jackjack on September 13, 2013, 12:24:48 PM https://en.bitcoin.it/wiki/Change
Title: Re: Blockchain.info wallet import "reversed" my transaction change. Post by: DannyHamilton on September 13, 2013, 01:08:34 PM 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. |