|Python (3.8 and higher)||Electrum-4.3.0.tar.gz||Signatures|
|Windows (8.1 and higher)||Standalone Executable||Signatures|
|Portable version (security advice)||Signatures|
|macOS (10.13 and higher)||Executable for macOS||Signatures|
(5.0 and higher)
(available on Google Play)
|Run without installing:||
|Install with PIP:||
GPG signatures are a proof that distributed files have been signed by the owner of the signing key. For example, if this website was compromised and the original Electrum files had been replaced, signature verification would fail, because the attacker would not be able to create valid signatures. (Note that an attacker would be able to create valid hashes, this is why we do not publish hashes of our binaries here, it does not bring any security).
In order to be able to verify GPG signatures, you need to import
the public key of the signer. Electrum binaries are signed with
key. On Linux, you can import that key using the following
gpg --import ThomasV.asc. Here are tutorials for
When you import a key, you should check its fingerprint using
independent sources, such
the Web of
Electrum binaries are often flagged by various anti-virus software. There is nothing we can do about it, so please stop reporting that to us. Anti-virus software uses heuristics in order to determine if a program is malware, and that often results in false positives. If you trust the developers of the project, you can verify the GPG signature of Electrum binaries, and safely ignore any anti-virus warnings. If you do not trust the developers of the project, you should build the binaries yourself, or run the software from source. Finally, if you are really concerned about malware, you should not use an operating system that relies on anti-virus software.
Old versions of Windows might need to install the KB2999226 Windows update.