Circle blocklisted the Zama confidential USDC (cUSDC) contract address on Ethereum on May 30, freezing approximately $12.6 million in user funds. Blockchain investigator ZachXBT first reported the freeze on May 30, raising questions about compliance requirements versus decentralization. Zama stated Circle's compliance system flagged an external depositor's wallet, causing the entire contract to be swept into a standard holding freeze as collateral damage. The incident highlights ongoing tensions between privacy-focused protocols and centralized stablecoin compliance controls in the decentralized finance ecosystem.
Circle Blocklists Zama cUSDC Contract Without Prior Notice
According to ZachXBT, Circle added the Zama cUSDC contract address to its blocklist without prior notice to the Zama team. The affected contract currently holds around $12.6 million worth of USDC. The frozen contract address is publicly listed in Zama's documentation and blockchain explorers. Despite the freeze, no significant outflows have been recorded from the contract since the action was taken. ZachXBT noted that the reason behind the freeze remains unclear. The event quickly became one of the most discussed stories involving Circle this year, especially given previous concerns over the company's ability to freeze assets at the smart contract level. Zama is known for using fully homomorphic encryption (FHE), a privacy technology that allows transaction details to remain encrypted while still being verifiable on-chain.
Zama Attributes Freeze to Flagged External Depositor Wallet
Shortly after reports emerged, Zama provided additional context regarding the incident. According to the team, Circle's compliance system flagged an external wallet that had deposited funds into the cUSDC contract. Because those assets were held within the broader contract, the entire system was swept into a standard holding freeze. Co-founder Rand Hindi confirmed that the team is actively investigating the issue. Zama's legal team is working to isolate the flagged wallet and restore access for unaffected users. In a statement on May 30, Zama clarified: "Circle's compliance system flagged an external depositor's wallet. Because that wallet held funds in the cUSDC contract, the entire contract was swept into a standard holding freeze. This is collateral damage, not a sanction against the Zama Protocol."
ZachXBT Links Frozen Address to Overnight Finance Activity
Further analysis by ZachXBT revealed that the frozen address may have links to funds associated with Overnight Finance. The wallet reportedly participated in a recent governance vote involving treasury allocation discussions. Overnight Finance has previously faced allegations from some community members regarding treasury management and alleged rug pull concerns, although no direct connection has been officially confirmed. ZachXBT highlighted that Patagon Management, a plaintiff involved in civil litigation against Overnight Finance, may have linked the address to Zama during court proceedings. At this stage, the exact relationship between the frozen funds, Overnight Finance, and the blocklist remains unclear.
Incident Exposes Privacy Protocol Vulnerability to Centralized Compliance
The incident creates an important test case for privacy-focused blockchain infrastructure. For developers, the freeze demonstrates how centralized stablecoins can create unexpected risks for decentralized applications. Even when a protocol itself is not under investigation, a single flagged participant may impact an entire contract. For users, the event serves as a reminder that assets backed by centralized issuers remain subject to compliance controls regardless of the underlying technology. The case raises questions about how privacy protocols can design systems that better isolate individual wallets and reduce contract-wide exposure. The crypto community continues to debate whether compliance actions of this scale should come with greater transparency.
FAQ
What did Circle do to Zama's cUSDC contract on May 30?
Circle blocklisted the Zama confidential USDC (cUSDC) contract address on Ethereum on May 30, freezing approximately $12.6 million in user funds without prior notice to the Zama team.
Why did Circle freeze the Zama cUSDC contract?
According to Zama, Circle's compliance system flagged an external depositor's wallet that held funds in the cUSDC contract, causing the entire contract to be swept into a standard holding freeze as collateral damage rather than a direct sanction against Zama Protocol.
What connection does the frozen address have to Overnight Finance?
ZachXBT's analysis revealed the frozen address may have links to funds associated with Overnight Finance, with the wallet reportedly participating in a recent governance vote involving treasury allocation discussions, though no direct connection has been officially confirmed.
