Download Best Wallet
Download your #1 Monero wallet
Developers and APIs

How can you verify that a released binary corresponds to published source code?

Verifying that a binary executable matches the original source code is a fundamental security practice.

Quick Answer

Verify binary integrity by comparing the hash of the downloaded binary against known good hashes in signed release manifests. Users should also verify detached GPG signatures against the project’s signing key to confirm authenticity. For maximum trust, use the reproducible build process, which allows independent compilation of the source code to generate identical binary outputs, confirming the code was not tampered with.

Using Software Signatures

Monero releases are accompanied by detached GPG signatures. By verifying these signatures against the project’s signing key, users ensure that the release originates from trusted maintainers and has not been altered during distribution.

Building from Source

For maximum trust, users can compile the software themselves using the build instructions provided in the repository. Reproducible builds allow users to confirm that their locally compiled binaries are bit-for-bit identical to the official releases, confirming that the code hasn't been backdoored during the compilation stage.

Sources

Related reading

Key takeaways

  • Always verify GPG signatures for official binaries.
  • Building from source confirms the integrity of the executable.
  • Reproducible builds ensure consistent results.