Bitcoin Forum

had blocked payments (did not update) I closed and reopened and said the password unlock the portfolio, yet it is the one, I tried it with a brute force light, the password is so damaged? I had about half a bitcoin

sorry for my english,will pay 0,03 BTC for who can fix this issue
thank you

If you are using MultiBit Classic, this support note on using wallet backups may be useful:
https://multibit.org/en/help/v0.5/help_walletBackups.html

If you are using MultiBit HD, try restoring one of the cloud backups, or recovering from your wallet words.
Help:
https://multibit.org/en/help/hd0.1/restore-wallet.html

do you have your Wallet seed or a private key? if so you could upload the coins to a new wallet.

i have wallet HD,i lost the words, i not have the key,i have only the files, i tried the wallet on another pc but not work,the wallet show that can't unlock the wallet (but the password is correct)

Are you absolutely sure you have lost your wallet words ?
If you have them you can:

+ recover everything from a cloud backup if you have one
+ recover your bitcoins even if you don't have a cloud backup
+ recover your wallet password

If you DO NOT have your wallet words then your options are very limited.
Please have a think as to what you did when you were shown your wallet words at wallet creation. You must have put them somewhere because you had to type them in again on the verification screen. Did you write them on a scrap of paper ?


Every time MultiBit HD writes out a wallet it:
1) Encrypts them with the password you entered
2) Then DEcrypts them in memory and double checks the wallet is the same as before
3) Writes out the encrypted file and check the file size is what it should be.

Thus as long as you type in the password EXACTLY the same as when you created the wallet it should decrypt (because we have already decrypted it to double check the decryption works). You'll have to try things like case changes, transpositions etc with your password but really your wallet words is what you need.

because i have saved the words in the file txt and the system and hd gone in crash, tonigh i will try recuva for recovery files from HD...
however the correct password not work! why??
i had only close multibit and reopen

lost about 80-90$

If you can recover your wallet words then you can click on the 'Restore' button on the password entry screen and it starts a wizard to guide you through the recovery process.

i know, tonight i will try,but if i can't recovery the words from the hd?
i lost the btc?

Maybe your password was all in capitals when you typed it because you didn't notice the caps lock key was on or your password is backwards.

nope  :-[

however i seen with the brute force that the password is correct  :-\



 >:( >:( >:( >:(

Right read this link I've posted maybe this will help. This explains another method of recovery. Hope it works out hitting the sack

https://github.com/bitcoin-solutions/multibit/issues/620

in conclusion? with all those people did not understand what to do :-[

Your hard drive corrupted the files. The password is correct, but the files are damaged and cannot get decrypted... Data recovery is the only option.

I don't know why this only seems to happen with MultiBit files, though. I've never heard of corrupted files/decryption issues with other Bitcoin wallets... They must save the data in a safer way or something?

i have the backup in the directory of multibit hd but not work.

in the file .yaml  i have found
encryptedPassword
encryptedBackupKey

@paputa The reason why we ask you to write down your wallet words is exactly for the scenario you have encountered so it is unfortunate you have not done this.

With your wallet words it is straightforward to recover your bitcoins. In MultiBit HD the wallet directory has a structure (in various ways that I will skip over here) which means you CANNOT just 'copy some files' and expect things to work. That is the whole reason why we implemented the zip and cloud backups.

For instance, the encryptedPassword is to support password recovery for when people forget their password. It is encrypted with a one way function of the wallet words. You do not have the wallet words.

The encryptedBackupKey is an AES key derived from your wallet words and encrypted with your wallet password that is used to encrypt your cloud backups. To recover your zip/cloud backups you need your wallet words.

@f3tus We take great care in writing out wallets. When we write out the wallets in HD we:
1) check the decryption of the wallet bytes is reversible in memory
2) copy the existing wallet file to a rolling back up (there are 4 of these)
3) write out the wallet, check the size is ok
4) secure delete the oldest rolling back up

Plus there are a local zip backups and cloud backups described here:
https://multibit.org/en/help/hd0.1/backups.html

The user MUST know their wallet words to recover their backups.
The rolling backups (4 of them) load sequentially automatically so it is very unlikely all of them have write errors.

Even if all these backups fail because MultiBit HD is fully deterministic you can recover your bitcoins in MultiBit HD (or Lighthouse if you like) from your wallet words.

tl;dr You must write down your wallet words when you create a wallet in MultiBit HD to ensure the safety of your bitcoin.

ok but why the correct password not work? i have only close the program and reopen

It is hard to say from your description.
If the original PC you were using had disk problems it could be related to that.
PCs aren't perfect, which is what backups are for.

how can find a program exe for do a bruteforce?

i have found the words but are 16 words  ???

use Electrum to recover the coins then, (if the ''16 words'' means 16 word Recovery seed)

With MultiBit HD you can have 12, 18 or 24 wallet words but not 16.

There is also a datestamp (something like 1234/56) but that is always numeric.

The words for the wallet words will always be from the BIP39 word list, which is here:
https://github.com/bitcoinjs/bip39/blob/master/wordlists/en.json
if that is helpful.

i got the service http://www.walletrecoveryservices.com (http://www.walletrecoveryservices.com) without success

With a member of bitcointalk,we have seen that the password is correct but the wallet damaged,however i have decided of using electrum

@paputa Sorry that, in the end, you were not able to recover your bitcoins. We use the wallet words extensively in the recovery so without those options are limited.

Electrum is a very good wallet so I am sure you will have a good experience with that.
For your own peace of mind I recommend going through their recovery process (from the Electrum seed phrase) at least once. That way you will know what it entails and can see it working.

Regards,

Jim

thank you

Great news, paputa!!!, I just recovered your wallet!!.

I already sent you a PM :)

Thank you

 good person but above all honest.

If you need to retrieve the wallet go to him, very good.

Thanks again!

I'm glad you trusted me without knowing me, I know that's the hard part :)

