Feather Wallet review — the desktop reference for Monero

Feather is a free, open-source, Monero-only desktop wallet for Linux, macOS and Windows, with its own build for Tails and Whonix, where all its traffic goes over Tor.

Feather Wallet review — the desktop reference for Monero

Feather Wallet review

Feather is a free, open-source, Monero-only desktop wallet for Linux, macOS and Windows, with its own build for Tails and Whonix, where all its traffic goes over Tor.

Who is this for? Readers following the Monero guide who want a desktop wallet on Linux, macOS, or Windows, and who prefer a Monero-only tool over a multi-coin app like Cake Wallet.

Feather is free, open-source (BSD-3-Clause), and Monero-only — no other coins, no built-in swap, no exchange integration. It runs on Linux, Tails, macOS, and Windows, and has a dedicated Tails/Whonix build. Feather’s docs explain installing it on Tails, whose list of included software doesn’t name it, and Whonix’s own Monero page documents the official Monero GUI rather than Feather.

Monero’s planned FCMP++ upgrade, which would replace 16-member ring signatures with a full-chain anonymity set, is a protocol-level change that has not activated yet (Monero’s roadmap still lists it as future work and its blog index names no mainnet date, checked 4 November 2026) — keep Feather updated; we expect it to apply to your transactions once a Feather release for the fork ships (our reading: neither a date nor that release exists yet). The Monero guide explains what it would change.

Who builds Feather (checked 4 November 2026)

Feather “was created by dsc, tobtoht, and contributors”, and its development “is entirely funded through the Monero CCS and by donations” (Feather’s About page; the latest community-funding proposal listed there is from July 2023). Development continues in the repository, with contributions from other developers; after a gap of more than eighteen months since 2.8.1 (14 April 2025), 2.9.1 came out on 2 November 2026 (GitHub releases, featherwallet.org download page). Its signed source tag is dated 29 July 2026 and its release notes give Monero v0.18.5.1. Monero has since released 0.18.5.3 and 0.18.5.4, the former with wallet fixes that include cold signing, and Feather’s development branch moved to 0.18.5.4 on 17 October, which no Feather release has yet; Feather’s own patched copy of Monero in 2.9.1 was last changed on 29 July, so those later fixes aren’t in it (we read its source). For a wallet this widely recommended, it is a small, donation-funded project, so continuity depends on a few people (our inference).

What to check: look for a newer release on featherwallet.org before installing, and once Monero announces the FCMP++ hard-fork date, check that Feather has shipped an update for it in time.


Monero-only, on purpose

Feather does exactly one job: Monero. There’s no “create a Bitcoin wallet too” option, no swap tab, no fiat on-ramp. That’s a deliberate scope choice, not a missing feature — the project’s own framing is a small, fast, beginner-friendly wallet that still has “a feature set that is on par with the official CLI” for advanced users. If you want Monero plus a built-in way to swap from Bitcoin in the same app, that’s what Cake Wallet is for; if you specifically want a Monero-only wallet with nothing else installed alongside it, Feather is built around that constraint from the ground up.


Node connection: local, remote, or Tor

Feather gives you three ways to reach the Monero network, and the choice matters for privacy:

  • Local node — you run your own monerod and point Feather at it. On first start Feather detects a node on the default port (18081 on mainnet) by itself; later, go to File → Settings → Network → Node, uncheck “Let Feather manage this list”, click “Add custom node(s)” and enter 127.0.0.1:18081 (Feather’s local-node guide). This is the strongest privacy option (our assessment): no third party runs the node, so the remote-node risks below don’t apply. Feather does not route local-node traffic over Tor.
  • Remote node — you connect to someone else’s public Monero node. Convenient, because you don’t download the blockchain yourself, though the wallet still has to sync. According to Feather’s node page, a remote node doesn’t know your addresses or balance, can’t steal your funds, can’t detect your incoming transactions, and doesn’t know where you send money or how much. A malicious one can try an attack that may reveal the true input of a transaction (low chance, and Feather warns if it detects it), make your outgoing transactions stand out by manipulating the fee, and link your outgoing transactions to your IP address, but only if all traffic goes over clearnet; by default Feather broadcasts transactions over Tor.
  • Tor — Feather ships with its own bundled Tor binary and does not require a separate Tor install. If no Tor daemon is running on the default port (9050), it starts its own on port 19450 (Feather’s Tor page). 2.9.1 bundles Tor 0.4.9.11. Its release notes say the Tor daemon bundled with the previous release was deprecated: if an older Feather can’t reach a node, update, install Tor system-wide, open Tor Browser and set Feather’s Tor proxy port to 9150, or turn Tor off in Feather. The proxy setting also offers i2p and socks5.
