How-to: Use Electrum Bitcoin Wallet in Whonix ™ - Manual Installation

From Whonix

< Electrum


See Electrum for introduction and warnings!

Primarily refer to Electrum! Use this page only in case newer versions of Electrum are desired!

Community Support Only!:

Community Support Only means Whonix ™ developers are unlikely to provide free support for wiki chapters or pages with this tag. See Community Support for further information, including implications and possible alternatives.

Install Electrum[edit]

Installation Steps[edit]

Note: The following instructions should be applied in Whonix-Workstation ™ (Qubes-Whonix ™: anon-whonix).

1. Open a terminal.

If you are using Qubes-Whonix ™, complete the following steps.

Qubes App Launcher (blue/grey "Q")Whonix-Workstation ™ AppVM (commonly named anon-whonix)Xfce Terminal

If you are using a graphical Whonix with XFCE, run.

Start MenuXfce Terminal

2. Import the gpg public key of Electrum developer Thomas Voegtlin. [1]

Securely download the key.


Display the key's fingerprint.

gpg --keyid-format long --import --import-options show-only --with-fingerprint ThomasV.asc

Verify the fingerprint. Should show.

In early-2019, the output is identical to the following image.

Figure: Fingerprint Verification

Electrum verify gpg fingerprint.png

pub rsa4096/2BD5824B7F9470E6 2011-06-15 [SC] Key fingerprint = 6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6 uid Thomas Voegtlin ( [archive]) <> uid ThomasV <> uid Thomas Voegtlin <>

sub rsa4096/1A25C4602021CD84 2011-06-15 [E]

The most important check is confirming the key fingerprint exactly matches the output below. [2]

warning Warning:

Do not continue if the fingerprint does not match! This risks using infected or erroneous files! The whole point of verification is to confirm file integrity.

Add the signing key.

gpg --import ThomasV.asc

3. Download the Electrum AppImage.

Note: At the time of writing, electrum-4.1.5 was the latest stable release. Before starting the Electrum download, browse to [archive] to verify the correct file path. Then download the file with scurl. [3]


5. Check the Electrum AppImage is not corrupted after download. [4]

To check the Electrum AppImage, run.

file electrum-3.*x86_64.AppImage

The following output indicates a corrupted and/or non-existent AppImage file.

electrum-4.1.5-x86_64.AppImage: HTML document, ASCII text, with very long lines

In that case, delete the file and try downloading the AppImage again.

6. Download the corresponding gpg signature.

It is necessary to verify the integrity of the AppImage with the correct signature.

Note: If users downloaded a later Electrum version at step 4, then modify the following command to match the corresponding signature file. [5]


7. Verify the integrity of the AppImage image.

Note: This command must be run in the same directory as the downloaded AppImage and signature.

gpg --verify electrum-4.1.5-x86_64.AppImage.asc

If the image is verified successfully, the output will show a "Good signature" similar to the screenshot below.

Figure: Good Signature [6]

Electrum gpg good signature.png

The above "gpg: WARNING" can be ignored since it does not alter the validity of the signature related to the downloaded key. Rather, this warning refers to the level of trust placed in the developers signing key and the web of trust. To remove this warning, the developers signing key must be personally signed with your own key.

If the following "gpg: BAD signature" message appears, the Appimage has been corrupted or altered during the download process.

Figure: Bad Signature

Electrum bad gpg signature.png

In this event, delete both the AppImage and signature and either wait 10-15 minutes for the Tor circuits to change, or open up the Nyx Tor Controller in Whonix-Gateway ™ (Qubes-Whonix ™: sys-whonix) and type "n" to create new Tor circuits. Wait for a random period of time before repeating the steps to download the AppImage and signature.

8. Change file permissions.

Make the electrum AppImage executable.

chmod +x electrum-4.1.5-x86_64.AppImage

Start Electrum[edit]

Info Users should create a wallet with a strong password!

