I suspect you simply missed the change addresses when exporting the keys from your core wallet.

So when you sent the BTC out, it would have take all the BTCs from the change addesses as well. However, you've only exported the keys for your 8 "receive" addresses... and not your "change" addresses (FYI, these don't show up in Bitcoin Core when you goto "File -> Receiving addresses" list)

Have a look at the actual transaction(s) where you sent all the BTC from Bitcoin Core to your new Core Wallet on a blockexplorer... how many addresses show there? Did you import the keys for ALL of those addresses into ElectronCash?

No, you only need to sync it to see the transactions. If you load it up and use "dumpwallet" you should be able to get all the addresses and keys straight away.

"salvagewallet" is a last ditch attempt to extract keys from a wallet... it is not recommended unless you have exhausted all other options of wallet recovery... as it can mess up a perfectly fine wallet.

If you are having issues getting Python added to the PATH, simply type the full path to Python when you are trying to run it... so you would use the following command:

C:\Python27\python decrypt_multibit_classic_walletkeys.py multibit.wallet

That should then start it running

You cannot merge two different wallets into one. Jaxx uses a single seed to create all the different altcoin wallets.

You would need to create a new wallet in Jaxx with a new seed... and then send the BTC and ETH to the new wallet.

DO NOT USE MULTIBIT!! (Classic or HD)... both are old, outdated and no longer supported by the developers... HD also has some really bad bugs that will potentially lock you out of your wallet and make it really difficult to recover your coins.

Bitcoin Core if you want a full wallet
Electrum if you want a lightweight wallet
Trezor and/or Ledger if you want a hardware wallet

You can't get BCH from Electrum... you can only get BCH from ElectronCash... they're two different programs.

Also, looking at the BCH block explorer... you're correct, all the BCH from your 1AcQ address was moved in this transaction: https://blockchair.com/bitcoin-cash/transaction/243725249#o=0

If you never created/sent this transaction, (did you do a sweep transaction?) then someone else has the private key for the 1AcQ address... I see all the BTC was also moved from that address here: https://blockchain.info/tx/3487420c502b9c0779c66515903c364f4ca4a29bc43805c2e6e03092fae1f045

If you didn't send the BTC transaction, then someone else definitely has the private key for the 1AcQ address and both your BCH and BTC have been stolen and there is no way to get those coins back, they're gone.

Electrum works perfectly fine with compressed keys?? What are you talking about? Quoting stuff from 2012 isn't that useful

OP, you DO NOT want (or need) to convert it from compressed to uncompressed... you'll end up generating a different address within Electrum and, as you have discovered, won't be able to see your coins...

Just make sure you are using the most recent version of Electrum and import the "L" key... using "File -> New\Restore -> Standard Wallet -> Use Public or Private keys"... then paste in the L key one per line.

you shouldn't move the multibit_recovery-master files anywhere... you just run from where they are.

Also, you're trying to run the python script from within python, which is why you get the syntax error. You need to run it from the "normal" commandline...

To open a commandline where you extracted the scripts, you need to press and hold the "Shift" button and then right click in the folder... you should see an option in the menu that says "Open command window here"... make sure you're right clicking on an empty part of the folder window and not a file... otherwise you'll get a different menu


The prompt should say something like "C:\Path\to\multibit_recovery-master>"

Then you simply type python multibit_recovery-master multibit.wallet and press enter

I'm not sure they will be easily recoverable... mSIGNA uses "MultiSig" P2SH addresses for everything... even single signature addresses (They're set up as 1of1 addresses)... this makes it quite difficult to export the keys

The issue with P2SH addresses, is that you generally can't just "import a key" into another wallet and spend coins... you need to know what the original script was.

with the xpriv, there is a chance you could just recreate the private/public keys... and use something like coinb.in to create redeem scripts and craft manual transactions and sign them to be able to spend the coins... but unfortunately, I don't know what the BIP32 derivation path is for mSIGNA... I can't find any record of it being mentioned anywhere... and I've been looking through the mSIGNA github without success... I'm not terribly familiar with C++ so some of the code doesn't make a lot of sense to me

At this point, your best bet is to try and get mSIGNA talking to your Bitcoin Core node so you can just send the coins out of the wallet. The fact that you sent coins before it was synced up shouldn't make any difference. mSIGNA should still be able to find them.

In the bottom right corner of the mSIGNA window, do you see something like "483594/483594" with a Green Tick icon?


If not, then it would seem that mSIGNA is not talking to your Bitcoin Node properly...


Also, if you manage to get in touch with mSIGNA support, maybe you can ask them what the BIP32 Derivation Path is

Why don't you just order it from https://www.ledgerwallet.com ? The ones I've seen for sale on Amazon etc are all ridiculously overpriced and expensive...

Theoretically, you can simply shutdown Electrum, make a copy of the default_wallet file... then delete it from "/Users/[Username]/.electrum/wallets"... then start Electrum and it will ask to create a wallet... you can select the "I already have a seed" option, type your seed in... add a password if desired... and your wallet and all transactions will be restored.

