Bitcoin Forum

Other => MultiBit => Topic started by: Dave54321 on December 22, 2016, 11:14:29 AM



Title: Old transactions suddenly unconfirmed
Post by: Dave54321 on December 22, 2016, 11:14:29 AM
Yesterday I purchased 0.25 bitcoins to add to my balance. However, shortly after the payment had been made, the balance in my wallet suddenly started showing as totally unconfirmed - I mean every transaction made since I started in October 2015!

I did a wallet repair, and things improved, with all transactions confirmed except for the earliest two transactions. I have run two further wallet repairs, but still these early transactions are unconfirmed.

I didn't realise that a confirmed transaction could revert back to being unconfirmed. Could anyone advise if I need to do anything, please? It's a bit worrying! Thanks in advance. I'm using Multibit HD v0.4.1


Title: Re: Old transactions suddenly unconfirmed
Post by: steven0021 on December 22, 2016, 11:18:42 AM
It's an old bug with multibit. Try repairing the wallet (Manage Wallet > Repair Wallet) and verifying the network (Tools > Verify Network). I'd create a new wallet if I were you. It seems like this problem is persistent and will keep coming back.


Title: Re: Old transactions suddenly unconfirmed
Post by: Dave54321 on December 22, 2016, 05:42:03 PM
Thanks Steven, I'll do that.


Title: Re: Old transactions suddenly unconfirmed
Post by: Dave54321 on December 23, 2016, 12:46:57 AM
Repeated repairs have done nothing, unfortunately. I no longer trust Multibit HD.

If I install a different client, e.g. Bitcore, would I be able to import the existing wallet? I wonder if that would fix it?


Title: Re: Old transactions suddenly unconfirmed
Post by: shorena on December 27, 2016, 06:43:43 AM
Repeated repairs have done nothing, unfortunately. I no longer trust Multibit HD.

If I install a different client, e.g. Bitcore, would I be able to import the existing wallet?

No, you will have to send all your coins over to the new wallet.

I wonder if that would fix it?

Bitcoin core does not seem to have this problem. Did you try updating to 0.5?