Table of Contents
Gem Wallet adds reproducible builds, effective July 16, 2026. Gem Wallet’s code has always been open to read - now you can also build the app yourself and see that the release in the store was compiled from exactly that code, byte for byte. Transparency you can check not only in the repository, but right in the app on your phone.
What Are Reproducible Builds?
Reproducible builds are a way to confirm that the app in the store was built from exactly the published source code. Anyone takes Gem Wallet’s open-source code, builds the app themselves, and gets a file that matches the official release byte for byte.
You can read Gem Wallet’s source on GitHub, but the app itself you download from the App Store or Google Play - already compiled. During the build step, something extra could in theory slip into any product - through a hacked CI, for example - while the code in the repository stays clean. A reproducible build closes that gap: if the file rebuilt from source matches the release byte for byte, the app contains exactly the published code - and anyone can confirm it.
Why Reproducible Builds Matter for a Crypto Wallet
In a self-custody wallet - where only you hold the private keys - trust is built as a chain of three links:
- Open Source: The foundation of any open-source wallet - Gem Wallet’s code is 100% open, and anyone can read and review it.
- Reproducible Builds: Turn that openness from a promise into a verifiable property - the app from the store can be checked against the code byte for byte.
- Independent Audit: Closes the chain - Gem Wallet’s code passed a CertiK audit in April 2026, with more independent audits planned.
The point is simple: if a build can be reproduced, any tampering shows up immediately, and attacking it becomes far harder. That is why reputation services like WalletScrutiny lower their rating for wallets without reproducible builds - even open-source ones. Few people rebuild releases, but thousands trust their findings - so reproducibility works as a public pledge of honesty, not a feature for everyone. It also has a clear limit: it proves the app was built from the declared code, but not that the code itself is flawless - that is what audits and reviews are for.
How It Works in Gem Wallet
Gem Wallet keeps the entire build recipe in the open: the exact commit, tool versions, and scripts are all public. The rebuild is performed by the independent F-Droid infrastructure, which builds the Android release outside Gem Wallet’s servers and ships it only on a byte-for-byte match. Current coverage:
- Android (F-Droid): The reproducible build is already available and verified on every release.
- iOS (App Store): Not reproducible yet - Apple re-signs and modifies the binary at publication; independent verification is planned.
- Universal APK and Google Play: Reproducible-build support is planned.
The full verification model and current coverage are described on the Reproducible Builds page, and reproducibility itself is part of Gem Wallet’s approach to security.
Resources for Developers
The source code, reproducible build scripts, and metadata with the exact commit and expected APK are published in the Gem Wallet repository.
Conclusion
Open source shows how Gem Wallet is built. Reproducible builds let you confirm that exactly this code is in the app on your phone - and anyone can check it, independently.
Install Gem Wallet - a secure, fully open-source and transparent wallet whose build anyone can verify themselves.
