#Electrum 2.7.9 wont sync update#

You need to make sure, you gave a proper JSON file, so all the final commas must be dropped. You need to locate the wallet file and remove all the transactions from the wallet file except for the one that funds the address you want to claim (the wallet obviously must not be encrypted but for watch-only this is OK).

You can manually create a transaction from the command line but you can use Electrum GUI.

#Electrum 2.7.9 wont sync update#

It's required so Electrum will not update the wallet after you edit it. Now go offline or set localhost as your server that Electrum connects to so no connection is performed. Run the patched Electrum and catch up with your wallets you want to claim (the wallets can and rather should be watch only, or on ledgetrezor, otherwise your keys are exposed).The guide assumes that you use patched Electrum from now on. Apply my patch patch -P0 also this article.Similarly, any BIP39 seeds or a single key. This procedure should work with everything that Electrum supports (except maybe F2A that may be not supported on the SBTC chain), so Electrum seed legacy or segwit, LedgeTrezor with legacy or segiwt-p2sh (m/'49) derivation. All can be stolen if you exposed your key. Even if the keys do not have any bitcoins, you can some day have bitcoins sent to these addresses or you have a fork that you have not claimed.

Why such a guide? I followed these steps because I did not want to expose the keys to any online machine at all. Although the procedure in this guide is safe even for hot addresses (containing bitcoins), there is always a risk of a critical mistake. Move you bitcoins to safe addresses first.

And that you can compile and run Bitcoin Core and run Electrum. This guide assumes you have some basic experience with the command line, can run Linux and you understand the basics of keys/signing/broadcasting transactions.