Two Android builds, sideloaded — the test one sits happily next to the real one — or the same wallet in a browser.
Real funds. You hold the only key that can spend them.
Download APK ↓The same wallet on a test network. Coins are worthless — try everything here first.
Download APK ↓No install at all. The same wallet in a tab — keys stay encrypted in that browser, not on the server.
Open signet.whispawallet.comOpen the web app →Check it before you install: both APKs are covered by a signed SHA256SUMS file. Three commands confirm the build is ours and reached you intact — how to verify a download →
Installing the APK: Android blocks apps from outside the Play Store — when you open the file, allow installs from your browser, then continue.
Using more than one: your account is the same everywhere, but your keys are not — they're generated on the device you're using and stay there, in the phone's keystore or encrypted in that browser. The server never holds anything that can spend, so a second device (or the browser, after the app) starts empty until you import your recovery phrase there.
Every release is signed. Three commands prove the file you have is the one we built.
WhiSPa Wallet <>
Confirm this fingerprint somewhere other than this page — on GitHub or X. Anyone who could serve you a fake APK from whispawallet.com could serve a fake key beside it, and the check would pass anyway.
Run this in the folder you downloaded the APK into. (Opening these links in a browser shows the text rather than saving a file — curl avoids that.)
You want Good signature, a fingerprint matching the one above, and OK. The WARNING is expected and does not mean the signature is bad — it only says you haven't told GPG you personally trust this key, which you don't need to do.
If either command fails, don't install the APK. Delete it, download again on a different network, and check once more. If it fails twice, tell us at before installing anything.
Separately, Android checks the APK's own signature on every update, so once WhiSPa is installed a build signed by a different key can't replace it. That makes the first install the one worth verifying.
WhiSPa