Transactions from mining generation block sometimes not appearing in MultiBit wallets

[jim618]

I got a report yesterday of a serious bug as follows:

Transactions from mining generation block sometimes not appearing in MultiBit wallets

It appears that sometimes the transactions from your pool share of the 50 BTC block reward is not appearing in the wallet in MultiBit, even though the transaction is on the blockchain and you can see it in blockexplorer/ blockchain.info.

I recall someone else mentioning something similar to me in the past but I missed the significance of it - sorry.

Recommendations
For the moment, do not forward your mining block rewards to a MultiBit receiving address
If you have a receiving address in MultiBit that you have been sending mining block rewards to, check its balance against the same address in blockexplorer.com or blockchain.info. If they do not match look at 'Recovering your bitcoin' below.

I am in the process of buying an example wallet from a miner (not being a miner myself) so as to be able to reproduce the bug and fix it.

Recovering your bitcoin
If you unfortunately have a discrepancy on your mining block reward address you can either wait for a fix from me or do the following:

1. Choose the wallet in question in the wallet side panel.
2. Export the private keys WITHOUT A PASSWORD in the 'Export private keys' screen.
3. Open the output key file, select everything and copy it into your paste buffer.
4. Go to http://blockchain.info and either log in to your blockchain.info wallet or create a new one.
5. Go to the 'Import/Export' screen.
6. In the 'Import Wallet' text area, paste in the contents of the key file.
7. Press 'Import Wallet'.

This puts your private keys in your blockchain.info wallet.
(You sometimes have to log out/ shut down/ start up/ login again to get blockchain.info to refresh the wallet to see the transactions).

You should then see your mining block reward transactions.

Apologies for any inconvenience and I will be looking at the problem over the weekend.

Jim

[jim618]

This has been fixed in Version 0.3.2