Wallets
What exists today, honestly
No signed installer or app-store listing has been released yet — this page will start linking to those the moment they exist, and not before. One thing is available now: a debug build of the Android app, for testnet testing only. See the mobile card below for exactly what that is and isn't.
Full node (firstislamiccoind)
The reference implementation, including a graphical (Qt) wallet, builds from source today on Linux, macOS and Windows.
No signed installers or GitHub release binaries yet — build it yourself from the public source once the repository is published (see the roadmap).
Web wallet
A no-install browser wallet talking to the same gateway the mobile app uses, forked from and rebuilt against the same web-wallet approach used by the project FIC was built from.
Deployed at wallet.firstislamiccoin.com, against testnet.
Mobile (Android / iOS)
A single Flutter codebase for both platforms. iOS needs a paid Apple Developer account to build at all, so only Android has a build to offer right now.
Download the Android debug build
(174 MB, SHA256
a80f6c9f76c2f1f72678c2b64ac9ac73a1dbd0ff36be214f70d39c7934fb6055,
also in the .sha256 file).
This is not a release: it's an unsigned debug build (Android's own debug
keystore, not a real signing key), built from a specific source commit
(902d974) for testnet use only. It has not been through any app-store
review, has not been tested on a physical device or emulator, and is not audited. Two
real crypto bugs in this codebase were found and fixed shortly before this build (see
the roadmap) — treat this as a testnet preview for people who
want to look, not as something to hold real value in. Android will warn about installing
from an unknown source; that warning is expected for a debug build like this one, not a
sign anything is wrong with the file itself (verify the checksum above to confirm that).
Packaged desktop installers
Signed .dmg, .exe, and Linux packages, built and tested through CI.
Not yet published.
Verifying a download, once releases exist
When binaries are published, they'll ship with SHA256 checksums and a detached GPG signature over those checksums — the same scheme Bitcoin Core itself uses — so anyone can verify a downloaded file is exactly what the project published, independent of whether the OS itself shows an "unidentified developer" warning (which depends on paid code-signing, a separate thing entirely). This page will publish the real signing key fingerprint here once one exists — not before.