Author

Topic: Restoring Multibit wallet? HELP! (Read 512 times)

HCP
legendary
Activity: 2086
Merit: 4361
May 16, 2017, 01:32:32 AM
#3
As I have explained in several other threads... it isn't that your password has been change or stopped working... it is just a "bad" error message being output by the application.

The easiest recovery is to simply install breadwallet on an Android or iOS device, restore using your MultiBit HD seed and you should have full access to all the funds that were in your MultiBit HD wallet.

Alternatively, if you use my python scripts... specifically the find_unspent_multibitHD_txes.py script, you will get:

1. a list of the UTXOs in your MultiBit HD wallet, along with a list of the matching Addresses/Private Key(s) for these UTXOs
2. a plain text output of your wallet (parsed_wallet.txt) NOTE: all seeds/private keys are still encrypted in this file.

My investigation into the source of this issue leads me to believe that newer transactions are unable to be parsed correctly by the wallet. This manifests as a "Transaction did not deserialise completely" message in the application debug logfile. Unfortunately, the wallet does not handle this error properly and returns with the "Password did not unlock the wallet" error Sad

If you need any help, PM me...
newbie
Activity: 1
Merit: 0
May 15, 2017, 01:56:58 PM
#2
I'm experiencing the same shit right now. This is my second multibit wallet where the password suddenly stops working. First one I just assumed was hacked, but now multibit can go to hell. Seed words don't restore, just "working..." for hours at no result.
newbie
Activity: 4
Merit: 0
May 15, 2017, 01:10:04 AM
#1
So after this shitty wallet decided to change my password I had to restore my wallet by using the seed.

I have the seed but my wallet has been synchronizing for the past 48 hours and still can't get into my wallet.

How long does this process last? Theirs no way it should take this long!



I recommended everyone stay away from multibit wallet!!!!!!!



Any help please email me: [email protected]
Jump to: