How to Swap XMR to BTC from Cake Wallet: Step-by-Step

If you have been stacking Monero in Cake Wallet and now need Bitcoin liquidity — to pay an invoice, fund a Lightning channel, or move into a BTC-only exchange — you are in one of the most common situations in the privacy-coin world. Cake Wallet has grown from a niche iOS-only project in 2018 into one of the most downloaded non-custodial multi-chain wallets of 2025, with roughly two million active installs across Android, iOS, macOS, Linux, and Windows. Yet the in-app "Exchange" tab can be confusing the first time you use it, and a wrong click can leak metadata you spent months trying to protect. This guide walks you through the entire XMR-to-BTC flow from Cake Wallet, screen by screen, including the parts the official documentation glosses over: how to pick between integrated providers, when to route through MoneroSwapper for a no-KYC alternative, and how to verify the BTC actually arrived without doxing the receiving address. Everything below assumes you already have a funded Cake Wallet seed and a place to receive the Bitcoin.

Why this swap is harder than it looks

Trading XMR for BTC is mechanically simple — pick an amount, paste an address, broadcast — but the privacy stakes are higher than in any other major pair. Monero's ring signature, RingCT, and stealth address stack hide sender, receiver, and amount on-chain. The moment funds land on a transparent Bitcoin output, every previous obfuscation can be undone by a chain-analysis firm if the exit address is ever linked to your identity. The hop you are about to perform is the single most important choke point in the entire privacy chain, and how you execute it determines whether your Monero history stays sealed or becomes a forensic breadcrumb.

• Address reuse risk: sending all your swapped BTC to a single address you have used before merges your Monero exit with prior Bitcoin activity in any clustering heuristic.
• Provider logging: some "instant exchange" integrations inside wallets retain IP, browser fingerprint, and counterparty addresses for years, even when they advertise "no KYC".
• Timing correlation: a swap initiated, settled, and forwarded within the same minute creates a near-perfect time-stamp link between your XMR view-key zone and a future BTC address.
• Fee surface: a 1.5% provider spread on a 5 XMR swap is roughly $20 of friction; over a year of routine swaps this compounds into real losses if you do not check rates.

Cake Wallet itself does not act as the swap provider. It is a router: the in-app "Exchange" screen forwards your order to one of several third-party desks (SimpleSwap, ChangeNow, Trocador aggregator, Exolix, MajesticBank, and a few more depending on your app version). The wallet signs the outbound Monero transaction from your local seed, but the actual XMR-to-BTC conversion happens on the third party's books, and that is where most of the privacy risk lives.

Preparing Cake Wallet before you press Exchange

Five minutes of preparation now prevent the most common mistakes — sending to the wrong network, getting stuck on a stalled order, or accidentally connecting through an exit node that the provider has flagged for region blocking. Treat the checklist below as mandatory rather than optional, especially if this is your first Monero-to-Bitcoin swap.

1. Confirm wallet sync and balance visibility

Open Cake Wallet, switch to your Monero wallet (the one funded with XMR), and wait until the small sync indicator in the header reads "Synchronized". If the wallet shows "1 block behind" forever, your remote node is overloaded — swap to a different node under Settings → Connection and node, then choose a public node from the curated list (cakewallet.com:18081, xmr-node.cakewallet.com:18081, or a Feather-recommended node). A desynced wallet will let you start an exchange, but the outbound transaction will sit in your mempool unbroadcast, and the provider will time out and refund — minus their spread.

2. Generate a fresh BTC receiving address

If you are sending the BTC to another wallet you control — a hardware device, Sparrow, Blue Wallet, or a separate Cake Wallet Bitcoin profile — generate a brand new address there first. Never reuse a previously used Bitcoin address as your swap destination. The standard receive screen in Sparrow, BlueWallet, or the Bitcoin wallet inside Cake itself will give you a fresh bech32 (`bc1q…`) address each time. Copy it now and verify the first four and last four characters match what you paste later — clipboard hijackers remain a real threat on Android in 2026.