Uninstalling probably won't work, as it won't remove the Electrum data dir with the wallet file in it. I believe that on OSX, Electrum is storing it's data in a folder called .electrum in your home directory. I've not used Electrum-LTC, but I would assume it uses .electrum-ltc or something similar

If you have your seed, then you can delete the contents of that folder and then you should be able to restart and create a wallet from scratch. (Note: You will probably want to make a backup of the "wallets" folder before you delete everything in .electrum-ltc... #justInCase )

The correct Derivation Path is definitely m/0' for importing MultiBit HD seeds into Electrum.

I think that what has happened is that the change address "1NJGvFX..." that received the 0.16 BTC from your transaction may be past the "Gap Limit" in Electrum for change addresses (by default I think it is only 5)...

Open the console tab (you may need to use "View -> Show Console" if you can't see the console tab)... and then type:

print wallet.create_new_address(True)

This will generate the next change address in the sequence, you may need to do this several times depending on how far down the list that address is. You can also try and bulk generate them 50 at a time by using:

Note that the text is case sensitive (True not true), the spaces before the "print" command are required, and that you need to press ENTER after you type in each line

You shouldn't need to delete anything or use a different computer.

If your "old 2fa wallet" that you can open in ElectronCash shows BCH, but when you "restore" your seed and the "new 2fa (disabled) wallet" shows 0, then I suspect you are actually restoring a completely different seed! Are the addresses in the two wallets the same?

There must be something very odd with your installation... perhaps some security software or firewall that you're running or maybe some weird permissions issue or something is causing your problems.

I've not had major issues with either Electrum or ElectronCash on Windows 10 (or Windows 7 in a VM for that matter)... they both run quite happily on the same machine at the same time:



Also, I think you meant to say that you removed the "..\AppData\Roaming\Electrum" folder

Note that if you choose to import a BIP39 seed into Electrum... that you will NOT be able to view the seed words at a later date from within Electrum ("Wallet -> Seed" option will be greyed out). Electrum does not store BIP39 seed words encrypted in your wallet file like it does with native Electrum seed words.

Not a massive issue, if you have your seed words written down safely... but just something to be aware of

Is your Electrum wallet a Two Factor Authentication (aka "2FA") wallet? "3" addresses in Electrum are usually from a 2FA wallet... but can also be from a "MultiSig" wallet. These addresses actually require multiple private keys to be able to send coins. They cannot easily be "imported" into another wallet.

A "3" address from an Electrum 2FA wallet is a "2of3" MultiSig and actually has 3 private keys. 1 key is controlled by TrustedCoin (you need a Google Authenticator code to get them to sign a transaction), the other 2 keys are controlled by your "seed words". By default, 1 of these seed words keys is stored in the wallet file. This is the private key you get when you "export" the private key from Electrum.

The 2nd private key is only stored in your wallet if you restore it using your 2FA seed words and choose "DISABLE" when prompted to keep or disable 2FA functionality.

Any combination of 2 of these 3 private keys will be able to sign a transaction that is able to spend coins from the address. However, you will struggle to be able to recreate your "3" address in another wallet unless it allows creation of MultiSig Addresses and even then it won't be easy.



That is incorrect.

What version of Electrum are you using? I suspect you are attempting to use an older version, as the latest version (v2.9.3) asks for the Derivation Path, NOT the BIP44 Account number... perhaps this is what is causing issues?

I've just tested with a Trezor test seed that I use, and 2 different passphrases using Electrum v2.9.3... and both times it is generated the same addresses as the Trezor wallet with that seed and those passphrases

1) What Kind of Wallet do you want to create? "Standard Wallet"
2) I already have a seed.
3) I enter the 24 word seed, select advanced options and tick both boxes ("Extend this seed with custom words" and "BIP39 Seed")
4) I then enter my passphrase in the "Seed Extension" dialog box.
5) It will prompt for Derivation Path... Leave as m/44'/0'/0'
6) It generates addresses which will be the same ones as your Trezor.

It's showing as zero because of this transaction: 1daa2586a9bc0db13f2d286ccc5f81f4c4b7588880f2de1643831bf38e0c1b50

It is attemptig to send your 0.8 balance... it was created on 18/08... So you wallet has detected this and adjusted your balance to 0, as effectively those coins are no longer in your wallet.

However, that transaction has a fee of 0... So is likely to get dropped by the majority of the network and won't propagate well... And it's unlikely to get confirmed.

You may need to reset the wallet to get the balance to show correctly again (maybe restore from seed?)

OP seems to be very confused...

MultiBit Classic (v0.5.14) generates .key files... They are generally encrypted with wallet password and result in the random text starting with a 'U2' and ending with '='

Refer here: https://multibit.org/help/v0.5/help_exportingPrivateKeys.html

There is NO SEED for MultiBit Classic.

However, there is a seed for MultiBit HD, but that will generate a completely different wallet than the one containing the keys from MultiBit Classic.

OP, you need to establish if your coins were in MultiBit Classic or MultiBit HD. They are two different programs with different wallet formats.

If it was MultiBit Classic, do you know the wallet password for your MultiBit Classic wallet? If so, recovering the actual private keys from should be a relatively simple task.