How it works
Sparrow is a desktop application — installers for Windows, macOS (Intel and Apple Silicon) and Linux (Intel/AMD and ARM64), distributed at sparrowwallet.com and on GitHub. A separate Sparrow Server build runs headless on a home server. The wallet runs no service of its own: it is a Bitcoin client that signs and broadcasts transactions on the user's machine. Wallet files are encrypted on disk with Argon2-based key derivation.
The headline feature is Partial Signed Bitcoin Transactions. Sparrow speaks PSBT end-to-end, which is what makes it the de-facto coordinator for multisig and air-gapped setups: an unsigned transaction leaves the online machine on a QR code or microSD, gets signed on a hardware wallet or offline laptop, and comes back to be broadcast. Every common hardware signer is supported in both USB and air-gapped modes, alongside single-sig and arbitrary multisig templates.
For network connectivity, Sparrow ships three options: a public Electrum server (fast, but leaks your addresses), a self-hosted Electrs or Fulcrum pointed at your own Bitcoin Core, or Bitcoin Core directly over RPC. Tor is built in.
KYC & privacy
There is no signup. There is no account. No email is collected. You download a binary, verify it against Craig Raw's GPG signature, and that is the entire onboarding ceremony. The KYC tier we assign is L1 — anonymous, the most a piece of self-hosted software can earn on this rubric.
The privacy story is sharper once you reach the network layer. By default Sparrow talks to a public Electrum server and surfaces the trade-off in its own quick-start docs: public servers do not put your funds at risk, but they can see your addresses. That is the wallet's editorial stance — privacy is an outcome of how you connect and which UTXOs you pick, not a checkbox the software ticks for you. Coin labels, UTXO selection, BIP47 PayNyms and per-output fee control are all surfaced rather than hidden.
The one notable loss is the Whirlpool client, which Sparrow shipped for years and removed in v1.9.0 after the April 2024 United States indictment of the Samourai Wallet developers took the original coordinator offline. PayNym and BIP47 send/receive support remains.
Strengths and limits
Sparrow's strength is its honesty: it shows you what you are signing, where the transaction is going, which UTXOs it would spend and what change it would create, with a transaction editor that is unusually direct for a consumer wallet. Every release is signed with Craig Raw's PGP key (fingerprint D4D0D3202FC06849A257B38DE94618334C674B40) and ships with a SHA-256 manifest.
The limits are real. The project is effectively one maintainer, a bus-factor risk that no amount of code quality cancels. Releases are reproducible only in the weak sense: hashes match a published manifest, but the binaries are not deterministically rebuildable the way Bitcoin Core's are. There is no published third-party security audit. The wallet is Bitcoin-only with no native Lightning support, and the on-ramp assumes you already know what a PSBT and an Electrum server are.
Verdict
For a self-custodial bitcoiner willing to run their own node and treat privacy as an active practice, Sparrow is one of the most considered desktop wallets shipping. For a beginner who wants press-send-and-forget, it is not. The single-maintainer footprint and absence of a formal audit are the reasons we hold off the top grade.
Grade: A- (8.9/10). Trust: TRUSTED.
For a self-custodial bitcoiner who runs their own node and treats privacy as an active practice, Sparrow is one of the most considered desktop wallets on the market. A single-maintainer footprint and the absence of a third-party audit keep it short of the top grade. Grade: A- (8.9/10). Trust: TRUSTED.
