A lesson on pooled collateral from the Zama cUSDC freeze
A court froze funds inside a confidential USDC wrapper then reversed it three days later
On May 30, Circle blacklisted the Ethereum contract behind Zama's confidential USDC, a token called cUSDC. It froze the contract, and the contract held the USDC backing every person who had wrapped into it. On June 1, after a hearing, the court lifted the order. Zama said the court found the freeze unwarranted and the USDC is unfrozen. Start to finish, the episode ran about three days.
It wouldn't be right to see this as a privacy protocol caught in a money dispute. The more useful read starts with what cUSDC actually conceals.
A confidential token is not an anonymous one. cUSDC uses fully homomorphic encryption to hide balances and transfer amounts. It does not hide addresses, and it does not hide the act of transacting. When a user wraps USDC into a confidential ERC-20, the original USDC is deposited into the wrapper contract and an equivalent confidential balance is minted to the user. The wrap step posts the deposit amount in plain text. That is why analysts traced the disputed funds within hours. Rand Hindi, Zama's chief executive, compared the model to HTTPS rather than Tor: it hides the contents of a transaction, not the sender and recipient. The privacy layer did not expose the funds, and it did not freeze them.
Circle was carrying out a court order the same court later found unwarranted. The depositor's funds cleared compliance screening when they arrived. The freeze worked because a confidential ERC-20 wrapper tracks each holder's balance as encrypted state, but the real USDC backing all of those balances is held in the wrapper contract. Blacklist the wrapper address, and every dollar it holds stops moving, whatever encrypted balance it backs.
The freezability came from USDC. The pooling turned a freeze aimed at one depositor into a freeze of all of them. Hindi made the wider point himself: the same thing could happen to any protocol holding freezable assets, including AMMs, lending markets, and bridges.
Holding confidential balances as on-chain ciphertext over pooled collateral is what makes the token composable with other contracts. Keeping each holder's state isolated or off-chain reduces that composability. The same pooling that lets a confidential token behave like a normal on-chain asset is what gives a blacklist a single point to act on. Designs that keep balances in a holder's own account, such as Solana's confidential transfer extension, localize a freeze to the targeted account. A natively issued confidential asset, rather than a wrapper over Circle's USDC, would not inherit Circle's freeze authority at all; the lever would sit with that asset's own issuer instead. It's difficult to make a design decision that does not trade composability, custody, or issuer trust for a smaller freeze surface.
Zama said it will make compliance transitive, so that a confidential token will mirror the actions taken on its underlying asset, and a freeze on a USDC address propagates only to that address's cUSDC. The wrapper still holds all the underlying tokens, but each address has its own confidential balance and can be acted on individually. Zama also said it will stand up a compliance council and integrate know-your-transaction providers. The fix for a pool-wide freeze is to push enforcement down to the account.
The process is worth marking before it is forgotten. A third-party stablecoin issuer was directed, on an ex parte order, to freeze a contract that was not the defendant's. Zama, not a party to the case, said it received no notice before it executed. The order here was reversed through cooperation among the parties, and the plaintiffs had offered to make uninvolved users whole. But that doesn't change the fact that the mechanism worked for those three days.
Any protocol that pools a freezable asset inherits that asset's freeze authority, and the narrow remedy is account-level enforcement rather than pool-level. Zama is building that, which will result in a privacy protocol that can freeze individual balances on an issuer's instruction. That's a requirement for the financial institutions it wants as customers.
