This is a pretty deep issue I have been working on and off at for the last few years for somebody and my bounty is .2 bitcoin out of the deal.
It is a tricky situation, but maybe someone might know of a way...
Wallet was affected by the 0.5.1 bug where you know the password, but upon reopening the wallet it tells you that the password is incorrect. From what I have read among the issues of Multibit's downfall was that there was issues with how UTF16 and UTF8 worked. Some of the characters would end up mangled into other characters for some people.
What makes the issue more complex is that this was the 1 time the person did not write down the seed words.
I have tried many different ways, but I am really curious about what I find in the .YAML files.
0.5.1 version YAML files contain values for:
encryptedPassword: "88 Characters with /, + and 2 = signs at the end"
encryptedBackupKey: "64 Characters with / symbols"
Not sure if I am missing a step, but when I run base64 decode I get an output of ">����P�......etc"
I feel I am missing something, but maybe someone can clarify what I am doing wrong here.
Topic: Over .5 BTC in corrupt Multibit HD 0.5.1 wallet (Read 15 times)
Jump to: