Feather Wallet Setup and Privacy Settings

Feather is an independent, open-source Monero desktop wallet. It is not the Monero reference wallet. Feather gives you direct control over node selection, Tor routing, subaddresses, accounts, and individual outputs. Those controls help only when you understand what each one changes.

1. Verify the download

Use the official Feather download page. As of this review, that page lists version 2.8.1 as the latest release. It provides a separate PGP signature for each package, a signed list of SHA-256 hashes, and the project signing key.

A matching checksum only proves that your file matches the listed file. Verifying the PGP signature on the hash list checks that the list was signed with Feather's release key. The project documents its current key and fingerprint in the release-signing guide. Obtain the key and fingerprint from more than one official project location before trusting it.

Do not install a copy from a search advertisement, forum attachment, or third-party download site. A wallet installer can read keys and replace receiving addresses. Download verification matters more than any later privacy setting.

2. Create the wallet and protect the seed

Open File → New/Restore, choose Create new wallet, and copy the words in order. Feather's wallet creation guide says new wallets use a 16-word Polyseed. The seed can recover the funds if the wallet files are lost.

Write the seed on paper or another offline medium. Do not save it in cloud notes, email, screenshots, or clipboard managers. Feather then asks for a password to encrypt the wallet files. That password protects the local files. It does not replace the seed, and it cannot stop malware that reads the wallet while it is open.

A seed restore recovers the balance, transaction history, accounts, and subaddresses. It does not recover contacts, account labels, subaddress labels, transaction keys, transaction descriptions, or the recorded destinations of outgoing payments. Feather lists these limits in its restore documentation. Back up any records you need separately, without exposing the seed.

3. Decide who supplies blockchain data

Feather connects to a random server from its curated remote-node list by default. You can review this before the first network connection and change it later under Settings → Network → Nodes.

According to Feather's node documentation, a remote node does not learn your wallet addresses, balance, incoming transactions, payment destination, or amount. It still supplies data used for synchronization and transaction construction. A malicious node can try to identify the true input, manipulate the fee, or associate a broadcast transaction with an IP address when the traffic does not use Tor. Feather says it warns when it detects the documented input attack.

A node you control removes that third-party dependency. To connect one on the same computer, disable Let Feather manage this list, add a custom node, and enter 127.0.0.1:18081 for Monero mainnet's default RPC port. Feather's local-node instructions also cover nodes on a private network.

4. Know what Feather sends over the network

Feather's network traffic table identifies three connection types: node traffic for synchronization and transaction construction, a websocket for fiat prices, Monero community crowdfunding data, and the current block height, plus an update check to featherwallet.org when the websocket is enabled.

Transaction broadcasts use Tor by default. This protects the network origin of the broadcast from the remote node, but it does not make a compromised computer safe. It also does not hide information that you reveal to an exchange, merchant, or other counterparty outside Feather.

5. Use subaddresses instead of reusing one address

Create a new receiving address for each person or service. Feather recommends labelling an address before copying it so you know who received it and avoid reuse. Its receiving guide says not to give the same address to more parties than necessary.

Every subaddress in an account sends funds to the same wallet account. A sender who sees one subaddress cannot derive your other subaddresses from it. The label remains local wallet data and is not restored from the seed.

Use separate accounts when you need separate balances and transaction histories. Feather notes that accounts can help keep identities separate, but they do not protect against every cross-account analysis. Do not treat an account label as a privacy boundary by itself.

6. Use output controls carefully

Enable View → Coins to inspect wallet outputs. Feather lets you freeze an output so it cannot be selected for a future transaction. Thawing makes it spendable again. The project documents this in its output control guide.

Freezing can preserve separation between funds received in different contexts. It can also leave you without enough available balance for a payment. Spending several outputs together creates an observable relationship between those inputs inside the transaction. Coin control needs a reason and records, not random clicking.

Before receiving serious funds

• Confirm the installer against Feather's signed hash list.
• Store the seed offline and verify every word and its order.
• Set a strong wallet-file password.
• Choose a remote node or connect a node you control.
• Check the Tor and websocket settings against your threat model.
• Create and label a fresh subaddress for the first sender.
• Receive and send a small test amount before moving more.

Sources

• Feather Wallet: official downloads and signed hashes
• Feather Wallet documentation: create a wallet
• Feather Wallet documentation: nodes and remote-node risks
• Feather Wallet documentation: network traffic
• Feather Wallet documentation: connect to a local node
• Feather Wallet documentation: restore from seed
• Feather Wallet 2.8.1 release record