What can go wrong

The honest list, including the parts that are your problem and not the program's.

You lose your receipt

The deposit stays in the pool forever. Nobody can recover it. This is the most likely way to lose money here.

You give yourself away at the edges

Withdraw a minute after depositing and the timing pairs the two. Withdraw into the wallet you deposited from and you have done the work for the observer. The pool hides the link; it cannot hide behaviour.

The crowd is too small

Privacy here is arithmetic: your withdrawal could have come from any deposit of the same size still in the pool. If that is four deposits, it is a weak claim. Early users are the most exposed, and the pool is worth less when it is new — which is the opposite of what a launch wants to tell you.

The set-up is compromised

If the proving key is generated by one party, that party can forge proofs and empty the pool, and nothing on the chain would look wrong. A proper multi-party ceremony is the fix, and it has not been run yet.

The program has a bug

Zero-knowledge code is difficult and unforgiving; a subtle circuit mistake can mean free withdrawals. This is why an audit stands between devnet and mainnet, and why nothing here should hold money you cannot lose.

Your own machine

The receipt is drawn in your browser. A compromised browser, a malicious extension or a screenshot in the wrong place reads it at the moment it is made. Nothing on the chain can protect a secret you have already leaked.

The rules where you live

Privacy tools are treated very differently from one country to the next, and the way you use one can matter more than the tool. Work that out for yourself; this page is a description, not advice.