Verifying a wallet download.
The fastest path from "I have a GPU or ASIC" to "shares are landing" on the testnet demo. Five steps.
01 Why verify at all
You install the getcryptocoin wallet by downloading an APK directly from this site, not from an app store. That is deliberate — it keeps the wallet self-custodial and free of store gatekeeping — but it puts one job on you that a store would otherwise do: confirming that the file you installed is exactly the file I published, byte for byte.
Verifying takes about a minute. You compute a SHA-256 hash of the file you downloaded and check it against the value I publish. If they match, the file is intact and unmodified. If they do not, delete it and download again — do not install it.
02 Get the APK and the checksum list
Two downloads, both from this site:
- The wallet APK from the wallets page.
- The published checksum list at
/downloads/checksums.txt.
The checksum file is plain text. Each line is a SHA-256 hash followed by the filename it belongs to, like this:
Make sure the filename on the line matches the APK you actually downloaded — the hash is only meaningful for that exact file.
03 Compute the hash and compare
Run one of the following on the machine where the file is, from the folder you downloaded it into. The command prints a 64-character hex string; compare it, character for character, with the value on the matching line of checksums.txt.
Linux:
macOS:
Windows (PowerShell or Command Prompt):
The hashes are case-insensitive, so do not worry if one tool prints uppercase and another lowercase — only the characters matter. If they match, the file is genuine and you can install it. If even one character differs, the file is not what I published: delete it and download it again over a clean connection.
04 The signing fingerprint
The release build is also signed with a keystore I control, and the certificate’s fingerprint is published on the wallets page. The checksum proves the file is the one I uploaded; the signing fingerprint ties that file to my signing key, and Android itself checks the signature when it installs and again on every update, refusing any update not signed by the same key.
Together they give you two independent things to lean on: the checksum for integrity of the exact download, and the signature for provenance. For a self-distributed wallet that is the verification a store would otherwise have done on your behalf.