3. Decide if you want Tor

Cake Wallet on desktop and Android supports routing the connection to its exchange providers through Tor via the built-in proxy settings. iOS users will need to run Orbot in the background. Tor adds 5–15 seconds of latency to quote refreshes but removes your real IP from the provider's logs. For any swap above roughly half a Monero ($75 at recent prices), enabling Tor is worth the friction.

4. Pick a swap mode: floating vs fixed

Cake Wallet's exchange screen lets you choose between a "Floating rate" and a "Fixed rate" quote. Floating gives you the best possible price at settlement time but exposes you to roughly 0.5–2% slippage if XMR moves during the swap. Fixed locks the rate but adds a 0.5–1% premium and a hard timeout (typically 30 minutes) — if your transaction is not confirmed in time, the provider may pay out at the floating rate anyway. For swaps under 10 XMR with stable market conditions, floating is almost always cheaper. For larger orders, fixed protects you from a flash dip.

The step-by-step XMR-to-BTC flow inside Cake Wallet

Here is the exact sequence, written for Cake Wallet 4.x on Android and iOS (the desktop builds use almost identical screens). Have your fresh BTC receive address copied to the clipboard before step 4.

1. From the home screen of your Monero wallet inside Cake, tap the menu icon and select Exchange. The top half of the screen shows what you are sending; the bottom half shows what you will receive.
2. In the upper "You send" panel, confirm XMR is selected. In the lower "You receive" panel, tap the asset icon and select BTC. Make sure the network reads "Bitcoin" — not "BTC (Lightning)" or any wrapped variant. If you want Lightning, that is a separate flow with different providers.
3. Enter the amount you want to send in XMR. The receive field updates in real time with the current quote. Below the receive field you will see the active provider (e.g. "via ChangeNow" or "via Trocador"). Tap that label to see all available providers and their rates side by side — Cake will pre-select the best floating rate, but you can override.
4. Paste your fresh BTC bech32 address into the "Recipient Address" field. Cake checks the format and will reject malformed strings before you can continue. Verify the first four and last four characters character-by-character against your source.
5. Leave the "Refund Address" field set to your own Monero subaddress. Cake auto-fills a new subaddress here; this is where the XMR will return if the swap fails. Do not paste your main address.
6. Choose the rate type — Floating or Fixed — using the toggle at the top of the exchange screen. Review the displayed mining fee for the Monero side; Cake uses normal priority by default, which clears in 20 minutes.
7. Tap Exchange. The next screen shows a one-time deposit address generated by the provider, an exact XMR amount, and a countdown timer. Tap Confirm to instruct Cake to broadcast the Monero transaction from your wallet to that deposit address.
8. Authenticate with your PIN or biometrics. Cake signs the transaction locally, broadcasts it to the Monero network, and immediately switches to a status screen showing the order ID, the transaction hash, and a progress bar (Waiting → Confirming → Exchanging → Sending → Completed).
9. Wait. A typical XMR-to-BTC swap requires 10 confirmations on Monero (about 20 minutes) plus 1–2 confirmations on Bitcoin (about 20 minutes), so plan for roughly 30–45 minutes total. Cake updates the status screen in real time, and the order also appears under Trade History.
10. When the status reads "Completed", verify the Bitcoin arrived at your destination wallet by checking the receive address on the destination side. Note the order ID and screenshot the status screen — you will need both if you ever have to contact provider support.

Never close Cake Wallet during steps 7 and 8 before the Monero broadcast confirms in your transaction history. If the app is killed mid-broadcast on iOS, the signed transaction may be lost and the provider will mark the order expired even though you intended to send.

Built-in providers vs an external swap: which is right for you?

Cake Wallet's in-app exchange is the most convenient path, but it is not the only one. For privacy-maximalist swaps, many users prefer to send Monero out manually to a no-KYC swap service like MoneroSwapper and have the Bitcoin land in a completely unlinked wallet. Below is the practical trade-off table.

