How-to: Use Electrum Bitcoin Wallet in Kicksecure - Manual Installation
Manual installation from upstream (electrum.org) of Electrum AppImage.
See Electrum wiki page for introduction and warnings!
Note: The following instructions should be applied in Kicksecure (Kicksecure for Qubes:
1. Open a terminal.
If you are using Kicksecure ™ inside Qubes, complete the following steps.
Qubes App Launcher (blue/grey "Q") →
Kicksecure App Qube (commonly named kicksecure) →
If you are using a graphical Kicksecure with Xfce, run.
Start Menu →
2. Import the gpg public key of Electrum developer Thomas Voegtlin. 
- Digital signatures: A tool enhancing download security. Commonly used across the internet.
- Learn more: Curious? Learn more about digital software signatures.
- Optional: Digital signatures are optional. If you've never used them before, there might be no need to start now.
- No worries: New to digital software signatures? It's okay, no need to worry.
- Not a requirement: Not mandatory for using Kicksecure, but an extra security measure for advanced users.
Securely download the signing key.
Display the key's fingerprint.
gpg --keyid-format long --import --import-options show-only --with-fingerprint ThomasV.asc
Verify the fingerprint. It should show.
Note: Key fingerprints provided on the Kicksecure website are for convenience only. The Kicksecure project does not have the authorization or the resources to function as a certificate authority, and therefore cannot verify the identity or authenticity of key fingerprints. The ultimate responsibility for verifying the authenticity of the key fingerprint and correctness of the verification instructions rests with the user.
In early-2019, the output is identical to the following image.
Figure: Fingerprint Verification
Key fingerprint = 6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6
The most important check is confirming the key fingerprint exactly matches the output above. 
Add the signing key.
gpg --import ThomasV.asc
3. Download the Electrum AppImage.
Note: At the time of writing,
electrum-4.4.6 was the latest stable release. Before starting the Electrum download, browse to electrum.org/#download to verify the correct file path. Then download the file with scurl. 
5. Check the Electrum AppImage is not corrupted after download. 
To check the Electrum AppImage, run.
The following output indicates a corrupted and/or non-existent AppImage file.
electrum-4.4.6-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. 
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.4.6-x86_64.AppImage.ThomasV.asc electrum-4.4.6-x86_64.AppImage
If the file is verified successfully, the output will include
Good signature, which is the most important thing to check.
Figure: Good Signature 
gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner.
This message 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 Kicksecure signing key and the web of trust. To remove this warning, the Kicksecure 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
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 Kicksecure (Kicksecure for Qubes:
kicksecure) 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.4.6-x86_64.AppImage
The installation of the electrum AppImage has been completed.
To start Electrum on all platforms, run.
Kicksecure for Qubes users are recommended to configure a Split Bitcoin Wallet 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
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?".
Select server manually and press
Figure: Server Setting
Add Application Launcher to Start Menu
1. Create folder
mkdir -p ~/.local/share/applications
2. Create a new file
~/.local/share/applications/electrum.desktop using an editor.
3. Paste the following contents.
[Desktop Entry] Type=Application Exec=/home/user/electrum-4.4.6-x86_64.AppImage Name=electrum Categories=Other
4. Save the file.
The procedure is now complete.
6. Start using the launcher.
The launcher can be found here:
Start Menu →
After installing Electrum, please consider making a donation to Kicksecure to keep it running for years to come.
- Minor changes in the output such as new uids (email addresses) or newer expiration dates are inconsequential.
- To find the correct image download:
Copy Link Location→
to scurl command.
- Due to recent DDoS attacks.
- To find the correct signature file download:
Copy Link Location→
to scurl command
gpg: Signature made Mon 19 Jul 2021 02:22:33 PM EDT gpg: using RSA key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6 gpg: Good signature from "Thomas Voegtlin (https://electrum.org) <email@example.com>" [unknown] gpg: aka "ThomasV <firstname.lastname@example.org>" [unknown] gpg: aka "Thomas Voegtlin <email@example.com>" [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