I'm quite new to this, so no teasing the newbie. ;-)
I've just tried to import my wallet from the bitcoin-qt client into blockchain.info, and whilst the process seem to go swimmingly they both show different balances, with blockchain.info showing that I'm down one full bitcoin!
Now I know that there are other answers about that subject on the site, but I haven't found an answer to these specific questions (That I was able to grok!). There seem to be a multitude of ways somebody new to bitcoin can spectacularly b0rk their wallets, so many that I couldn't quite make any particular problem fit my situation.
However, a user on another question posted that they'd been able to solve their problem by doing the following:
As it turns out, the import did not pick up all my addresses/keys. By comparing the output from pywallet --dumpwallet and the blockchain.info exports I was able to identify the missing keys and add them manually. Both balances match now :-)
So I have a two part question:
- I think I can work out how to do what he's suggesting with some googling, but I don't know why this solution would work, can somebody enlighten me?
- I've read that it's possible that my balances are different because my client wasn't in sync with the network when I did the export/import process, could this have a bearing on the problem?
- And if this is a contributing factor, will just leaving the bitcoin-qt client running on my machine until it synchronises with the network cause both blockchain.info and bitcoin-qt to show the same balances?
- Or do I have to do start the whole process again after the client has synchronised?
(I know, I know, that was more than two questions :-))
Any help would be greatly appreciated!
EDIT: As to why I wanted to do this, I wanted to move away from the bitcoin-qt client to another one because I was having performance problems with the original. I thought I could export everything to blockchain.info, and from there export my wallet into a new client. Convoluted, yes; completely misunderstood, agreed, but that's where I'm at.