For amounts under about 2 XMR, the convenience of Cake's in-app exchange usually wins. For larger sizes, opening a Tor browser, visiting MoneroSwapper, and pasting the deposit address into Cake by hand adds maybe 90 seconds and significantly reduces metadata exposure. If you swap regularly, mixing the two approaches randomly also reduces pattern-of-life signals.

A worked example: 3 XMR to BTC into a fresh hardware wallet

Suppose Alice has 3.2 XMR in Cake Wallet on her Pixel running GrapheneOS and wants 0.025 BTC delivered to a brand-new address on her Coldcard Q. The XMR/BTC rate at the time of the swap is roughly 0.0078 BTC per XMR. Here is how she should execute the trade.

First she connects the Pixel to her usual Wi-Fi over a self-hosted WireGuard VPN, opens Orbot, and routes Cake Wallet through Tor (Settings → Privacy → Connect via Tor). She generates a new bech32 address on the Coldcard via the Q's air-gapped receive screen, double-checks the first and last characters on the physical screen, and copies the address into her phone using a QR code rather than typing — manual entry remains the single biggest source of catastrophic address typos.

In Cake she taps Exchange, selects XMR send / BTC receive, enters 3.0 XMR (she will keep 0.2 XMR as buffer), and chooses Floating rate because the market has been calm. The aggregator shows MajesticBank at the best rate; she taps the provider label to confirm. She pastes the Coldcard address, leaves refund address auto-filled, and reviews the receive estimate of about 0.0233 BTC after spreads and network fees.

She taps Exchange, scans her face for biometric auth, and the Monero transaction broadcasts. Cake shows order status "Confirming" within 30 seconds. She locks the phone and walks away. Twenty-five minutes later the order status reads "Sending", and three minutes after that it switches to "Completed". She opens her Coldcard companion app, confirms the unconfirmed UTXO arrived from a clean coinbase-distant address, and waits for two confirmations before considering the swap final. Total elapsed time: 31 minutes. Total fees: roughly 0.7% spread plus mining fees on both chains — about $7 on a $290 transaction.

Crucially, no element of this swap exposes Alice's identity. The IP seen by the swap provider was a Tor exit node; the deposit address was a one-time provider-generated string; the BTC receive address has never been used before and lives on an air-gapped device; and the refund address is a fresh Monero subaddress under her control. If she wanted to be extra cautious she could now use Whirlpool-style coinjoin or Payjoin on the resulting UTXO before spending it, breaking even the timing correlation between her XMR exit and any future BTC outgoing transaction.

Troubleshooting common problems

Even with a clean setup, things occasionally go wrong. Below are the four scenarios that account for over 90% of the user reports we see in Monero community forums.

The order stays on "Waiting" forever

Almost always this means the Monero transaction has not yet reached enough confirmations on the provider's side. Open the order details in Cake, copy the Monero tx hash, and look it up on a block explorer such as xmrchain.net (over Tor, ideally). If it has 10+ confirmations and the order still says Waiting, the provider has a backlog — wait another 30 minutes before contacting support. If your tx hash is not visible on any explorer, the broadcast never completed; rebroadcast manually using the "Rebroadcast" option under Trade History.

The provider asks for KYC mid-order

Both SimpleSwap and ChangeNow occasionally trigger an "AML review" after the deposit lands, demanding ID before releasing the BTC. This is rare under 1 XMR but increasingly common above 5 XMR. You have two options: comply (defeats the privacy purpose), or refuse and request a refund to your auto-filled Monero refund address. Refunds typically arrive within 1–3 business days. To avoid this scenario, route larger swaps through MoneroSwapper-listed desks that publicly commit to no-KYC for all amounts.

The rate at completion is worse than quoted

If you chose Floating, this is expected — the live market price at the moment of settlement governs your payout. If you chose Fixed and got a worse rate, the order timed out (Monero confirmations did not arrive within the lock window) and the provider fell back to floating. Future fix: bump the Monero mining fee priority to "High" inside Cake Wallet for time-sensitive Fixed-rate swaps.

