Deployments
Privacy Pools v2 runs in production on three chains, served by one production ASP (https://api-v2.0xbow.io) and one multi-chain production relayer. Sepolia remains the development environment on the dev ASP and is the only chain in the SDK's default DEPLOYMENTS table.
- Ethereum mainnet (chainId 1): ETH plus three Aave yield shares (ppUSDC, ppUSDT, ppETH); swaps supported.
- BNB Chain (chainId 56): BNB, FDUSD, and the ppUSDT yield share; swaps supported.
- Citrea (chainId 4114): cBTC only; no swaps, no yield, and no ASP root published yet.
- Sepolia (testnet)
One address set, three chains
The production contracts were deployed deterministically on 2026-09-01, so the core addresses are the same on all three chains:
What differs per chain is the asset configuration, the yield deployments, and whether the ASP has published a root; each chain page lists those. The monorepo's ChainDeploymentRegistry does not yet record these production addresses, so the deploy script's registries cannot be used as a source for them; the 0xbow frontend pins the same set in config/prod-deployments.ts.
Whatever the chain, take relayer, processor, and yield-router addresses from the relayer's /v1/details rather than hand-copying them, and keep your SDK, circuit artifacts, deployed verifiers, and addresses on one matching set; see Relaying.