In a word... Yes. Ledger even wrote a guide on it: https://ledger.zendesk.com/hc/en-us/articles/115005297709-On-which-wallet-can-I-restore-my-wallet-if-I-lose-my-Ledger-device-

Or... you can use decrypt_bitcoinj_seed (https://github.com/gurnec/decrypt_bitcoinj_seed)...

It will extract the 12 word seed from the Bitcoin Wallet backup file. You can then import that seed mnemonic into any BIP39 compatible wallet.

Previously, I would have said "AntPool" might take it... but it seems the "hidden" accelerator there has been abused by so many of the "helpful" people here offering free "acceleration services" (hoping for tips), that I'm not sure it is even working any more

If you are super nice and polite... and ask TrustedCoin very very nicely... there is a *chance* that they might agree to do a "one off" and sign a transaction that you generate from ElectronCash that moves all the BCH... providing that you can prove that you are the owner of the addresses etc (which you should be able to do as you can partially sign the transaction and can generate 2FA codes etc)...

Absolutely no guarantees that there is even a chance that they'll do this, but it can't hurt to ask... you're not going to lose anything and you might get your BCH, so I'd say it's worth a shot.

First up... please stop double posting... if you realise there is more to add to your post a minute or two later... click the "Edit" button and simply add the new comments to the current post. There is no need to create an entirely new post.

You have ONE password per Electrum wallet. You can't choose to have one to open and one to send. The same password does both.



Then the only 3 attempts at the 4-8 digit PIN before the device resets itself should stop them... and if they somehow guess that correctly, then the nice strong passphrase with at least 10 characters of lowercase, uppercase, numbers and symbols that you use should stop them getting into your wallet.

They would also need a copy of your wallet file... but it's not too far fetched to think that if they have access to your machine, then they probably have access to your wallet file.


If the wallet file itself is encrypted, they'd need the password to get into it... if they have a keylogger and can get your wallet password as well as your wallet... then your coins are gone.

If you use a hardware wallet, if they got your wallet file it wouldn't matter, your coins will be safe, because the wallet file won't contain any private keys... even if they have your password. They would need to physically have your hardware wallet as well. If you notice your hardware wallet is lost, you simply move your coins ASAP.

If you put bitlocker on, the entire drive would be encrypted and they'd need the password for that before the computer would even start up... it's possible they could use a USB hardware keylogger to capture directly from your keyboard, but that's easy to notice a little box between the keyboard and computer (or you can super glue your keyboard into the USB port so no one can unplug it to install the hardware keylogger ) But in theory, anyone with physical access won't even be able to read the drive contents as it would be stored encrypted.

Also, at some point, you're just going to have to accept that NO SYSTEM is 100% hack or disaster proof. There will ALWAYS be some way to compromise or break a system...

Paper wallets - can be lost or stolen or damaged by fire/flood etc
Brain wallet - not random enough and guessed by people bruteforcing, head injury causes memory loss
Hardware wallet - disassembly and reading of chip using forensic techniques, loss of password (same as brain wallet), loss of seed written on paper (same as paper wallet)
Software wallet - loss of wallet file (hacking, hardware failure), loss of password (same as brain wallet), loss of seed written on paper (same as paper wallet)
Offline Air-Gapped PC - loading of malware by someone with physical access... loss of wallet file (same as software wallet), loss of password (same as brain wallet), loss of seed written on paper (same as paper wallet)
Encrypted drive - loss of data (brute forcing of encryption, hardware failure), loss of password (same as brain wallet)

They'd have to keep an awful lot of private keys to be able to do this...

You can continually reset the device as many times as you like, generating a new randomly generated seed (and thus, new private and public keys) every time you reset it...

If it still doesn't show, can you confirm that you sent to the correct address, which I'm guessing is: 1PBkPU8Sdk5D82oMBC43HqabwbM1ZejubT

is that address contained in your wallet?

You need to set the password... AND make sure that the "Encrypt Wallet File" option is selected.

From the menus select: "Wallet -> Password"... enter your current password, then enter a new password (can actually be your current password if you want)... make sure the box is ticked.

Now, when you try to open that wallet file, you will need your password before it even opens.

If that is the first time you've used the 2FA to send... based on the amounts you have specified, I would guess that you have just prepaid for 20 (0.0002 btc) 2FA credits as per TrustedCoins current charges: https://api.trustedcoin.com/#/electrum-help



If you click the little blue shield in the bottom right corner, you'll see how many credits you now have remaining. Your next lot of 2FA transactions (equal to the number of credits you have) will be not cost extra until you run out of credits and need to prepay again.

What is the error message? Are you using an older version of windows like Win7 or Win8? and is it an error about Python35.dll like this?


If so, go back to using v2.9.3 available from here: https://download.electrum.org/2.9.3/

v3 doesn't play nice with older versions of Electrum.

or is it a completely different error message?

You can't export private keys from a 2FA wallet... it is effectively a 2of3 MultiSig wallet where you have 1 private key in the wallet file... The 2nd private key is "protected" (and recoverable) by the seed... and the 3rd private key is owned and controlled by TrustedCoin.

You can ONLY access the 2nd private key if you restore your wallet from seed... and "disable" the 2FA functionality during restore.

You will never get access to the 3rd private key.


If you have the wallet, and you have the password... and you still have your Google Authenticator... I suggest that you immediately create a new wallet (Electrum or otherwise) and send ALL your BTC to it BEFORE you lose the authenticator.

If you no longer have the Google Authenticator... and you've lost your seed... the coins are effectively stuck forever.

That's the point... you can't "claim" it... it doesn't current exist. THERE IS NOTHING TO CLAIM. There is no code, there is no wallet... there is no blockchain!!?!

The only thing being traded on a couple of shitty exchanges are some "tokens" representing BCD "futures"... you cannot deposit nor withdraw BCD... IF you happened to have some BTC on these exchanges, they would have credited you these tokens... people are gambling that BCD is actually going to happen, or that it is a scam.

Those selling, probably think it's a scam that isn't going to happen and are happy to sell what they consider to be "worthless" tokens to suckers buying them for BTC... The buyers think that BCD is actually going to be a "real" coin someday... and are hoping that the actual price once it exists will be higher than what they're currently buying it for.


- If it turns into a real coin and price is higher than now, the sellers maybe lose out on making more money... buyers can sell at the higher price and profit
- If it turns into a real coin and price is lower than now, the sellers "win"... the buyers lose, but there is the possibility it could recover at a later date.
- If it turns out to be a scam, the sellers "win"... the buyers lose with no hope of recovery

For now, unless you had BTC on the exchanges handing out BCD tokens... you get nothing... If it actually turns into a real coin, then you can think about claiming them.

No, you don't need to be online or synchronised... you can be completely offline and use "tools -> export private keys". In fact, I recommend doing it this way.

- Get offline
- Export keys from MBC with NO password
- import keys into Electrum (File -> New\Restore -> Import Bitcoin addresses or private keys -> copy/paste private keys, one per line -> Set a strong password on the wallet file)
- (Optional) write you private keys down on paper, so you have an offline copy.
- Delete the exported key file.
- Go online and sync Electrum.

For added security, you could consider doing a lot of that with a Linux Live CD/USB boot disk that has networking disabled and no persistent storage. That would help minimise possible exposure of your private keys.

Also, there is no "deadline"... the BCH (and BTG) will sit on those keys until it is moved by someone with access to the keys.


Yes, I would highly recommend moving the BTC as soon as you can... move them to a completely new wallet... and possibly your BCH too (you can use ElectronCash to get your BCH at the same time that you use Electrum)

Yes, if the file is in plaintext, anyone who gets access to that file will have access to your private keys and theoretically any BTC, BCH or BTG that has not been moved from the key.

NOTE: currently there are no decent wallets for BTG except the BitcoinGold Core wallet that requires a full blockchain download.

You know modern versions of Bitcoin Core use a seed as well right?

They just don't provide "access" to it by using a "mnemonic phrase" like most wallets do... although, theoretically, if you extract the seed (which is really just a very large number) from your wallet file, you could probably convert it to a "mnemonic phrase"

So you're sticking with the "non-HD" wallet format and multiple file backups then?


It's actually ludicrously simple... File -> New\Restore -> "standard wallet" -> "Use a hardware device"

You connect your Trezor (unlock it) and Electrum will read the xpub directly from it and recreate a "watching-only" version of your wallet (it even supports the randomised PIN entry system and passphrases for "hidden" wallets)... From this point, you basically use Electrum as you normally would... and when you want to send a transaction out, you need to have the Trezor connected to sign the transaction.

Pretty much the same goes if you want to use a Ledger Nano S...

Electrum with a HW wallet is actually pretty awesome... dynamic or manual fees, coin control, "freeze" addresses, PayToMany etc... backed with the security of a HW wallet.

There are several "experts" around here Myself and Chilly2k and one or two others...

Like... a couple of days after the fork as far as I'm aware: https://github.com/fyookball/electrum/issues/67

Basically, they had some issues with signing when using MultiSig, but I'm fairly certain it got sorted out... It was just the issues with 2FA that kept going and going... mostly because people were unable to read If multisig signing wasn't working, then the restored 2FA "workaround" probably wouldn't be working (as that has to use two sigs to sign a transaction)

So, theoretically, you can either just load up a copy of your MultiSig wallet in ElectronCash, or you can attempt to recreate the MultiSig by creating a 1of3 and using the xprv and two xpubs from your Electrum MultiSig wallet.

That isn't a private key at all... it is encrypted text that probably looks something like:


Electrum cannot import this.


As per the tutorial (https://www.youtube.com/watch?v=LaijbTcxsv8), you MUST export the private key without password protection. Otherwise you cannot open the export file to read the keys... you just get the big lot of "random" encrypted characters.

The private key needs to be in WIF format and show start with a "5", an "L" or a "K"... your export file needs to looks like this:


You then just copy/paste the Keys ONLY... do NOT just copy/paste the whole file... and do NOT copy the "date/timestamps" at the end of each line...

That'll be because you have "select server automatically" checked on the "Overview" tab. The network settings options were changed around a little in the upgrade from v2.9.3 to v3...

In v3, the "select server automatically" option was moved to the "Server" tab...


Yeah... looks like you'd accidentally configured Electrum to attempt to connect to a (non-existent) SOCKS5 proxy on your local machine

Don't forget, you're only looking at one address... the previous payment(s) to TrustedCoin were most likely from a different address/transaction chain...

If I was the OP, I'd contact TrustedCoin and ask them why they ended up with multiple lots of prepay... and possibly log an issue on the Electrum github issues list, seems like it could be a bit of a glitch.

Thanks for the headsup... will go grab that and start seeding it!