> 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/zano.md).

# Zano

Zano support is being removed from Cake Wallet. Covers Zano addresses and aliases, BIP39 and 26-word seeds, fee levels, and Confidential Assets.

Official Website: [zano.org](https://zano.org/)

Zano is an open-source cryptocurrency and ecosystem with enterprise-grade privacy, security, and scalability that operates as a robust foundation for confidential assets and decentralised applications (dApps).

{% hint style="warning" %}
**Zano support is being removed from Cake Wallet.** While we have loved supporting Zano, it has undergone multiple hard forks, including one that rolled back the chain 30 days to resolve a critical bug, leading to a very high maintenance burden for our team without much usage. As a result, Zano will be removed from Cake Wallet in a future release so that we can prioritize other assets and features that have a larger impact overall. Since v6.5.0, new Zano wallets can no longer be created or restored; existing Zano wallets keep working for now, so back up your seed from `Recovery & Keys`.
{% endhint %}

Cake Wallet shows a "Support for Zano will soon be removed" notice listing your Zano wallets, and shows it again each time you open a Zano wallet.

## Addresses

In Cake Wallet's Zano wallet, there is only one address per wallet, which is standard for the Zano ecosystem. Keep in mind that this will have lesser privacy compared to some other assets, where new addresses are automatically generated.

Your Zano address will start with `ZxD` followed by a series of alphanumeric characters.

When sending, Cake Wallet also accepts a Zano **alias** in place of an address — a short handle beginning with `@`, such as `@alice`. Aliases are registered on the Zano network and resolve to a normal Zano address.

![Zano receive screen in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/zano_01_receive.png)

## Seed Format

Zano wallets created in Cake Wallet v6.4.3 or later use a standard BIP39 seed (12 or 24 words, with an optional seed passphrase); wallets created earlier use the original 26-word native Zano seed. You'll need whichever seed your wallet shows under `Recovery & Keys` to restore it in another Zano wallet.

## Fee Levels

Transaction fees are a necessary part of sending Zano or Confidential Assets.

Cake Wallet lets you choose a fee level for each transaction under `Advanced Settings` → `Fees`. Zano offers five levels, in this order:

* **Slow**
* **Automatic** — the default, and what we recommend
* **Medium**
* **Fast**
* **Fastest**

We recommend leaving it on `Automatic`, which balances speed and cost based on current network conditions. Higher fee levels confirm faster but cost more; lower levels are cheaper but can take longer to confirm.

## Confidential Assets

Cake Wallet's Zano wallet can store Confidential Assets in addition to ZANO. To add a Confidential Asset, open the `Assets` tab on your home screen, tap the `Tokens` button, then tap the `+` to add a token. Any existing Confidential Assets owned by the wallet will automatically be shown on the home screen.

![Managing Zano Confidential Assets in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/zano_02_assets_hl.png)


---

# 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/zano.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.
