> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluton.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What stays public

> Operation by operation, what Fluton reveals on-chain and to whom, what it hides, and the known limits of the anonymity it offers.

Fluton hides who paid whom, not that the pool exists. Crossing the pool's boundary is a public act: the circuit needs a plaintext `publicAmount` and `publicAsset`, so a deposit and a withdrawal each name their amount, their token and the format they chose. Everything that happens strictly inside the pool can hide all three. This page is the plain list, so that the guides and the wallet pages do not have to argue it again.

## What is public, and to whom

| Operation | What the chain shows | Who else learns something |
| - | - | - |
| TOKEN deposit | The depositing wallet, the amount, the token, the format chosen (TOKEN). TOKEN balances are public anyway, as for any ERC-20. | The pool logs the screening it spends: depositor and nonce. The screener learns the depositor's address, which the deposit makes public regardless. |
| eTOKEN deposit | The depositing wallet, the amount, the token, the format chosen (eTOKEN). eTOKEN balances, the pool's reserves and any refund stay encrypted. | The same screening log and the same address, for the same reason. |
| Withdrawal | The amount, the token, the format and the recipient address. | The relayer, if one submits it, is the on-chain sender and reads its own fee note, so it knows the token and the fee. |
| Private transfer, self-sent | A pool transaction with its new commitments and ciphertexts, and the wallet that sent it. No amount, no recipient, no token. | Nobody beyond the chain. |
| Private transfer, relayed | A pool transaction with its new commitments and ciphertexts, and the relayer as sender. No amount, no recipient, no token, no sender. | The relayer knows the token and the fee, because it reads its fee note. It logs transaction hashes only. |
| Fee collection | The withdrawal fee rate, and the fees kept per token in `protocolFees`, so what the owner has taken is public. A relayer's fee income shows only when it withdraws it: the total of one token since its last withdrawal. | Nobody. |
| Referral | A deposit's referrer, each referrer's credits and claims, and a referrer's bonus. A withdrawal names no referrer at all. | Nobody. |

An indexer adds nothing to this picture. It is a read-only view of the same public events, so whatever is public on the chain is public to it, and whatever is not is not.

## What is hidden

Amounts inside the pool are never revealed; only the net amount crossing the boundary is. A private transfer shows neither its amount, nor its recipient, nor its token, whether you submit it yourself or a relayer does for you; a relayed one does not show its **sender** either, because the relayer is the on-chain sender and it is paid with a note rather than in public. eTOKEN balances, the pool's reserves, refunds and the amounts of notes are encrypted or shielded throughout.

With and without the relayer, side by side:

| Private transfer | Through the relayer | From the wallet |
| - | - | - |
| Sender's wallet | Hidden, the relayer sends | Visible |
| Token | Not named | Not named |
| Amount, recipient | Hidden | Hidden |

Deposits and withdrawals always name their token, because value enters or leaves the pool in public.

## Known limits

* **A self-sent transfer exposes its sender.** Your wallet visibly interacted with the pool, though nothing links that transaction to the recipient, to any amount or to any token. Submitting through a relayer hides the sender too.
* **A relayed token hides only among the tokens that relayer serves.** The relayer's list is public, so a relayer serving one token effectively names it.
* **Screening is at entry only.** The pool takes the screening signer's verdict on who may deposit, and the pool's owner can only name a different signer. An address flagged after it deposited is already in the anonymity set. If the API or CipherOwl is down, deposits stop and nothing else does.
* **Anyone can refer themselves from a second wallet**, which amounts to a 25% rebate on the withdrawal fee, and up to 55% with the largest bonus the API grants. Credits are public per referrer address, as is the link between a deposit and its referrer.
* **The token list is owner-controlled**: append-only, with no removal.
* **The pool is upgradeable.** The `ProxyAdmin`'s owner can replace the pool's code and with it every rule on this page, including who can withdraw what. The fee cap, the append-only token list and renouncing ownership bind only until an upgrade.

For why the relayer's fee is a note rather than a public payment, see [fees and referrals](https://docs.fluton.io/concepts/fees.md); for what the ciphertexts of a transfer do and do not carry, [private transfers](https://docs.fluton.io/concepts/private-transfers.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.