FFSWallet

Download

v0.0.10, published 2026-09-10. Four builds and a checksum list. Each file shows its SHA-256 here; the Linux builds and SHA256SUMS carry a Sigstore signature.

1. Linux x86-64AppImage
   FFSWallet-linux-amd64.AppImage
   14.2 MBsigned
   sha256a785e97fa5482135c05743352b58ffaaaaf7dec47ec057929acb677ac28ad2cf
2. Linux x86-64tarball
   FFSWallet-linux-amd64.tar.xz
   11.2 MBsigned
   sha256f9961289410f6bce04f5413e67d1fd91b92049f755d37df89e3c3ac9b7c004e2
3. macOSApple silicon
   FFSWallet-macos-arm64.zip
   13.5 MB
   sha256a55eddfbd4a89768dd3748386da66139ef077278dfe68c6c7ee311a12e3caeec
4. Windows x86-64
   FFSWallet-windows-amd64.exe
   29.6 MB
   sha256bfc6ca584dd9d4f47b27d161db0cf7cee008cd1a6dccd0a6662aad74845df52d
5. Checksumsevery file above
   SHA256SUMS
   378 Bsigned
   sha256e7c2bc5796f186fe965efabef86e4ab6206f6c24d81e6fddee27000f4b80b357

Running it

Linux

Mark the AppImage executable and run it. Or unpack the tarball and run usr/local/bin/ffswallet.

macOS

Unzip and drag FFSWallet into Applications. The app is not notarised, so the first launch is right-click, then Open.

Windows

Run the executable. There is no installer.

The wallet opens on testnet. Mainnet is a choice you make when you create a wallet.

Verify

The release workflow signs the Linux builds and the checksum list with Sigstore, keylessly. There is no public key to fetch: the certificate names the GitHub workflow that produced the file, and cosign checks it against the transparency log. Before you run a download, check it against its .sig and .pem:

cosign verify-blob FFSWallet-linux-amd64.AppImage \
  --signature   FFSWallet-linux-amd64.AppImage.sig \
  --certificate FFSWallet-linux-amd64.AppImage.pem \
  --certificate-identity-regexp '^https://github.com/brad1121/FFSWallet/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

Then sha256sum -c SHA256SUMS in the download directory covers the macOS and Windows files too. SHA256SUMS is itself signed, so the check reaches every file.

How it syncs

FFSWallet is a light node. It connects to the Bitcoin SV peer-to-peer network directly, follows block headers, and listens to the mempool for payments to its own addresses. It does not download the chain and it does not trust an indexer.

It only hears what is relayed while it is open. A payment mined while the wallet was closed is not in the balance until that block is replayed. So the wallet remembers the last block it scanned and, on unlock, catches up from there in the background: it pulls each block from peers and replays it. Blocks on this chain run to gigabytes; they stream through one transaction at a time.

Height: 1757291 · scanned to 1719168 (38123 behind)

That is the status bar. The height on the left is the peers' best; the height in blue is how far the wallet has replayed. When the two agree, the balance is right.

Keys

BIP39 seed words, BIP44 derivation. One wallet file, encrypted with Argon2id and AES-GCM.

State

UTXOs and transaction history in a SQLite store beside the wallet file.

Network

Peer-to-peer only. No API keys, no accounts, no telemetry.

Stack

Go, Fyne for the UI, a private BSV SDK for the protocol.

Older releases

Every release stays mirrored here in full. Run the current one; these are for reference.