Feather and Cake Wallet get mentioned in the same breath so often that people assume they are competing options. They are not. Feather is a desktop Monero wallet built for people who want control over their node and a small, auditable program that runs on Tails. Cake is a multi-currency wallet for phones and desktops with a built-in exchange. They cover two different jobs, and this is both the comparison and the setup.
Feather
Feather is a free, open-source Monero wallet for Linux, Tails, macOS and Windows. It is written in C++ with Qt and deliberately small: it runs comfortably on a live system, in a virtual machine or on a Raspberry Pi, and it starts fast because it is not trying to be everything.
It is Monero only. No Bitcoin tab, no token list, no exchange on the main screen. What it does have is a serious feature set: multiple accounts, subaddresses, view-only wallets, hardware wallet support, transaction proofs, output freezing, portable mode, and support for both Tor and I2P.
Install and verify
Download from featherwallet.org or the GitHub releases page, then verify before running anything. Releases are signed, and the release signing key fingerprint is:
8185 E158 A333 30C7 FD61 BC0D 1F76 E155 CEFB A71CImport the key, check the signature, and only then install. A wallet from an unverified mirror is not a wallet, it is someone else's wallet.
Create the wallet
On first start choose Create new wallet. Give it a name and a password. The password encrypts the wallet file on disk; it is not the seed and cannot recover the wallet if the file is lost.
Feather generates a standard 25-word Monero seed. Write it on paper, in order, and check it twice. Do not screenshot it, do not put it in a notes app, and do not keep it beside the wallet file. On Tails without persistence, the seed is the only thing that survives a reboot: the wallet file is disposable, the seed is the wallet.
Leave the restore height at its default for a new wallet. It only matters when restoring an existing one, where the wrong height means a long resync or a balance that looks empty.
Node and Tor
Feather needs a node to read the chain. On first run it offers a list of remote nodes. That is fine to start, and it means the node operator can see your IP and that you broadcast a transaction, though not its contents. If you run your own node, point Feather at it; that is the privacy upgrade the wallet is built to support.
Tor and I2P are in the network settings. On Tails the Tor daemon is already running, so Feather can use it immediately. On Windows or macOS you need Tor running separately; Feather will not start it for you.
Receive and send
For receiving, generate a fresh subaddress per order rather than handing out your primary address. Feather handles this cleanly, and it means one leaked address does not tie your whole history together. The view key is there if you need to prove a payment without giving up spend authority.
Sending is paste, amount, fee level, confirm. Monero fees are small and the difference between priority levels is cents. Read the address on screen before confirming; there is no chargeback.
Cake Wallet
Cake is open source, non-custodial, and available for Android, iOS, macOS and Linux. There is no Windows build. It supports Monero, Bitcoin, Ethereum, Litecoin, Bitcoin Cash, Polygon, Solana, Tron, Nano and several others, and it adds what a desktop Monero wallet does not: a built-in exchange, the ability to buy and sell, a payment card, and an interface a normal person can use without reading documentation.
Install without an app store
Not from the App Store or Google Play. Both record the install against an Apple ID or Google account, tie it to the device, and keep a history you cannot delete. That is a permanent link between the wallet and a real identity, which is the opposite of the point.
Use the project's own distribution: the APK from the GitHub releases page, or the F-Droid repository. Both can be verified. On Android the signing certificate hash is published in the repository, so you can check that the file you installed matches the official build with apksigner or an APK verifier.
On iOS there is no anonymity-preserving install path at all; every route goes through an Apple ID. If Cake has to run on a phone without being linked to you, Android with a verified APK is the only version of that plan that holds up. For desktop, take the macOS or Linux build from GitHub releases.
Create the wallet
Create a new wallet, choose Monero, and write down the 25-word seed. Cake will offer to back the wallet up to iCloud or an external location. Refuse it: an iCloud backup is tied to an Apple ID, and the seed is the wallet.
Set a password. For Monero specifically, Cake keeps the view key on the device, supports subaddresses and multiple accounts, and lets you set a restore height. Those are the things that make it a real Monero wallet rather than a token screen with a Monero logo.
Tor and nodes
In the privacy settings, enable Tor-only connections. It routes the app's traffic through Tor, including node requests and exchange calls. Slower, and the setting that makes the app behave like the rest of your setup instead of like a consumer app.
Cake ships with default remote nodes; you can leave them or set your own. It also lets you configure a proxy for Monero nodes that works with Tor and I2P, which matters if you route the node connection separately from app traffic.
Receive, send, and swaps
Receive shows an address and a QR code; Cake supports subaddresses and accounts, so use a fresh one where it allows it. Test in both directions before anything significant.
The exchange tab swaps between supported currencies. It is convenient and it is not a privacy tool: the partner behind the swap may require identification depending on pair and amount, and the swap creates a record on the other side. If a swap matters to your privacy, do it outside the app and treat Cake as where the coins land, not where the link is broken.
What each is actually for
Feather is the wallet you use on a computer, particularly a Tails session, when you want to hold Monero, receive it to clean subaddresses and send it without a company in the middle. It is the better choice for anything involving a market: small, running on the same hardened system as everything else, and able to talk to your own node.
Cake is the wallet you use when you need to move between currencies or touch the ordinary financial system: swapping, buying or selling, paying with the card, holding a small balance on a phone. It is convenient in exactly the ways Feather is not, and that convenience is the risk surface.
The cash-out workflow people describe
One route circulates as a template. The short version: swap XMR to BTC through a crypto mixer, receive the BTC into an Electrum desktop wallet, then send it to a payment app, sell it there and withdraw to a linked bank account. Starting from BTC, reverse it: swap to XMR into Feather, move it to Cake, swap back to BTC inside Cake, then cash out.
The reasoning for the extra hops is that an external mixer breaks the direct link between source and destination in a way an in-app swap may not. The direction of that argument is reasonable. The confidence is not.
Where that plan is weaker than it sounds
Mixers are businesses. They log IP addresses, destination addresses and amounts, and some require identification above certain thresholds. A service that does not ask who you are still knows which wallet sent coins and which wallet received them, which is exactly the link the extra hop is meant to break.
Payment apps are regulated financial institutions. They flag crypto inflows, close accounts and file reports, and the bank account at the end is the strongest identity anchor in the chain. No amount of wallet hopping changes the fact that the last step is a KYC account with your name on it.
Timing and amounts correlate. A swap, a transfer and a withdrawal within half an hour for the same value are not three independent events.
Mixers also have a habit of becoming evidence. ChipMixer was seized in 2023, Sinbad was sanctioned the same year, and the founders of Samourai Wallet were charged in 2024 over a service the government described as a mixer. In each case the operators kept records, the infrastructure was taken, and the records became the case. A mixer is not a hole in the chain; it is another company with logs, and one that attracts more attention than an exchange does.
The chain-analysis firms do not need to see inside the pool. They cluster by timing, by amounts, by the addresses that appear on both sides, and by the exchange records at either end. The on-ramp knows who bought the coins and the off-ramp knows who sold them; the middle is the part that has to be perfect, and it never is.
And Cake's exchange is not a laundering step because it is inside the app. It is a convenience feature run with partners, and it may ask for identification depending on the pair and amount.
One detail worth noting: the guides that recommend a specific mixer often include a referral link. A recommendation that pays the recommender is not neutral advice, whatever the fee.
Before you trust either wallet
Write the seed twice and store the copies separately. Restore one wallet from the seed on a spare device or a fresh install and confirm the balance appears; a seed you have never restored is a seed you are trusting on faith. Turn off cloud backups. Use subaddresses. Keep the phone and the computer separate where you can.
And do the test transaction. People lose funds every year to a wallet pointed at the wrong node, restored at the wrong height, or never actually backed up. The test costs almost nothing and it is the only proof the setup works.
Neither wallet is usually the weak point. The weak point is the route between the wallet and the rest of the world, and that route is made of companies that keep records.
