|=[ PRIVACY POOLS :: FOR BUILDERS ]=
INTEGRATE PRIVACY POOLS.
DEPOSIT · SIGN · WITHDRAWThe Privacy Pools protocol is mostly public; contracts, circuits, relayer, and SDK. Plug deposits and withdrawals into your own app using a simplified kit, an AI markdown, or the official SDK.
HOW TO INTEGRATE
Three different ways.
SIMPLIFIED KIT — EPT-PRIVACY-POOLS
A minimal, self-contained integration kit: deposit, one-signature accounts, gasless withdraw, plus a basic browser tool to try the whole flow yourself. No API keys, no hosted services.
AI MARKDOWN
One markdown file written for a coding agent: contract addresses, the deposit and withdrawal flows, the pitfalls, and a working code sketch. Paste it to your AI and let it wire the integration.
THE NATIVE SDK
0xbow's own stack: @0xbow/privacy-pools-core-sdk on npm, full docs, and the Apache-2.0 monorepo with contracts, circuits and relayer.
One wallet signature derives the Privacy Pools account on the client. Deposits re-derive from the same wallet, and a note export covers the rest. You can back up the deposit by downloading a note.
precommitment = Poseidon(nullifier, secret) → Entrypoint.deposit() with the amount. The note is a non-secret pointer: scope + index.
The ASP screens the deposit and publishes an updated approved-set root. There is no ETA, I love you.
Fetch the approved set, build the inclusion proofs, groth16 in the browser, submit through a relayer. The recipient pays no gas and shows no link.
THE PITFALLS
ASP approval has no ETA. The relayer's signed fee commitment lives about 20 seconds, so proving and submission are one step, not two. Reconstructing accounts needs event logs, so you'll need to use an RPC or subgraph. Proving artifacts need to be downloaded once (~20MB).
Integrating Privacy Pools but not sure it fits? Talk to Ben.
TALK TO BEN →