> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/cryptos/monero.md).

# Monero

Monero in Cake Wallet: Polyseed, 25-word and BIP39 seeds, syncing, accounts and subaddresses, view-only wallets, fee levels, and saving recipient addresses.

Official Website: [getmonero.org](https://www.getmonero.org/)

Monero `(XMR)` is the leading cryptocurrency focused on private and censorship-resistant transactions. It is a private, decentralized cryptocurrency that keeps your finances confidential and secure.

The majority of existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains. Transactions can be verified and/or traced by anyone in the world. This means that the sending and receiving addresses of these transactions could potentially be linked to real-world identities.

Monero, on the other hand, uses various technologies to ensure the privacy of its users.

## Seed Types

New Monero wallets use the 16-word Polyseed by default. On the creation screen you can also choose the 25-word legacy seed or a 12-word BIP39 seed. `Advanced Settings` also has an optional seed passphrase. Most people should leave it empty: a passphrase creates a completely different wallet, and if you forget it, your seed alone can't restore your funds.

{% hint style="info" %}
Only BIP39 Monero wallets can join [wallet groups](https://docs.cakewallet.com/features/managing-your-wallet/wallet-groups). Polyseed and legacy 25-word wallets cannot.
{% endhint %}

### How BIP39 Monero wallets work

Monero doesn't use BIP39 natively, so Cake Wallet turns a BIP39 recovery phrase into a regular Monero wallet. It does this the same way whether you create a BIP39 Monero wallet on its own or add Monero to a [wallet group](https://docs.cakewallet.com/features/managing-your-wallet/wallet-groups):

1. Your BIP39 phrase (plus your seed passphrase, if you set one) is turned into a BIP39 seed.
2. Cake Wallet derives the key at path `m/44'/128'/0'/0/0` (128 is Monero's coin type).
3. That key is converted into a valid Monero private spend key, and the wallet is then created exactly as if it had been restored from the matching 25-word Monero seed.

When you add Monero to a wallet group, its restore height is set to the day you add it.

**Restoring it in Cake Wallet:** restore the same BIP39 phrase as a Monero wallet. Cake Wallet recognizes it as a BIP39 phrase and repeats the same steps, so you get the same wallet back. Enter your seed passphrase too if you used one, and pick a restore height from before the wallet's first transaction.

**Restoring it in another Monero wallet:** not every Monero wallet supports this BIP39 conversion. If your phrase has 12 words, open `Recovery & Keys` and use the `Legacy` tab: it shows the same wallet as a standard 25-word Monero seed, together with its restore height. For a 24-word phrase there is no `Legacy` tab; use the private view and spend keys on the `Keys` tab to restore the wallet elsewhere.

## Syncing

{% hint style="warning" %}
The most common issue with Monero is an unsynchronized wallet.
{% endhint %}

To perform most interactions with your wallet, your wallet must be fully synchronized. There will be a green dot at the top of your home screen.

If you are stuck on the same block while syncing for a while, or it says disconnected, you should [try another node](https://docs.cakewallet.com/features/managing-your-wallet/manage-nodes) or another internet connection. Cake Wallet ships with several Monero nodes to pick from — see the [built-in Monero nodes](https://docs.cakewallet.com/features/managing-your-wallet/manage-nodes#built-in-monero-nodes) list.

If your wallet is not fully synced, your wallet balance may be incorrect, and you won't be able to send transactions. Wait until your wallet is fully synced before proceeding. Keep the app open with the screen on to keep syncing.

To keep your wallet up to date while the app is closed, enable [background sync](https://docs.cakewallet.com/features/advanced/background-sync). Background sync is available for Monero only.

## Accounts and subaddresses

Monero organizes your funds into accounts and subaddresses. This mirrors the [Receive page](https://docs.cakewallet.com/features/basic/receive-funds): accounts are separate buckets that each track their own balance and transactions, and subaddresses are generated automatically within an account.

![Monero addresses](https://content.gitbook.com/content/tSLIJ3VE2UcCjtTcoMgl/blobs/LquShCsGQqVmBzS9ak0D/monero%20addresses.png)

### Monero subaddresses

A Monero subaddress is a unique, unlinkable address that can be generated on-demand. Coins sent to it still arrive in your main wallet, but the sender cannot determine your wallet's main address. Cake Wallet automatically generates a new subaddress after each one is used.

To manage subaddresses yourself, open `Privacy settings` and disable `Auto generate subaddresses`. Then, on the `Receive` screen, tap the refresh icon in the top right to generate a fresh subaddress, and tap the address label tag to open the `Label address` sheet, where you can name the subaddress and tap `Continue`. Subaddresses always start with `8`; your main address starts with `4`.

![Labeling a Monero subaddress from the Receive screen](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/monero_subaddress_02_name_hl.png) ![The labeled subaddress shown on the Receive screen](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/monero_subaddress_03_created.png)

You can review all of an account's subaddresses under `Accounts and subaddresses` → `Addresses`.

![The list of subaddresses for a Monero account](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/monero_subaddress_01_addresses.png)

### Monero accounts

Each Monero wallet can have several accounts. We recommend this feature for advanced users only. Open `Settings` from the top right of the home screen, tap `Monero Settings`, then `Accounts`. Your accounts appear as a stack of cards, with the currently active account in front. The first time you open it, a short walkthrough explains how accounts work — tap `?` to see it again.

To switch accounts at any time, on your home screen tap the card of the account behind the active one — it moves to the front and becomes your active account.

On the Accounts screen, tap `Add Account` to create another account, and tap `⋮` on the front card to open `Edit Account` and rename it. You can have unlimited accounts, and each account can have unlimited subaddresses. The first indexed subaddress of each account (besides the main account) starts with an `8`.

![The Monero Accounts screen with accounts as a card stack and Add Account at the bottom](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.5.0/monero_accounts_01_accounts.png)

Balances and transactions for each Monero account are shown separately. While you're in one account, you can't see the balance and transactions of another — switch accounts to view each one. Each account's balance also appears in the account list.

Accounts can't be deleted, only archived. In an account's `Edit Account` screen on the Accounts page, tap `Archive Account` to hide it — its funds stay in the account, and you can bring it back from `Archived Accounts` at the top of the Accounts screen.

## View-only wallet

It's possible to create a Monero view-only wallet. You need the following information:

* Main Monero address (`4...`)
* Private view key
* Restore height (recommended, not required)

Restore from keys following [these steps](https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/recovery-phrase-or-keys). Leave the `Spend key (private)` field blank. Let the blockchain sync fully. After syncing, you should see all incoming transactions ( *including* incoming change). View-only wallets usually do not show an accurate balance (they cannot be relied upon for this purpose), and they will not show some types of outgoing transactions.

## Payments that need several transactions

{% hint style="info" %}
If a payment would have to be split into more than one Monero transaction — usually because your balance is spread over many small amounts — Cake Wallet stops it before sending and shows "This payment would be split into N transactions. Send smaller transaction to yourself first." Send a smaller amount to your own wallet first to consolidate your funds, then try the payment again.
{% endhint %}

## Monero fee levels

Cake Wallet follows the standard wallet2 fee levels. We recommend leaving your Cake Wallet fee for Monero as `Automatic`, the default. In the app the priorities appear as **Slow / Automatic (default) / Medium / Fast / Fastest**.

A higher priority pays a higher fee and is generally confirmed sooner; a lower priority is cheaper but can take longer to confirm. `Automatic` picks a fee based on current network activity, which is why we recommend it for most transactions.

| Cake Wallet name | wallet2 priority value | CLI name    | GUI Name  |
| ---------------- | ---------------------- | ----------- | --------- |
| Automatic        | 0                      | default     | Automatic |
| Slow             | 1                      | unimportant | Slow      |
| Medium           | 2                      | normal      | Normal    |
| Fast             | 3                      | elevated    | Fast      |
| Fastest          | 4                      | priority    | Fastest   |

## Monero save recipient addresses

Monero addresses (unlike Bitcoin) are never stored on the blockchain. When you send Monero to a recipient, the address you send to can only be recorded locally, on your device — never on the blockchain. So if you restore a Monero wallet from a seed or from keys, you will not see the Monero addresses that you sent funds to.

In Cake Wallet, saving that local record is **on by default**. To turn it off, go to `Settings` → `Privacy` and untick `Save recipient address`.

{% hint style="warning" %}
While `Save recipient address` is off — the recipient address of every Monero transaction you send is **not stored at all**. It is not on the blockchain and it is not on your device, so it is gone permanently the moment you send.

This matters if you ever need to **prove that you made a payment**. With no saved recipient address there is no local record to point to, and the Monero blockchain has no record either.
{% endhint %}

If you want to be able to look up or prove who you paid, keep `Save recipient address` **on**. Turning it off is the more private choice, and is recommended only if you understand that you are giving up the record.

## Auto generate subaddresses

In privacy settings, you can enable or disable the automatic generation of Monero subaddresses. This feature is enabled by default.

When enabled:

* You can still switch between different accounts.
* For each account, the receive screen displays the first **unused** subaddress after the last manually labeled or last used subaddress.
* Your address book collapses to one entry per account, linked to the latest subaddress for that account.

You can disable this feature in settings. Doing so restores the earlier behavior: you manually label and switch to each subaddress.

## Testnet and stagenet

Cake Wallet doesn't support Monero testnet or stagenet. It only creates, restores and opens Monero wallets on Monero's main network, and there's no setting anywhere in the app to switch a Monero wallet to a test network. Every Monero wallet in Cake Wallet holds real XMR.

The `Use Testnet` switch you may see under `Advanced Settings` when creating or restoring a wallet only appears for Bitcoin and Decred wallets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/cryptos/monero.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
