Feather Wallet

What Is Feather Wallet?

Running Monero the way it’s meant to be used—without outsourcing privacy to someone else’s server—usually comes with friction: heavy clients, slow syncs, confusing settings, and too many chances to leak metadata. Feather exists for people who want a desktop Monero wallet that’s fast to operate, defaults to sensible privacy choices, and still exposes the knobs advanced users actually care about.

Feather targets a specific sweet spot: a lightweight desktop GUI that can connect to remote nodes (or your own local node) without turning into a “view-key-to-a-third-party” style light wallet. It’s built for Linux, Windows, macOS, and explicitly supports privacy-focused environments like Tails/Whonix builds. The project positions Feather as “small and fast,” beginner-friendly, but with a feature set comparable to advanced Monero tooling. (github.com)

What makes it distinctive in practice is the privacy posture: Feather routes network traffic over Tor by default (with a documented exception for wallet synchronization), and it also supports routing traffic over I2P if you configure it. That combination—desktop GUI, remote-node workflow, and anonymity-network routing options—aims at people who care about metadata, not just on-chain privacy. (docs.featherwallet.com)

Feather Wallet Features and Performance

Feather is a Monero-only desktop wallet with official builds for Linux, Windows, and macOS, plus a dedicated build option for Tails/Whonix. The official download page also publishes PGP signatures for release artifacts and advertises alternative access via onion and I2P addresses, which is a practical nod to users who don’t want to fetch wallet binaries over clearnet. (featherwallet.com)

On the networking side, Feather’s “first start” flow makes a key design choice explicit: it must connect to a Monero node to scan for transactions, and using third-party nodes has privacy implications. For most users, Feather offers “auto connect” using a built-in list of “high-performance nodes hosted by the Feather team and trusted members of the Monero community,” chosen at random. If you don’t like that, you can select a custom remote node or connect to a local node you run yourself. (docs.featherwallet.com)

Feather’s default traffic routing is privacy-forward but not absolutist. Documentation states it routes all network traffic over Tor by default except wallet synchronization, because sync traffic is large and “very slow over Tor.” The docs claim this is a privacy/convenience trade-off because the remote node “does not learn much about your wallet during synchronization” (and points users to deeper node/privacy documentation). If you require always-on Tor, the UI provides that choice—but it’s not the default. (docs.featherwallet.com)

If Tor isn’t your thing (or your threat model is different), Feather can be configured to route all network traffic over I2P. The I2P guide documents using i2pd, switching the proxy type to I2P in Settings → Network → Proxy, and notes that node connections and other traffic (including the optional websocket connection, if enabled) will also go over I2P.

For advanced control and operational safety, Feather’s documentation set includes capabilities that matter in real-world wallet hygiene: creating view-only wallets, exporting transaction history, freezing/thawing outputs (coin control), and importing transactions. These aren’t “nice-to-have” checkboxes—coin control and export/import workflows are how careful users avoid accidental address reuse patterns, manage UTXO-like outputs, and do offline/airgapped-style operations where appropriate. (Feather’s docs explicitly include guides for view-only wallets and freezing/thawing outputs.) (docs.featherwallet.org)

Hardware wallet support is also documented—important for people who want to keep spend keys off the host machine. Feather’s hardware wallet support page lists supported Trezor models (Model T, Safe 3, Safe 5) and notes the Trezor Safe 7 is not currently supported due to a new device communication protocol not yet implemented in the Monero codebase. The same page includes a comparison table listing several Ledger and Trezor devices and notes (at a high level) properties like secure elements and firmware openness, but the key point for Feather users is simple: it supports common Trezor options for Monero, and it expects the underlying Monero codebase to handle device protocol support. (docs.featherwallet.org)

Finally, there’s the build-and-update story. The Feather GitHub repository describes it as free and open-source under a BSD-3-Clause license, and includes a Guix-based workflow intended for reproducible release binaries and attestation steps (via a separate signatures/attestation repo referenced in documentation). The updater documentation also describes how Feather checks for updates and fetches a PGP-signed hashes file from a hardcoded domain over Tor, which is the kind of detail you want to see when evaluating supply-chain risk. (github.com)

Pricing and Plans

Feather’s pricing model is straightforward: it’s free to use. The project describes itself as “a free Monero desktop wallet,” and the GitHub repository likewise calls it “free and open-source.” There are no subscription tiers, no paid “pro” plan, and nothing resembling a commercial VPN-style pricing table on official sources we reviewed. (github.com)

Because there’s no purchase, there’s no refund policy window to evaluate. Your “cost” is operational: you’re responsible for safe downloads (signature verification is recommended) and for understanding the privacy trade-offs when connecting to third-party nodes. (github.com)

Privacy and Security Assessment

Feather is built for a privacy-centric Monero workflow, but it’s not magic. A desktop wallet still runs on an OS that can be compromised; a remote node can still observe network-level metadata; and “privacy coin” users often forget that wallet metadata is a big part of the risk. Feather at least tackles that reality head-on in its documentation and defaults.

