Crypto Security & Privacy How Privacy Pools Balance On-Chain Privacy and Compliance Owen Gaines Owen Gaines is a professional poker player and author who has played an estimated ten million hands and written four poker strategy books. November 20, 2026 Privacy Pools are smart contract protocols that let users deposit funds into a shared pool and later withdraw to an unrelated address, while proving that their deposit belongs to a set of deposits considered legitimate. The design responds to a specific problem: earlier mixing protocols offered privacy but no way to separate honest users from illicit funds, which made every withdrawal suspect and drew regulatory action. For crypto poker players, the relevant question is not whether Privacy Pools make funds untraceable. They don’t. It is how much linkability they actually remove, what they cost in security and smart contract risk, and how regulated operators and exchanges treat funds that have passed through them. This guide explains the mechanics behind shared pools and zero-knowledge withdrawals, how association sets work, where chain analysis still applies, and the compliance trade-offs any cryptocurrency user should understand before interacting with one. The Problem Privacy Pools Were Designed to Solve Public blockchains record every transfer permanently. On Ethereum, where Privacy Pools first launched, an address’s full balance and history are visible to anyone who knows it. Paying someone once can expose your entire financial activity to them. Earlier mixers broke the link between deposit and withdrawal addresses, but treated all deposits identically. Honest users and stolen funds shared one anonymity set, so no withdrawal could demonstrate clean origins. One prominent mixer was sanctioned by the U.S. Treasury in 2022, a designation later lifted after litigation, and exchanges widely flagged any funds with mixer exposure. Privacy Pools, based on a 2023 research paper co-authored by Vitalik Buterin and academic collaborators, add a second proof to each withdrawal: membership in an association set that excludes deposits flagged as illicit. The aim is privacy from the public combined with a verifiable claim about the funds’ origin. How Privacy Pools Work The protocol has three components: a shared deposit contract, zero-knowledge withdrawal proofs, and association sets maintained by a provider. Deposits and Commitments When you deposit, your wallet generates two secrets locally and submits a commitment, a hash of those secrets, to the contract. The commitment is added to a Merkle tree containing every deposit in the pool. The deposit transaction is public and shows your address and amount; the secrets never leave your device. Zero-Knowledge Withdrawals To withdraw, you generate a zk-SNARK proof showing that you know the secrets behind some commitment in the tree, without revealing which one. You also publish a nullifier, derived from one of the secrets, which the contract records to prevent the same deposit from being withdrawn twice. The withdrawal address has no on-chain link to the deposit address. Association Sets The withdrawal proof also shows that your commitment belongs to an association set, a subset of deposits approved by an Association Set Provider (ASP). The ASP screens deposits and excludes those tied to known illicit activity. Deposits that are not approved cannot withdraw privately; implementations typically allow them to exit publicly back to the original address. This is the core of the compliance design: a private withdrawal carries proof that it did not come from an excluded deposit. What This Means for Players Privacy Pools reduce public linkability between two addresses you control. They do not change your relationship with regulated counterparties, and they introduce risks of their own. Factor What Privacy Pools Do What They Don’t Do On-chain linkability Break the direct link between deposit and withdrawal addresses Hide the deposit itself or the withdrawal itself Origin of funds Prove membership in an approved association set Guarantee every exchange or operator accepts that proof Identity Reduce what the public can infer Remove KYC records held by exchanges or operators Anonymity level Depends on pool size and user behavior Provide a fixed or guaranteed level of privacy Custody Funds are controlled by your secrets Protect you if the secrets or the contract fail Many exchanges and payment operators screen incoming funds for exposure to privacy protocols. Some accept association-set proofs, some request source-of-funds documentation, and some reject such funds outright. Players should check an operator’s terms before depositing funds that passed through any privacy protocol, and should never use one to avoid identity verification or anti-money-laundering controls. Common Mistakes Players Make Withdrawing the exact deposited amount shortly after depositing, which makes the pair trivial to match Funding the withdrawal address’s gas from the deposit address, recreating the link the pool removed Losing the locally stored deposit secrets, which makes the funds permanently unrecoverable Assuming a privacy pool withdrawal will be accepted everywhere, then facing delays or rejection at an exchange Treating the pool as storage, leaving funds exposed to smart contract risk longer than necessary Where Chain Analysis Still Works Anonymity Set Size Your privacy is bounded by how many deposits your withdrawal could plausibly match. A pool with thousands of active deposits provides far more cover than one with a few dozen. The association set narrows this further: if the approved set is small, so is your effective anonymity set. Amount and Timing Correlation Unusual deposit amounts and short gaps between deposit and withdrawal are the most common ways users de-anonymize themselves. Analysts match withdrawals to deposits by size and time window. Waiting longer and withdrawing in common denominations reduces this risk but does not eliminate it. Entry and Exit Points If you deposit from an address funded at a KYC exchange and withdraw to another address that later deposits to a KYC exchange, both ends are tied to your identity. The pool hides the path between them from the public, not from institutions that already know both endpoints. Scenario: A Withdrawal That Wasn’t Private A player deposits ETH into a Privacy Pool and later moves funds toward an exchange account. Deposit: an uncommon amount with several decimal places Pool activity: a small number of deposits in the preceding days Withdrawal: the same amount, under an hour later, to a fresh address Gas for the fresh address funded from the original deposit address The Technical Process The zero-knowledge proof is valid and reveals nothing cryptographically. But an observer sees one deposit and one withdrawal of the identical unusual amount within an hour, in a pool with little other activity, plus a direct gas transfer between the two addresses. Matching them takes seconds. When the fresh address later deposits to an exchange, the exchange’s screening flags privacy protocol exposure and requests source-of-funds information. The Outcome The player gained no meaningful privacy and incurred a compliance review. Because the player kept records of the original deposit and the association-set proof, the review was resolved, but with a delay. The cryptography worked as designed; the operational choices defeated it. How Professionals Approach Privacy Protocols Experienced players treat privacy protocols as a specialized tool with legal and operational costs, not a default step. Many conclude that basic wallet hygiene, fresh addresses and separate wallets by purpose, meets their actual privacy needs without the added risk. Technical Risk Management Those who do use Privacy Pools back up deposit secrets as carefully as a seed phrase, use only audited contracts, limit the amount and duration of exposure, and keep complete records of deposits, withdrawals, and association-set proofs for compliance and tax purposes. System Optimization They confirm in advance that the destination exchange or operator accepts such funds, use relayers or separately sourced gas so withdrawal addresses aren’t linked by funding, and route poker payouts and deposits through simple, documented paths rather than privacy protocols. Technical Evolution in Compliant Privacy The direction of on-chain privacy is toward selective disclosure: systems where users keep transaction details private from the public while proving specific facts to specific parties. Association sets are one approach. View keys, which let a user share transaction details with an auditor or exchange, are another. Comparable ideas are being explored beyond Ethereum, including in the Bitcoin ecosystem. For poker players, the practical takeaway is stable: address-based deposits and withdrawals through the ACR Poker software are simplest to document, and any privacy tool should be evaluated against the operator’s terms and local law before use, not after. Frequently Asked Questions What is a Privacy Pool? A Privacy Pool is a smart contract where users deposit funds and later withdraw to a different address using a zero-knowledge proof. The proof shows the withdrawal comes from a valid deposit without revealing which one, and also that the deposit belongs to an association set that excludes funds flagged as illicit. Do Privacy Pools make transactions anonymous? No. They break the direct on-chain link between a deposit address and a withdrawal address, but deposits and withdrawals remain public. Small anonymity sets, matching amounts, short timing gaps, and KYC records at exchanges can all link activity. Privacy Pools reduce public linkability; they do not provide anonymity. What is an association set? An association set is a list of deposits approved by an Association Set Provider, which screens deposits and excludes those tied to known illicit activity. A private withdrawal must prove its deposit is in the set. Deposits that are excluded generally can only exit publicly, back to the address they came from. Will exchanges and poker operators accept funds from a Privacy Pool? Policies vary. Some accept association-set proofs, some request source-of-funds documentation, and some reject funds with any privacy protocol exposure. Check the operator’s or exchange’s terms before sending such funds, keep full records, and never use a privacy protocol to avoid identity verification or anti-money-laundering controls. What happens if I lose my deposit secrets? The secrets generated at deposit are required to create a withdrawal proof. If they are lost, the funds cannot be withdrawn by anyone and are effectively lost permanently. Back up deposit secrets with the same care as a seed phrase, and keep funds in the pool only as long as necessary. Are Privacy Pools legal? Legality depends on jurisdiction and can change. Privacy Pools were designed with compliance features, but regulators and platforms treat privacy protocols differently, and earlier mixers faced sanctions. Review local law and platform terms before use, and seek independent legal advice if you are unsure. This article is for educational purposes only and does not constitute legal, tax, or financial advice. Privacy protocols involve smart contract risk, including the possibility of total loss of funds, and their legal status varies by jurisdiction and may change. Blockchain transactions are pseudonymous, not anonymous, and no protocol guarantees privacy. Any use must comply with applicable laws and platform terms, including identity verification and anti-money-laundering requirements. Seek independent legal and financial advice before interacting with privacy protocols, and play within your bankroll limits.