Is this still something you are working on, I think I might be a good candidate for your services, but it appears you are no longer doing this?

https://www.reddit.com/r/Bitcoin/comments/7hjhs2/need_help_recovering_10_btc_from_multibit_classic/dqsbbl3?utm_source=share&utm_medium=web2x&context=3

Here is the dude who claimed the same thing. I have never been able to pin one of them down and get a definitive answer.

At this point my locked wallet is a nice payday for someone to figure out. If you want DM me what you are comfortable offering as a bounty for a solution.

I am facing the same problem. Some other people on reddit said they have the same error message and it ended up being an incorrect password. It is highly suspect that we are facing the exact same issue though. I have a wallet that I created in 0.5.14 that gives me the same error message when I entered in one of the main passwords I used.

Someone also told me there were messages in the code indicating that the way the wallet was encrypted changed between 0.5.14. and 0.5.15. It is also strange that they removed that version for download. Not saying that is a cover-up but I did want to try decrypting the wallet with that version in case by some miracle it is able to decrypt the keys/ wallet.

Are there other threads you know of with people facing this same issue?

Has anyone had any luck? Autoband?

I was digging into it a little today after forgetting about it. It looks like when I encrypted/ added a password to the wallet it created two separate wallet files. The strange thing is from the .info files both state there are three receiving addresses. The first wallet file has 2 of the 3 receiving addresses, the other has the other 2 of the 3.

Pretty strange, still think mine might be a corrupted file...

How many are left? I'm interested.

Oh sorry, the Bitcoin airdrop is still in process...

The signature campaign was completed.

It says there is a deadline of Feb 25th but also "the event has been completed" on the website it doesn't say that it's been completed, so I guess I will register and hope for the best.

To update anyone who care besides Autoband, I somehow was able to open a copy of a wallet that has the locked private keys in it. To my surprise there is a transaction from 2017 in June. The AES error appeared back in 2014.

I'm hoping that by some miracle I might be able to resync the wallet with the unlocked copy and restore the funds, but now I need to find out which computer it was sent from since I have opened it on several different computers and several different wallet files, with different versions of Multibit.

I think maybe one wallet backup is somehow not corrupted, but the problem was when I sent out the .005 BTC it did not display the balances with actual BTC in it.

It appears that Autoband may have updated the Multibit with the keys encrypted, (as I may have as well) resulting in the corruption??

So you had the "AES key is wrong" error or no?

If you did, are you saying that it was an incorrect password even with that (AES) error message, or did you have the cannot decrypt bytes message?

Mat008

It seems like spockrates was not getting the "AES key is wrong" error in the software, so it must have been a password issue. How this wallet was around for so long is unbelievable, with all the bugs

Spockrates,

What error does it give you when you type in your correct password in the actual multibit software GUI?

Autoband and I both get provided AES key is wrong instead of the usual "could not decrypt bytes"

Thanks

I was talking about when you load the wallet in Multibit Classic and try remove password with your known password does it give the AES error or cannot decrypt bytes. There are a few people with the "AES key is wrong"

Simon,

Do you get the error "provided aes key is wrong" when trying to remove the password from the wallet? You might be one of the few unlucky people who had Multibit corrupt their wallet.

No response from wallet recovery services

Also I tried this guys tool, to export the private key, when I enter the wrong password it gives a bad decrypt error, when I enter the correct password it gives a "not a valid private key" error. The search continues.

Did you get in on the SALT ICO pre-sale by chance, that is the main thing I was interested in, was the pre-ICOs...

Thanks

I am approaching Dave at wallet recovery services to see if he has any ideas, so it might be of some help. HCP tried to figure out what the correct password decrypts to 94 characters using his utility but to no avail. I will report back here if Dave is able to help. I'll send some BTC to HCP if I am able to crack the wallet, it has now become a life changing amount of money stuck in the wallet.

Autoband are most of your .cipher files in Chinese? Wonder what caused that?

Any luck gentlemen,

I am having the same issue, although I am less competent at code than both of you. My situation was pretty similar.

HCP scripts appear to attempt to decrypt the keys and wallet file, but I get the same error message as Autoband86.

I was chatting with a couple of the original devs on Github about this who were not of very much help. I can offer up a bounty of 1BTC for a solution.

HCP the wallet cipher decryption did not work for me either   (I have all the same files as autoband and confirmed in the wallet.info file the wallet with the address with the bitcoin)

I think what I did is upgrade from version .14 to version .15 then I put in the password. Prior to testing if the password unlocked the wallet I transferred the coins to cold storage from the exchange (since everyone tells you to do that) now they might be in permanent cold storage

I was thinking about buying a keep key as they have a script to move private keys from Multibit classic to their device, as a hail mary as well...

If you read the "authors" other "articles" you will understand he/she does not know the first thing about writing, journalism, or Bitcoin.

Do you think this could possibly cause a corrupted wallet, also did you know if you can import an encrypted private key into electrum??