Skip to main content
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

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: 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; for what the ciphertexts of a transfer do and do not carry, private transfers.