Please refer to the official Documentation at [archive] for comprehensive instructions, as well as more advanced topics like Cold Storage [archive] of private keys.

To start Electrum on all platforms, run.


Qubes-Whonix ™ users are recommended to configure a Split Bitcoin Wallet [archive] to better protect their private keys. To protect against identity correlation through Tor circuit sharing, follow the instructions below (see Stream Isolation for more information).

Electrum: First Run[edit]

Info These steps enable Stream Isolation for the Electrum application.

1. Configure a manual server connection.

When Electrum is started for the first time, users are met with the prompt: "How do you want to connect to a server?".

Choose Select server manually and press Next.

Figure: Server Setting

Electrum select server manually.png

2. Change the proxy settings.

The necessary settings are:

  • Proxy: SOCKS5
  • Host:
  • Port: 9111

Press Next and the application should be fully functional.

Figure: SOCKS5 Proxy Configuration

Electrum use proxy socks5 .png

Note: If Electrum is already set up but stream isolation was not enabled, then navigate to ToolsNetwork in Electrum to bring up the server and proxy settings.

Add Application Launcher to Start Menu[edit]

Info This step is optional.

1. Create folder ~/.local/share/applications.

mkdir -p ~/.local/share/applications

2. Create a new file ~/.local/share/applications/electrum.desktop using an editor.

mousepad ~/.local/share/applications/electrum.desktop

3. Paste the following contents.

[Desktop Entry]

4. Save the file.

The procedure is now complete.

The launcher can be found here:

Start MenuOtherelectrum


After installing Electrum, please consider making a donation to Whonix ™ to keep it running for years to come.

Donate Bitcoin (BTC) to Whonix ™.

Bitcoin accepted here 35wdTVzyYGzRd7W2Wb2dunw3v5Am14sxPX

Whonix donate bitcoin.png


  1. [archive]
  2. Minor changes in the output such as new uids (email addresses) or newer expiration dates are inconsequential.
  3. To find the correct image download: "Right-click" AppImage"Select" Copy Link LocationAppend to scurl command.
  4. Due to recent DDoS attacks.
  5. To find the correct signature file download: "Right-click" signature"Select" Copy Link Location"Append" to scurl command
  6. gpg: assuming signed data in 'electrum-4.1.5-x86_64.AppImage'
    gpg: Signature made Thu 16 May 2019 02:14:30 PM EDT
    gpg:                using RSA key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6
    gpg: Good signature from "Thomas Voegtlin ( <>" [unknown]
    gpg:                 aka "ThomasV <>" [unknown]
    gpg:                 aka "Thomas Voegtlin <>" [unknown]
    gpg: WARNING: This key is not certified with a trusted signature!
    gpg:          There is no indication that the signature belongs to the owner.
    Primary key fingerprint: 6694 D8DE 7BE8 EE56 31BE  D950 2BD5 824B 7F94 70E6

Fosshost is sponsors Kicksecure ™ stage server Whonix old logo.png
Fosshost About Advertisements

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier | Whonix ™ Wiki

Follow: 1024px-Telegram 2019 Logo.svg.png Iconfinder Apple Mail 2697658.png Twitter.png Facebook.png Rss.png Reddit.jpg 200px-Mastodon Logotype (Simple).svg.png

Support: 1024px-Telegram 2019 Logo.svg.png Discourse logo.png Matrix logo.svg.png

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate Whonix.png United Federation of Planets 1000px.png

Twitter-share-button.png Facebook-share-button.png Telegram-share.png link=mailto:?subject=Electrum/Manual Installation&body= link= Installation link= Installation link= Installation%20 Installation

Please contribute by helping to answer Whonix ™ questions.

https link onion link Priority Support | Investors | Professional Support

Whonix | © ENCRYPTED SUPPORT LP | Heckert gnu.big.png Freedom Software / Osi standard logo 0.png Open Source (Why?)

The personal opinions of moderators or contributors to the Whonix ™ project do not represent the project as a whole.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent.