# Pools and denominations

Each TONado Cash pool is uniquely identified by **three things**:

* The **asset**: either native TON or a specific TEP-74 Jetton.
* The **denomination**: a single fixed amount; the pool only accepts deposits of exactly this amount.
* The **network**: testnet or mainnet.

A withdrawal from a pool can only be linked to *deposits from the same pool*. Different denominations are different anonymity sets.

## Why fixed denominations

If the pool accepted any amount, the deposit amount itself would identify your withdrawal. ("Someone deposited 1.382 TON, and three days later someone withdrew 1.382 TON. Guess who.")

Fixed denominations force every deposit into the same shape, so the only thing distinguishing one deposit from another is *who made it*. The anonymity set is everyone who made a deposit and hasn't yet withdrawn.

## Which pools exist

The authoritative list lives in [`packages/core/src/deployments.ts`](https://github.com/tonadocash/monorepo/blob/main/packages/core/src/deployments.ts). You can also query it at the CLI:

```bash
tonado pools list --network testnet
```

Or via the relayer's REST API:

```bash
curl http://localhost:8090/pools
```

### Testnet (current)

| Asset | Denomination | Address                |
| ----- | ------------ | ---------------------- |
| TON   | 1 TON        | (see `deployments.ts`) |
| TON   | 10 TON       | (see `deployments.ts`) |

### Mainnet (planned)

Mainnet pools are gated on the [mainnet launch plan](/operations/mainnet-launch-plan.md): external audit + multi-party trusted setup + bug bounty. Once those gates are passed, the planned initial denominations are **1 TON and 10 TON**. Additional Jetton pools may be added per community demand.

## How to choose a denomination

Two tradeoffs:

1. **Larger denomination = smaller anonymity set.** Most users go for smaller pools, so there are more deposits, so the anonymity set is bigger. Fewer people deposit 10 TON than 1 TON. If you have a large amount to mix, consider splitting it across multiple smaller deposits, at the cost of a slightly more complex withdrawal flow.
2. **Larger denomination = relatively smaller fee.** Relayers typically charge a percentage with a floor. For a 1 TON pool with a 0.05 TON floor, you're paying 5% of the deposit. For a 10 TON pool with the same floor, you're paying 0.5%. The percentage component (e.g., 0.5%) is the same regardless of pool size.

The 1-TON pool is the right default for most users. Use 10-TON if you specifically need it and the anonymity set is comparable.

## Splitting a large amount

If you have, say, 12 TON to deposit, you have two options:

* **One 10-TON deposit and two 1-TON deposits.** Three notes, three withdrawals later. Each withdrawal mixes with its respective pool. Highest anonymity, slightly more bookkeeping.
* **Twelve 1-TON deposits.** Twelve notes. Even higher anonymity from the same pool. Significantly more bookkeeping.

Many small deposits at slightly varied times look the same as many independent users; one huge deposit looks like a whale and is harder to mix into.

## Adding a new pool

The protocol supports new pools without contract changes. Deploying a new denomination just requires running [`pnpm deploy:pool`](/for-developers/deploying-pools.md) with the new parameters and updating `deployments.ts`. See [Deploying pools](/for-developers/deploying-pools.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tonadocash.com/using-tonado-cash/pools-and-denominations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.