Topic: uploading wallet.dat to blockchain.info shows 0 balance (Read 734 times)

I can't because I have no posting history

the basic question I have is *if* I drag wallet.dat to blockchain.info and it does not show all the transactions that bitcoin-qt shows, why is that, and what procedure should I follow to sort it, or should I just give up on the blockchain.info wallet.dat import procedure

second question is, what is the total size in GB of the blk*dat and blkindex files, currently?

another question is, can these be downloaded anywhere to seed a new install instantly, for 0.8.x? because links to places previously mentioned no longer exist

thanks.

hmm im not sure ask in technical section

For various reasons running bitcoin-qt has become too difficult, if the computer crashes, for other reasons I won't go into, while it is up but not doing anything, then when it starts again I'm in for days (DAYS) of "catching up".

When I drag wallet.dat to blockchain.info then inspect, I see only the transactions in and then instead of individual withdrawals I see offsetting withdrawals of the same amount (in other words, it is not showing the correct set of withdrawals shown by bitcoin-qt) and the balance is 0.00 instead of what it should be.

When I dump the wallet with pywallet, there is an array of 110 keys each with fields hexsec, private, pubkey, reserve, sec, secret associated with different addr entries

1/ Why are there so many keys?
2/ Why didn't blockchain.info fully import the wallet?
3/ Do I have to manually import each "hexsec" but what about telling blockchain.info about each "addr" associated with it? Since I'm confused as to why importing a wallet.dat didn't work, I'm worried about going further down that rabbit hole.

Obviously I can let this particular instance of bitcoin-qt churn away for days and crawl to 100% although since it is 0.7.x I'm not sure if the May 15th thing will break it. Then I can just transact out the bitcoins with a transaction elsewhere.

BTW if I load up 0.8.x on a different computer (imac) it also runs for days "catching up" and has the same stability problems when the host crashes, as 0.7.x did.