So, thank you, actually.

Hope you're in contact with Jim to let him know what's causing this to begin with, he's going through another person's wallet to find out what happened/can be done: https://bitcointalk.org/index.php?topic=1205068.0

I'm glad to hear something CAN be done.

Well, the problem with paputa's files was that they were corrupted. I can't know why the were like that, but it could be because of many reasons: improper shutdown, disconnecting the power source, hard drive malfunction, etc.

a freeze of the program caused this, i has close the wallet and reopen but the password hasn't work

I can't be totally sure, but I really don't think that the software is corrupting the files. It must be another explanation.

@GoldTiger69

We suspect that the root cause is all the mutated tx flying around the network.
We've seen a stack trace that indicates that the password correctly decrypted the wallet file and then when the wallet was deserialised (i.e turned into an object) it wasn't consistent.

Specifically, a transaction has inputs which are the outputs of another, older tx. We've seen instances where this link wasn't valid which is almost certainly due to tx malleability. If the parent tx was the 'transaction that died' in a tx malleability attack you would see this.

What we plan to do in version 0.1.5 is:

+ not allow LowS signatures in the wallet at all.
+ at wallet load, if the wallet is inconsistent automatically perform a Wallet repair, which clears out all the tx and then resyncs.

This should eliminate this class of failure going forward.

Yep, hat makes sense. It should solve the issue of the inconsistent wallet.

Btw, maybe an option for a backup of the rolling and zip directories to a USB would be helpful? I have noticed that not many people trust Cloud places for a backup (I certainly don't, and not because of being hacked; but if they go out of business or simply they become unreachable, then I'll be paying the consequences). Just a tough.

What about MultiBit Classic? Same thing with corrupted files can and did happen there...

There is only essential network and safety fixes going into MultiBit Classic now.
Ideally we'd like people to move off Classic and onto HD (or another deterministic wallet if people prefer another client) now.
We cannot actually stop people using Classic but it is 'Bitcoin 2013' era so getting a bit old now.

I understand, but this would seem like an essential safety fix, and if it could prevent people from losing coins...

+1

I second this. You shouldn't just ditch a variant of your software especially if there is a possible solution to a bug users may encounter. It is far wiser to wrap that up where possible and then move forward.

The council approves this message.

Well the best fix is to have a fully deterministic wallet with wallet words that you can use to restore your wallet.
AKA MultiBit HD