A user decides to run Monero on a Linux desktop and wants to verify the wallet binaries before installing them. The official source publishes checksums and cryptographic signatures alongside each release, but most users skip this step and download directly from a mirror or a third-party link. That choice is understandable—verification is tedious—but it is also where a compromised binary can enter the system undetected. If an attacker has modified the executable or replaced it during transit, a checksum and a GPG signature are the only defenses that prevent running malicious code with full wallet access.
This guide walks through the complete verification workflow: obtaining the correct public keys, importing them into GPG, downloading the binaries and their signatures, verifying the cryptographic chain, and confirming that the checksums match. The process is mechanical and can feel paranoid, but it is the standard practice for users who cannot afford to trust a single distribution channel or a precompiled binary from an unknown source. For anyone managing meaningful Monero holdings, verification is not optional.

Why checksum and GPG verification matters for Monero wallet download security
A checksum is a hash value computed from a file’s contents. If even one byte changes, the checksum changes completely. GPG verification uses a digital signature—a cryptographic proof that the file was signed by someone who controls a specific private key. Together, they answer two questions: Has the file been corrupted or modified? Was it signed by the Monero development team?
Without verification, a user cannot distinguish between a legitimate binary and one that has been replaced by malware, altered in transit, or served from a compromised mirror. Checksum matching confirms integrity. GPG verification confirms authenticity. A compromised binary that runs silently and steals private keys or seed phrases is the worst-case scenario for a cryptocurrency wallet. No amount of strong passwords or good operational security can recover from running infected code.
The attack surface is real. Between 2018 and 2024, several download mirrors and third-party repositories experienced compromises or served malicious versions of cryptocurrency software. A user who skips verification assumes that every link they click and every file they download is exactly what it appears to be. That assumption is reasonable for some software; for cryptocurrency wallets, it is a gamble with personal financial security.
The Monero project publishes release signatures on its official channels and maintains documented verification procedures. The official Monero documentation includes the team’s public keys and detailed instructions for GPG verification. Following those procedures is the difference between a paranoid process and a risky one.
Obtaining the Monero development team’s GPG public keys
The first step is to obtain the legitimate GPG public keys of the Monero developers who sign releases. These keys are published on the official Monero website, on public key servers, and in the project’s GitHub repository. The key fingerprints are also listed in multiple places so that users can cross-reference them.
Start by visiting the official Monero website and navigating to the download or security documentation section. Write down or copy the key fingerprints listed there. A fingerprint looks like this: 81AC591FE2A748A0 (shortened) or a full 40-character hex string. Compare the fingerprints from at least two sources—the official website and the GitHub repository, for example. If they match, you have confidence that you are working with the correct keys.
Next, import the public keys into your local GPG keyring. Open a terminal and run gpg --keyserver hkps://keys.openpgp.org --recv-keys KEYID, replacing KEYID with the full fingerprint. GPG will download the key from the public key server and store it locally. Repeat this for each developer key listed in the official documentation. After import, verify the fingerprint by running gpg --list-keys KEYID and confirming that it matches the published fingerprint exactly.
If a key fingerprint does not match what you copied from the official source, stop. Do not import the key. An attacker who has compromised the key server or your network connection could serve a malicious key. In that case, try a different key server or download the key file directly from the GitHub repository and import it using gpg --import keyfile.asc.
Downloading the binary, signature, and checksum files
With the public keys imported, download the Monero wallet binaries from the official source. The release page typically contains several files: the executable or compressed archive, a file containing checksums (usually named something like hashes.txt or SHA256SUMS), and a signature file for the checksums (named SHA256SUMS.asc or similar). Download all three files to the same directory on your system.
For a typical Linux user, the binary file might be named monero-gui-linux-x64-v0.18.3.2.tar.bz2 or similar. The checksum file contains lines like a1b2c3d4... monero-gui-linux-x64-v0.18.3.2.tar.bz2, mapping each file to its expected hash. The signature file contains the cryptographic signature that proves the checksum file was signed by a Monero developer.
Do not download from random mirrors or third-party hosting services unless they are explicitly listed as official mirrors on the Monero website. Every additional hosting point is an additional attack surface. If you are downloading a large file and the connection is slow, it is better to download from a slower official source than a faster unofficial one.
Verifying the signature on the checksum file
The signature file is the key to the entire verification chain. If the signature is valid, it proves that the checksum file has not been tampered with and was created by someone who controls the developer’s private key. In the terminal, navigate to the directory containing the downloaded files and run gpg --verify SHA256SUMS.asc SHA256SUMS. (Adjust the filenames to match what you downloaded.)
GPG will output something like this: gpg: Good signature from "Monero Core Team <team@monero.cc>" followed by additional information about the key and signature date. If you see “Good signature,” the checksum file is authentic. If you see “Bad signature” or any warning about the key being untrusted, stop immediately. Do not proceed with the verification or installation.
A “Bad signature” means either the file has been modified, the signature is corrupted, or the wrong public key was used. Do not assume the issue is a minor error. Delete the downloaded files, clear your browser cache, and download again from the official source. If the second attempt also produces a bad signature, check that you imported the correct key and that your system clock is not wildly off (GPG checks signature timestamps).
If you see a warning that the key is “untrusted,” that is expected if you have not explicitly marked the key as trusted in your GPG configuration. The key is still valid and the signature is still good; you have simply not told GPG that you trust this particular key to sign software. For a single verification, this warning is not a blocker. For frequent use, you can mark the key as trusted by running gpg --edit-key KEYID, typing trust, selecting 4 (I trust this key fully), and exiting.
Verifying checksums and comparing against the binary
After the signature is verified, check the checksum of the binary you downloaded. In the same directory, run sha256sum monero-gui-linux-x64-v0.18.3.2.tar.bz2 (substitute the actual filename). This will output a long hex string. Compare it to the corresponding line in the SHA256SUMS file.
If the checksums match exactly, the file is intact. If they do not match, the file has been corrupted or modified. Do not install it. Delete it and download again. If the second download produces the same mismatched checksum, the problem may be on your system (a disk error, for example) rather than the source. Try downloading to a different location or using a different browser.
Alternatively, you can run sha256sum -c SHA256SUMS in the directory containing all downloaded files. This command will check every file listed in the checksum file against its corresponding downloaded file. Each successful match will print filename: OK. Any mismatch will print filename: FAILED. If you see any failures, investigate before proceeding.
At this point, you have confirmed that the binary you downloaded matches the checksum that was signed by a Monero developer. The chain of custody is intact: the signature is valid, the checksum file matches that signature, and the binary matches that checksum. You can now extract and install the wallet with confidence that it has not been modified or replaced.
Extracting, installing, and running the verified binary
Extract the compressed archive using tar -xjf monero-gui-linux-x64-v0.18.3.2.tar.bz2 or your preferred extraction tool. This will create a directory containing the executable and supporting files. The Monero CLI wallet and GUI are often provided in the same archive; choose which one you want to run.
Before running the wallet, set appropriate file permissions. Run chmod 700 monero-gui to make the executable readable and runnable only by the owner. This reduces the risk that another user on the system could modify or replace it. If you are the only user on the system, this is less critical, but it is still a good practice.
When you run the wallet for the first time, it will typically prompt you to create a new wallet or restore an existing one. If you are creating a new wallet, make sure the recovery seed is written down on paper and stored securely offline. Never copy it to a text editor, email account, cloud service, or any internet-connected device. The recovery seed is the master key to your wallet; anyone who obtains it can steal all your Monero.
For additional information on Monero wallet options and download locations, users can consult comprehensive resources that compare different implementations across mobile, desktop, and hardware platforms. A monero wallet download guide should always include verification instructions and warnings about third-party sources, as this reduces the risk of users installing compromised binaries or using phishing links.
Common verification pitfalls and how to avoid them
One frequent mistake is downloading the binary from a different source than the signature file. If you download the binary from one mirror and the signature from another, you have not verified anything meaningful; an attacker who controls one mirror could have altered the binary and left the signature unchanged. Always download the binary, signature, and checksums from the same official source.
Another pitfall is trusting a checksum without verifying the signature on the checksum file. A checksum alone confirms that a file is internally consistent, but it does not confirm that it came from the Monero team. An attacker who replaces both the binary and the checksum file has defeated a checksum-only verification. The GPG signature is what proves the checksum file is legitimate.
Users sometimes also skip verification because they believe that downloading from a well-known third-party site (a popular Linux distribution repository, for example) is safe. In many cases, those repositories do verify upstream signatures themselves before distributing software. However, the responsibility for verification rests with you, not the intermediary. If the repository is compromised, malicious software could be served without your knowledge. For a cryptocurrency wallet holding real funds, verification is the only guarantee.
Clock skew on your system can also cause signature verification to fail. If your system time is significantly off, GPG may reject signatures as being timestamped in the future or in the distant past. Check your system time by running date and comparing it to a reliable source (for example, timedatectl status on systemd systems). If the time is wrong, correct it before attempting verification.
Monero network security: why verification matters in a privacy context
Monero’s privacy model depends on strong cryptography: ring signatures to obscure transaction inputs, stealth addresses to hide receiving addresses, and a full blockchain that every participant downloads and validates. That security is only as strong as the wallet software that implements it. If a user installs a modified wallet, those privacy protections become meaningless; the altered code can log keys, redirect funds, or expose transaction details that the legitimate wallet would keep private.
The Monero protocol itself is resistant to many attacks because it is peer-to-peer and decentralized. No single authority controls the network, and transactions are verified by many independent nodes. However, that advantage is lost if the user’s wallet is compromised. A malicious wallet can steal the recovery seed, watch all transactions, or silently divert outgoing funds to an attacker’s address.
Verification is therefore not a paranoid extra step; it is part of the security model. For Monero to deliver the privacy and security it promises, users must run legitimate, unmodified code. Checksum and GPG verification is the practical way to ensure that happens.
Frequently asked questions
What do I do if the GPG signature verification fails?
Stop immediately. Do not install or run the binary. A failed signature means the file has been modified, the signature is corrupted, or you imported the wrong key. Delete the downloaded files, double-check the key fingerprint against the official source, import the correct key, and download again. If the problem persists, contact the Monero team or check their official support channels before proceeding.
Can I skip GPG verification and just check the checksum?
No. A checksum alone confirms that a file matches itself, but it does not prove that the file is legitimate or came from the Monero team. An attacker can replace both the binary and the checksum. The GPG signature on the checksum file is what proves the checksum came from a Monero developer. Always verify both the signature and the checksum.
Is it safe to download Monero wallet from third-party mirrors or distribution repositories?
Official mirrors listed on the Monero website are generally safe because the Monero team vets them. However, any third-party source is an additional attack surface. The only way to be certain is to perform GPG verification yourself. Linux distribution repositories may verify signatures upstream, but you should not rely on that; download the official binary and verify it directly. A monero wallet download from an untrusted source is a security risk, even if it appears to work correctly.