Feather's network settings in dark theme on Monero's test network: a list of three onion nodes, each with status and block height

Caveat: the default Tor mode excludes wallet sync. Feather’s default setting routes “all network traffic over Tor, except for wallet synchronization”: node traffic is set to “Switch to Tor after initial synchronization”, so the first sync after you open a wallet goes to the node directly. The stated reason is that sync involves a lot of data and is very slow over Tor — the developers judge this an acceptable privacy/convenience tradeoff, since a remote node doesn’t learn much just from the sync process itself. Readers who want everything over Tor, including sync, choose “Change proxy settings” on first start, or later go to File → Settings → Network → Proxy and set “Node traffic” to “Always over Tor” — it will just be slower. One notable exception: on Tails or Whonix (or when started with torsocks), Feather uses the system’s Tor instead of its own, and all traffic goes through Tor regardless of this setting; only traffic to a local node stays outside Tor.


View-only wallets, offline signing and hardware wallets

Feather supports view-only wallets — a wallet loaded with only the view key, not the spend key, so it can display incoming transactions without being able to sign outgoing transactions. Once the wallet has sent funds, the balance it shows is only correct after you import the key images from the full wallet (Feather’s guide). You make one from an open wallet via Wallet → View-Only → “Create view-only wallet”. This is useful for auditing purposes (checking a wallet’s activity on a machine you don’t fully trust, or handing bookkeeping access to someone else) without exposing spending capability.

Multisig is not supported. Feather’s own feature comparison lists it as “not yet” (the Monero command-line wallet does support it). What Feather offers for a higher-security setup is offline (air-gapped) signing: a view-only wallet on an online computer builds the transaction, a full wallet on an offline computer signs it, and the two exchange data as animated QR codes over a webcam, or by file (Feather’s guide). It is the desktop counterpart of what Cupcake and Sidekick do with an old phone.

Feather also supports Ledger (Nano S, S Plus, X, Stax, Flex) and Trezor (Model T, Safe 3, Safe 5) hardware wallets for holding the private key on separate hardware rather than the same machine running the wallet software. The Trezor Safe 7 is not supported yet: it uses a new communication protocol that Monero’s code doesn’t implement (Feather’s hardware-wallet page, checked 22 October 2026).


The April 2024 denial-of-service incident

Worth naming directly: on 28 April 2024, a bug affecting every available Feather version made it impossible to send funds for about five hours (Feather’s incident report). The root cause was a years-old hardcoded sanity-check limit (100 million RingCT outputs) in a sanity check added in a 2021 patch; the Monero network’s real output count grew past that hardcoded limit on that date, tripping the check. Feather shipped an emergency fix within hours — its first emergency release ever, reserved specifically for bugs that risk fund loss or block core wallet functionality.

What this means for the review: the bug blocked sending, and Feather’s report describes no lost or exposed coins — but it’s a concrete example of what “no formal audit” can look like in practice: a plausible, if narrow, class of bug that a broader security review might have caught earlier (our reading). Feather’s public incident report and fast, transparent fix are themselves a reasonable trust signal, even though they don’t substitute for an audit.


Security practices without a formal audit

We found no published third-party security audit of Feather (checked 4 November 2026). What it does have:

  • A bug bounty until September 2026. Feather’s policy offered USD 100–1,500 (in XMR) for reproducible vulnerabilities that could cause fund loss. On 2 September 2026 the maintainer ended it, citing a high volume of AI-generated bug reports and a preference for spending the money on AI-assisted security review directly. Reports sent before that date still qualify (commit).
  • Signed releases: the downloads have a GPG signature (Flatpak has its own key check), plus a GPG-signed list of hashes per release; the signing key is in the project’s repository. We verified the 2.9.1 source archive and hash list against it on 4 November 2026.
  • Reproducible builds: documented Guix-based build instructions, so anyone can verify that the published binary matches the public source code.