Network privacy (Tor/I2P). Feather routes network traffic over Tor by default, with one stated exception: wallet synchronization. The docs justify that exception on performance grounds and claim the privacy impact is limited relative to routing everything through Tor. Whether you agree depends on your threat model—but the important part is that it’s documented, not hidden. For users who need stronger metadata protection, Feather also documents configuration for routing all traffic over I2P. (docs.featherwallet.com)

Remote nodes and trust. Feather’s setup guide explicitly warns that connecting to third-party nodes has privacy risks and provides three paths: auto-connect to a curated list, manually choose a remote node, or connect to your own local node. Notably, Feather does not route traffic to local nodes over Tor (as documented). That makes sense in most home setups (your local node is reachable locally), but it’s a detail users should understand when they’re designing a compartmentalized setup. (docs.featherwallet.com)

Open-source and build integrity. Feather is open-source on GitHub and is licensed under BSD-3-Clause. The repo and docs reference a Guix-based process for reproducible release builds and an attestation/signatures workflow. In plain terms: the project is at least attempting to make “downloaded binary equals built-from-source result” verifiable, which is a meaningful countermeasure against build-server compromise and tampered releases. (github.com)

Key management and seeds. Feather supports multiple Monero seed schemes, and the docs are unusually clear here. Current Feather uses Polyseed for 16-word mnemonic seeds, older versions used a deprecated 14-word scheme, and Feather can restore wallets from Polyseed, 14-word, and standard 25-word seeds. The docs also make clear you can’t “convert” between some formats (e.g., 14-word to Polyseed isn’t possible; 25-word to Polyseed isn’t possible), which matters when users assume mnemonic formats are interchangeable.

Documented incident / self-criticism. Feather’s changelog includes a detailed write-up of a denial-of-service issue tied to an “Output distribution checks” patch committed to Feather’s fork of the Monero wallet library (dated August 29, 2021). The author explicitly concludes the sanity check should not have been added and acknowledges a failure to properly document/monitor/maintain the patch, which “ultimately lead to the denial of service,” and instructs users to upgrade to a fixed Feather version (2.6.6 or above) to resolve it. This is the kind of disclosure that’s both a red flag (a mistake happened) and a green flag (it’s transparently documented with remediation).

What we did not find in official sources: a third-party “no-logs audit” (that concept mostly applies to VPNs, not local wallets) or a formal external security audit report for Feather itself. If you’re evaluating Feather for high-stakes use, treat it like any other hot-wallet GUI: reduce attack surface, verify releases, and consider hardware wallet integration.

Strengths and Limitations

Strengths

• Privacy-aware defaults that are actually documented. Tor routing by default (with a clearly described sync exception) and documented I2P routing support are real features, not vague “privacy mode” marketing. (docs.featherwallet.com)
• Serious download hygiene support. Official downloads include PGP signatures and the project recommends verifying releases; the updater design also references fetching a PGP-signed hashes file over Tor. (github.com)
• Hardware wallet support (including modern Trezor models). The docs explicitly list supported Trezor devices and explain current limitations (e.g., Trezor Safe 7 not supported yet). (docs.featherwallet.org)
• Advanced controls are present. Feather’s docs cover view-only wallets, output freezing/thawing, transaction history export, and transaction import—features advanced users rely on to manage operational risk. (docs.featherwallet.org)
• Free and open-source. The repository and official site both describe Feather as free, and the code is publicly available under BSD-3-Clause. (github.com)

Limitations / trade-offs

• Default Tor routing is not “everything, always.” Wallet synchronization is excluded by default due to performance constraints, which may be unacceptable for some threat models. (docs.featherwallet.com)
• Remote node usage is inherently a privacy trade-off. Feather warns about third-party node privacy risks, but if you auto-connect you’re still trusting a curated node list unless you run your own node. (docs.featherwallet.com)
• I2P requires extra setup. Feather’s I2P mode (as documented) depends on installing and running i2pd and configuring proxy settings correctly.
• Past reliability/security mistakes happened. The changelog’s denial-of-service postmortem is candid, but it still documents a real issue users had to upgrade to fix.

Who Should Use Feather Wallet?

A good fit if you’re:

1. A Monero user who wants privacy-aware networking without living in the CLI. Tor-by-default (and optional I2P) is built into the documented workflow, and it’s designed to be usable for normal desktop users. (docs.featherwallet.com)
2. Someone who wants hardware wallet protection for Monero on desktop. Feather documents Trezor hardware wallet support (with a clear list of supported models and known unsupported ones). (docs.featherwallet.org)
3. An advanced user who cares about coin control and operational tooling. View-only wallets, freezing/thawing outputs, and transaction export/import features are documented parts of the product. (docs.featherwallet.org)

Not a great fit if you’re:

1. Looking for a multi-coin wallet. Feather is explicitly positioned as a Monero desktop wallet, not an everything-wallet. (github.com)
2. Unwilling to deal with node/privacy trade-offs. If you won’t run a local node and don’t want to trust remote nodes at all, any remote-node wallet workflow (including Feather) will feel like a compromise. (docs.featherwallet.com)
3. Needing “set-and-forget” anonymity-network ops with no setup. Tor routing is built in, but I2P mode (as documented) requires installing i2pd and configuring proxy settings; that’s not beginner-proof.