Topic: How to sweep a private MultiBit key into Electrum (Read 576 times)

I'm curious to know which method you used to unlock your BTC in the end.

Cheers!

I succeded to get a working key by using the script from https://github.com/gurnec/btcrecover. It turned out I had a typo in my password. Btcrecover found the right one.
Then produced a working key to sweep into Electrum.

See also https://bitcointalksearch.org/topic/trouble-recovering-multibit-classic-keys-1942459

I know this problem, i havent the same Issue yeahrs ago with multibit hd but my luck was i have my seed.
So i had the chance to calculate all my private keys with the iancoleman Tool
the only tricky problem was the exchange address in the wallet. the Derivation Path is " m/0'/0 " for normal address and " m/0'/1 " for exchange address
maybe this little info will help you?!

In a hex editor I copied the 32 bits after 08 02 1A 21 to Wallet Details in a local stored version of bitaddress.org-3.3.0.
(I downloaded it from https://github.com/pointbiz/bitaddress.org )
It generates a  Private Key WIF Compressed 52 characters base58, starts with a 'K' or 'L' and Private Key WIF 51 characters base58, starts with a '5'.
When a try to sweep these in Electrum it says: "No inputs found".
When I import that key beginning with a 'K' in Electrum it generates an empty wallet.

Hi,

i am in a very similiar situation.

I have some .wallet and .key files, but i cant get Multibit Classic to run and test my password.

I tried using the hex method and was able to get the private key from the wallets, but when i try to use electrum, it just doesnt recognize them.

Were you able to get your private keys?
And what happened when you add them as a new wallet to Electrum?

I have got a MultiBit key-backup map with the file multibit-201311xxxxxxxx28.key
The beginning and the and of the rows in the .key file are looking like this:
U2FsdGVxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxToxPXSx
xgFIbGS/hxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0MeL1rl
(the x's are replacement of the original characters)

When I run in the terminal: enter aes-256-cbc decryption password: xxxxxxxx

It returns:
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
salt=7DAA3xxxxxxxxE5A
key=1ED71A42Fxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx316AEB828
iv =95D359xxxxxxxxxxxxxxxxxxxxx09CAE
bad decrypt

The content of encoutput.txt shows 64 characters like this:
5Éä
Ñч­�8=™xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxÍÞ^¸�ãlÔÈÌ]Û·

When I open the .wallet file in a hex editor it shows this:
0A 16 6F 72 67 2E 62 69 74 63 6F 69 6E 2E 70 72 6F 64 75 63 74 69 6F 6E 1A 6D 08 02 1A 21 (the beginning of the file in hexadecimal)
..org.bitcoi[Suspicious link removed]oduction.m...! plus a lot of meaningless characters for me in ISO-8859-1
End of the file shows this text: org.multibit.walletProtect.2.....Z"De beschrijving van je portemonnee`.h.

I also have a .wallet.cipher file: multibit-201311xxxxxx16.wallet.cipher. When I open it in a hex editor the value begins with "mendoza"

I have got the address of the wallet and it is showing some mBTC in Electrum
How can I sweep the private key in Electrum?