Is Feather Wallet safe to connect?
Privacy wallet ยท Monero. Checked 2026-10-24; every line links its source.
Worst case: Feather keeps your keys on your computer, so malware on that machine, a fake installer, or a leaked Polyseed can empty the wallet. The last release was 2025-04-14, so a future Monero upgrade may need a new version before you can send.
Safe setup in 3 steps
- Download only from featherwallet.org (or its onion mirror) or github.com/feather-wallet/feather releases, never from search ads or links in chat.
- Verify the download: check its .asc signature or the signed hashes file against the release key fingerprint 8185 E158 A333 30C7 FD61 BC0D 1F76 E155 CEFB A71C.
- Write the 16-word Polyseed on paper offline, and run Feather on a clean, up-to-date machine (Tails is supported) with a strong wallet password.
What it can do with your money
| Who holds the keys | You hold the keys Desktop self-custody wallet. New wallets use a 16-word Polyseed with the restore date built in. Legacy 14- and 25-word Monero seeds can be restored. source |
|---|---|
| Can funds be sent out to any address? | Yes. Self-custody sends to any Monero address. source |
| Swaps and third parties | featherwallet.org lists no built-in exchange or swap, so funds don't pass through a third party inside the app. source |
| Monero and Zcash | XMR: send/receive ZEC: not supported source |
Official links
- Website:
featherwallet.org - Website:
docs.featherwallet.org - GitHub:
github.com/feather-wallet/feather
Where we confirmed these
Incidents
| Date | What happened | Amount | Outcome | Source |
|---|---|---|---|---|
| 2024-10-08 | 2.7.0 fixed a display bug: payments made with a payment ID could show the base address instead of the integrated address, which 'could lead to a potential loss of funds' if that address was copied and reused | fixed in 2.7.0 | source | |
| 2024-04-28 | Sending broke: versions 2.6.5 and below failed to build transactions ('Unrealistic number of outputs in output distribution') once Monero passed 100 million RingCT outputs; emergency release 2.6.6 | fixed in 2.6.6 (follow-up 2.6.7 for Linux startup) | source |