Even if you have an old seed you should use the latest version of electrum from electrum.org. Electrum maintains backwards compatibility with all old seed mnemonics.

How do you know the hash of the preceding blocks is the true hash? You will have to trust someone. Bitcoin is all about not having to trust anyone.

There is another risk with sharing the xpub. If any of your private keys are made public and your xpub is made public you whole wallet can be compromised. So that's one more reason why electrum doesn't share the xpub. Actually it only sends hashes of addresses to servers. It used to send addresses as is but now uses hashes. I'm not sure why it sends hashes though. The server operator only has to take a few extra steps to get your addresses if he wants them.

You need python 3.6 for 3.3.x branch. If your distro has that then install it otherwise stay with 3.2.4. Note that 3.2.x branch won't receive further updates so you will have to upgrade eventually. See if there's a newer version of your distro  or wait until the electrum appimage is released:

https://github.com/spesmilo/electrum/pull/5042/files

To use your wallet.dat file you place it in an empty directory. Then simply download and install bitcoin core from bitcoincore.org and the first time you run it it'll ask you for the location of the data directory. Point it to the directory with the wallet.dat file. It'll then load your wallet file and start synching the blockchain. The blockchain is some 200GB so if you wish to continue using bitcoin core you will have to wait for it to download and verify all that. It'll take a few days. Note that you don't have to store all 200GB. You can enable disk space usage limits in the software settings (look for the settings option in the menus).  However you will have to download it all.

Alternatively if you want to bail you can go to help > debug window > console and then type "dumpwallet </path/to/dump/file>" to dump your private keys. If you have a password set you may have to do "walletpassphrase <password> 600" first. Then you can open your wallet dump file using a plaintext editor like notepad and sweep your private keys into electrum. Your private keys are the long strings beginning with 5,K, or L.

That domain eleclrum dot org does currently 302 temporary redirect to electrum.org.

These fake sites get most of their traffic from ads on search results pages. When you submit an ad in adwords google does some checks to make sure its all kosher so it could be an attempt to fool automated checks by google's bot.

It's inheriting from QThread so I'm guess it happens when you run start. Start is defined in the parent class and it must be calling run.

Yes that's it: http://doc.qt.io/qt-5/qthread.html#start

this was resolved on reddit: https://www.reddit.com/r/Electrum/comments/akk7ej/electrum_wallet_issue_lost_funds/

Restore from seed does work. Choose multisig wallet and then 2 of 3. In the seed entry step click on options and check bip39, enter the seed and make sure once you've done that it says 'bip39 checksum ok' next to the options button. If it doesn't then check the spelling and order of the words. In the next step select "legacy p2sh" and enter this derivation path (single quotes matter):


Repeat this for each seed. That's all you have to do.

@HCP the derivation path is where you went wrong. Copay uses bip44 for multisig wallets as well.

AFAIK hardware wallets aren't designed for offline use. They are designed to make securing and handling your bitcoin easy i.e. without having to resort to cumbersome offline wallets. I'm guessing it worked after the sync because electrum now had data related to your unspent outputs. Data that it can only get from the blockchain.

If you want to resort to offline storage then you have no need for an HW. Electrum can do that for you for free.

You are right that the OP may be a victim of a scam where the attacker gets the victim to add his addresses as watch-only to a bc.i wallet. However addresses are not public keys. Please use the correct terms or we get questions like these.

It doesn't though: https://bitcoin.stackexchange.com/a/12438/5273

When you set a password for the very first time it changes the master private key and adds new keypairs derived from the new key to the keypool. Old keypairs derived from the old xprv are not deleted though. IDK whether it continues to use those or not.

You may be waiting for years. Just switch servers.

You have to switch to another server and do the transaction again.

The only thing you need to do is that in the event you get an error message when spending bitcoins try switching servers. Don't download any software that the error message tells you to.

Thanks for letting us know. That's a new one!

best to remove the local transaction and start again via the send tab.

That shouldn't be happening. The receive tab only hands out unused addresses. Perhaps electrum wasn't synced when you first switched to that tab? Try restarting electrum. Make sure it's synced and then switch to the receive tab.

look at your browser history and confirm the url you downloaded electrum from ?

You should complain in that issue: https://github.com/spesmilo/electrum/issues/4968


3.2.4 contains a backported version of the phishing attack mitigation for users who can't upgrade to python 3.6. Everyone else should stick to 3.3.2.