This is a meaningfully more concrete security posture than “trust us” — but signed, reproducible releases are not the same thing as an independent audit combing through the codebase proactively. Both matter; neither replaces the other.


Comparison with Cake Wallet and Monerujo

Feather Wallet Cake Wallet Monerujo
Platform Linux, Tails, macOS, Windows Android, iOS, macOS, Linux Android
Coins Monero only Monero, Bitcoin, Litecoin, Ethereum etc. Monero only
Built-in swap No Yes Yes (via Exolix)
Old-phone signer companion No (offline signing between two computers instead) Cupcake (QR-code, air-gapped) Sidekick (Bluetooth-paired)
Local node support Yes Yes (own node per coin) Yes
Built-in Tor Yes, bundled binary Yes, built-in Tor (marked experimental), plus “Tor only” for swaps and price data No (works with Orbot)
View-only wallets Yes Yes (restore from keys without the spend key) Yes
Multisig No (listed as “not yet”) Not in its docs No
Hardware wallet support Ledger, Trezor Ledger, Trezor for Monero (BitBox, Coldcard for other coins) Ledger (Nano S series)
Open-source Yes (BSD-3-Clause) Yes (MIT) Yes (Apache-2.0)
Independent audit Not known (bug bounty ended September 2026) See the Cake Wallet review Not known
Latest release (checked 4 Nov 2026) 2.9.1, November 2026 6.5.2, October 2026 4.1.7, June 2025

Feather’s strengths are on the desktop side: built-in Tor, local-node support, offline signing between two computers, and both Ledger and Trezor, in a Monero-only design that keeps things simple. Neither Feather nor Monerujo offers multisig, and Cake’s docs don’t list it. But “minimal” doesn’t apply across the board to its mobile counterparts: Cake Wallet and Monerujo both bundle a built-in swap and their own old-phone signer companion (Cupcake and Sidekick respectively), and Monerujo also supports Ledger and view-only wallets — Feather is the one without a built-in swap or an old-phone companion option of the three.


Getting started

Download: featherwallet.org (also reachable via Tor onion address and I2P). Verify the GPG signature against the published signing key before running any binary — the project publishes signed hashes for every release.

Linux options (glibc 2.31 or newer): standalone executable, AppImage (x64, ARM64, RISC-V 64-bit; 2.9.1 dropped ARM32), Flatpak, or a dedicated Tails/Whonix AppImage.

Windows: installer (Windows 10+) or a standalone .zip. Since 2.9.1 the Windows release is no longer code-signed; Feather says this doesn’t affect release security, because code signing was never a replacement for checking the GPG signature, and its notes mention antivirus false positives it has stopped working around.

macOS: separate builds for Intel and Apple Silicon (macOS 14 or later since 2.9.1, previously 12).

Feather’s interface is in English only; the labels below are the ones it shows (checked against the 2.9.1 source).

First start: before it makes any network connection, Feather asks three questions (Feather’s first-start guide). On Tails and Whonix it skips them.

  1. “How do you want to connect to the Monero network?” Choose “Auto connect” (a random node from a list hosted by the developers and trusted community members), or “Select node manually” for your own or a chosen remote node. A local node on port 18081 is detected automatically.
  2. “How should Feather route its network traffic?” “Use default settings” keeps Tor with the initial-sync exception described above; “Change proxy settings” lets you pick “Always over Tor”.
  3. “Do you want to obtain third-party data?” “Enable” connects to a service hosted by the developers for prices, the node list, Home feeds and update checks. Feather says the wallet sends no information about its state or transactions to it and that it is not used for telemetry. “Disable” turns it off, at the cost of those features; you can switch it in File → Settings → Network → Websocket (“Enable websocket connection”). Feather’s 2.9.1 notes say this service is being phased out: features that depend on it will gradually go, while live price conversion stays.

