Concepts
Deposits and approval
Why deposits wait
A shielded pool that accepts anything becomes a laundering tool, and that hurts every honest user's anonymity set and legal footing. Batin borrows the approach of Privacy Pools: an association set provider (ASP) decides which deposits join the pool, and a depositor who is never admitted can always leave with their money (Spec §7.2).
States
| State | Meaning | Who moves it |
|---|---|---|
| Pending | Funds are in the vault; the two output commitments are recorded but not in the tree, so they can't be spent | Created by shield |
| Approved | Commitments inserted into the tree; the note is spendable | Only the ASP poster (approve) |
| Refunded | Funds returned to the depositor | Only the depositor (refund) |
Approved and refunded are terminal. The ASP poster can't move funds, change outputs, or block a refund. The depositor can refund a pending deposit at any moment.
On testnet
The testnet ASP approves every deposit. The app asks for approval right after a deposit lands: it calls the approval service with the deposit id and its two commitments, and the service checks the on-chain record before approving. A daily sweep approves anything left pending (for example, if a phone lost its connection). The testnet ASP poster is 0x0D95…6D6c, the deployer.
To try a refund, tick Don't ask for approval yet under testnet options when depositing, then refund from Activity.
What a deposit reveals
Everything about the deposit itself: the depositor address, the asset, the exact amount and the time. The pending record also ties the depositor to the two output commitments. What it doesn't reveal is what happens to those notes afterwards.
Source: apps/web/content/docs/deposits-and-approval.md