If the fingerprint **DOES NOT** match, **DO NOT CONTINUE.** Instead delete the file `binaryfate.asc` and go back to [section 2.1](#21-get-signing-key).
``` gpg:using RSA key 81AC591FE9C4B65C5806AFC3F0AF4D462A0BDF92 gpg: Good signature from "binaryFate <[email protected]>" [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: 81AC 591F E9C4 B65C 5806AFC3 F0AF 4D46 2A0B DF92 ```
gpg:using RSA key 81AC591FE9C4B65C5806AFC3F0AF4D462A0BDF92 gpg: Good signature from "binaryFate <[email protected]>" [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: 81AC 591F E9C4 B65C 5806AFC3 F0AF 4D46 2A0B DF92
To protect the integrity of the binaries the Monero team provides a cryptographically signed list of all the [SHA256](https://en.wikipedia.org/wiki/SHA-2) hashes. If your downloaded binary has been tampered with it will be produce a [different hash](https://en.wikipedia.org/wiki/File_verification) than the one in the file.
This section will cover downloading the Monero binary for your operating system, getting the `SHA256` hash of your download, and verifying that it is correct.
From a terminal, get the `SHA256` hash of your downloaded Monero binary. As an example this guide will use the `Windows, 64bit` GUI binary. Substitute `monero-gui-win-x64-v0.15.0.1.zip` with the name of the binary that you downloaded in [section 4.1](#41-get-monero-binary).