The BTC never arrives

First check whether the provider has marked the order Completed. If yes, paste your destination Bitcoin address into a block explorer such as mempool.space and look for the incoming transaction. If the order is Completed and the tx is visible on the Bitcoin chain but not in your wallet, your wallet may simply be unsynced — give it ten minutes. If the order is Completed but no tx exists on the Bitcoin chain, contact the provider with the order ID immediately. Cake Wallet's role ends at "Monero broadcast successful"; from there the dispute is between you and the third-party desk.

FAQ

Is the in-app exchange in Cake Wallet KYC-free?

Mostly, but not guaranteed. Cake itself does not collect KYC information — it never asks for your name, email, or ID. However, the third-party providers it routes orders to (SimpleSwap, ChangeNow, Exolix, Trocador, MajesticBank, and others) each have their own AML policies. Smaller orders almost always complete without ID checks; larger orders or orders flagged by their risk engines may be paused with a KYC request. For guaranteed no-KYC behaviour at any size, prefer no-KYC-only desks accessible via MoneroSwapper.

How long does an XMR-to-BTC swap from Cake Wallet take in 2026?

Plan for 25–45 minutes end to end. The bulk of that is waiting for 10 Monero confirmations (about 20 minutes at 2-minute block intervals) plus 1–2 Bitcoin confirmations (10–20 minutes depending on mempool congestion). The provider's internal processing typically adds 1–3 minutes. Swaps that complete in under 15 minutes usually used a 0-confirmation Bitcoin payout, which only some providers offer and which forces you to wait for confirmations on the receive side anyway.

What fee should I expect on a Cake Wallet XMR-to-BTC swap?

Total cost is usually 0.5%–2% of the swap value. This decomposes into roughly 0.3–1.5% provider spread (the gap between their buy and sell rate), 0.1% Monero mining fee at normal priority, and a Bitcoin mining fee that varies wildly with mempool conditions — sometimes $1, sometimes $15. Always compare providers using the side-by-side picker inside Cake's exchange screen before confirming; the cheapest option can change hour to hour.

Can I cancel a swap after I press Exchange?

Once Cake Wallet broadcasts the Monero transaction, no. The Monero network is irreversible. You can stop the swap before pressing Confirm on the provider deposit screen — at that point you have only generated an unbroadcast transaction, which you can simply discard. After broadcast, the only "cancel" is to let the order fail (do not send, or send wrong amount) and wait for the provider's automatic refund to your auto-filled refund subaddress.

Should I keep my BTC in Cake Wallet after the swap?

Cake's Bitcoin wallet is non-custodial and uses your seed phrase, so it is reasonably safe for spending amounts. For long-term storage of swap proceeds above $500 or so, move the BTC to a hardware wallet (Coldcard, Trezor Safe, BitBox02) or an air-gapped Sparrow setup. Hot mobile wallets, however well written, remain a malware target.

Does my IP leak when I use the exchange screen?

Yes, unless you enable Tor. By default Cake connects directly to the provider's API to fetch quotes and submit the order, exposing your real IP. Turn on Tor under Settings → Connection if you want this hidden. Note that even with Tor enabled, the provider still sees your Monero refund subaddress and the destination Bitcoin address — only your network identity is hidden, not the on-chain identifiers.

Conclusion

Swapping XMR to BTC from Cake Wallet is a five-minute task if you have prepared correctly and a half-hour ordeal if you have not. The mechanical steps are simple, but the difference between a clean swap and a metadata-leaking one comes down to a fresh Bitcoin receive address, an enabled Tor route, a deliberate provider choice, and a refund subaddress you never reuse. For most users in 2026 the in-app exchange is good enough for small amounts. For anything you would rather not see resurface in a future chain-analysis report, route the order through a no-KYC aggregator like MoneroSwapper, paste the deposit address into Cake manually, and let the Monero privacy stack and the new Bitcoin wallet do the rest. The 90 seconds of extra friction buys you years of forward privacy — and that is a trade worth making.