Creating a wallet:

  1. Choose “Create new wallet”.
  2. Write down the 16 words (a Polyseed) and store them separate from the machine running Feather. To add a seed passphrase, click “Options” and check “Extend this seed with a passphrase”; you then need both the seed and the passphrase to restore, and the passphrase is not your wallet password.
  3. Give the wallet file a name and directory, then set a wallet password.
  4. Optionally set up a view-only wallet, or offline signing with a second computer, if your use case calls for it.

Restoring an existing wallet: in the wizard (or via File → New/Restore), choose “Restore wallet from…” → “Seed”, pick the seed type (“14 word mnemonic seed”, “16 word mnemonic seed (Polyseed)” or “25 word mnemonic seed”) and type the words; if the seed has a passphrase, click “Options” and check “Extend this seed with a passphrase” (Feather’s restore guide). Feather can recover a damaged Polyseed under specific conditions (see the project’s own recovery guide for exact steps).

Already have a setup? You don’t need to restart from scratch: the node choice and the Tor mode can be changed at any time in File → Settings → Network (tabs “Node” and “Proxy”), and an existing wallet’s 25-word seed can be shown via Wallet → Seed (enter your password, then check “Show 25 word seed”) if another wallet needs that format. On an older version that can’t reach a node, see the Tor note above.

Feather's History tab in dark theme: three test-network transactions with date, description column and amount Transaction details in Feather on the test network: transaction ID, status with block and confirmations, amount, fee and destination address

Screenshots: Feather 2.9.1 on the test network (stagenet), 4 November 2026.


Caveats

No independent third-party audit. Signed, reproducible builds are real, verifiable security practices, and so was the bug bounty that ran until September 2026, but none of them is a substitute for a dedicated audit combing the codebase for vulnerabilities before they’re found in the wild. The 2024 incident is a concrete (if narrow, fund-safe) example of the kind of bug a proactive audit might catch sooner.

Default Tor mode does not cover wallet sync. If your threat model requires every byte of network traffic to go over Tor, you need to change the default setting yourself — the out-of-the-box default is a deliberate speed/privacy tradeoff, not full Tor coverage.

Desktop-only. Feather has no mobile app. Readers who need Monero on a phone should look at Cake Wallet or Monerujo instead.

Long release gap until November 2026. Between 2.8.1 (14 April 2025) and 2.9.1 (2 November 2026) there was no release. Check for a newer one before installing, and for an update before Monero’s next hard fork.

No multisig. Feather lists it as “not yet”. For shared funds that need several approvals, Feather is not the tool today; for a single owner, offline signing on a second computer is the stronger setup it does offer.


Pros and cons

Pros

  • Free, open-source (BSD-3-Clause)
  • Monero-only — smaller attack surface than a multi-coin wallet (our reasoning), nothing else installed alongside it
  • Built-in Tor with no separate installation required
  • Local node support with no forced Tor routing when using it
  • View-only wallets, offline signing between two computers, and hardware wallet support (Ledger, Trezor)
  • Signed releases and reproducible builds
  • Public incident report and a fast emergency fix in 2024

Cons

  • No independent third-party security audit
  • Default Tor setting excludes wallet sync (configurable, but not the out-of-the-box behavior)
  • Desktop only — no mobile app
  • No multisig (listed as “not yet”)
  • Releases can be far apart (2.8.1 April 2025, 2.9.1 November 2026); a small, donation-funded team

Conclusion

Feather is the practical desktop reference for Monero: Monero-only by design, built-in Tor, real local-node support, and features (view-only wallets, offline signing, hardware wallet support) aimed at readers who want more control than a simple send/receive app. The lack of a formal audit is a real gap, and the bug bounty ended in September 2026; signed, reproducible builds remain a concrete trust signal. It is a small, donation-funded project whose releases can be far apart (latest: 2.9.1, November 2026), so check for updates around Monero’s next hard fork.

For most desktop readers coming from the Monero guide, Feather is the safe default. Readers who also want a built-in Bitcoin-to-Monero swap, or who need Monero on a phone, should look at Cake Wallet instead.

Next step

Coming from the Monero guide?

  • Monero guide — how Monero works, how to buy it, and where a desktop wallet fits in

Similar options

  • Cake Wallet — mobile-first, multi-coin, built-in swap
  • Monerujo — Android, Monero-only, Sidekick Bluetooth signer, offset passphrases

Want to go further?