Circle has frozen $12.6 million worth of USDC stablecoins held in Zama Protocol's system, a move that immediately drew fire from critics who say it shows how a single company can unilaterally seize funds and enforce rules unevenly across the crypto ecosystem.
What Happened
The freeze targeted USDC deposited on Zama Protocol, a DeFi platform. Circle, the issuer of the second-largest stablecoin, confirmed the action but did not provide a specific reason. The company has the technical ability to blacklist wallets and prevent USDC from moving — a feature built into the token's smart contract. That power is rarely used on this scale, making the $12.6 million block stand out.
Criticism Mounts
The incident quickly prompted criticism about unilateral control and selective enforcement in the stablecoin space. Some in the crypto community pointed to the freeze as proof that stablecoins like USDC are not truly decentralized — they rely on a central issuer that can freeze or seize assets at will. Others questioned why Zama Protocol was targeted while other platforms with similar or larger pools of USDC remain untouched. The lack of transparency around Circle's decision-making process only amplified the backlash.
Broader Implications for Stablecoins
The freeze lands at a time when regulators globally are tightening rules around stablecoin issuers. Circle has long positioned itself as a compliant actor, working closely with U.S. authorities. But actions like this one highlight the tension between regulatory compliance and the ethos of permissionless finance that many crypto projects champion. If a stablecoin can be frozen on one platform, what stops it from happening on another? That question now hangs over every DeFi project that relies on USDC.
For now, the $12.6 million remains locked. Zama Protocol has not publicly challenged the freeze, and Circle has not said whether the funds will be released or what conditions might lead to their return. The episode is a reminder that in the current stablecoin system, control ultimately rests with the issuer — not the user.
