BNB Chain
BNB Chain (chainId 56) is a production deployment of Privacy Pools v2, served by the production ASP and relayer. The core contracts went live on 2026-09-01 (Keystore at block 119401440; the ASP indexes the pool from block 119614738). The core addresses are identical to Ethereum mainnet and Citrea, because the three were deployed deterministically.
Contract addresses
MAX_BATCH() 10, canonical ANNOUNCER()), so batch, stealth, and register-and-relay withdrawals are available.approvedZapList() holds the ppUSDT zap below.transact_1x1 0x1C838Ca4BB05838907E99A3e328e14d87a6859c1 through transact_5x5 0x20D183F61B7a0A0c502d136149a827C811750272), the same verifier addresses as mainnet.Compatibility: SDK, circuits, deployed verifiers, and deployment addresses must all match. Mixing sets produces invalid proofs.
Parameters
Identical to mainnet: rootHistorySize 16, maxStateTreeSize 2^22, keystoreRootLiveness 1200 seconds, maxKeystoreTreeSize 2^18. Not paused at the time of writing.
How each path resolves
Pass the addresses above as config.deployment (the SDK's default table carries Sepolia only), point aspUrl at the production ASP, and take relayer, processor, and yield addresses from the production relayer's /v1/details, which lists this chain as bsc.
The public BNB Chain RPC (bsc-dataseed.binance.org) serves calls but not eth_getLogs at any range, so note discovery on this chain needs an archive-capable provider; the 0xbow frontend treats an Alchemy key as effectively required here.
Tokens
Read the live configuration with Entrypoint.assets(asset) before quoting; the values below were read on 2026-09-22. The vetting fee is 0 bps on every enabled asset. Stablecoins on BNB Chain have 18 decimals.
minAmount 0.02 BNB; maxRelayFee 2 BNB.minAmount 10 shares; maxRelayFee 1200 shares.minAmount 10 FDUSD; maxRelayFee 1200 FDUSD) but not listed by the production relayer, so it can be deposited and self-relayed today but not quoted or relayed through the relayer.Yield deployments
feeBps 2000The router is the relayer's only allowed_processors entry on this chain.
ASP
/public-key (the same production key as mainnet and Citrea).latestASPRoot() and latestIPFSCID() both answer), so attested notes are spendable.Relayer configuration
swapsSupported: true)Read /v1/details at runtime; these values are what the production relayer published on 2026-09-22.
Governance
Roles live on the AccessRouter above; read its RoleGranted and RoleRevoked events from block 119401440 for the current holders. This deployment is not recorded in the monorepo's ChainDeploymentRegistry.
Source: read live from chain and from the production ASP and relayer on 2026-09-22; pinned in the 0xbow frontend's config/prod-deployments.ts.