Drift

Kevin

ZachXBT

USDC

Read

<p><strong>The USDC freeze controversy widened after blockchain investigator ZachXBT said Circle froze 16 wallets that appeared to be legitimate operational accounts, then failed to act with similar speed during a later hack-related flow. The dispute matters beyond one civil case because it raises new questions about how much trust users should place in issuer-controlled stablecoin freezes when enforcement appears precise in one moment and absent in another.</strong></p>
<p>In a <a href="https://x.com/zachxbt/status/2036472308467224839" rel="noopener noreferrer nofollow">March 24, 2026, post on X about 16 unrelated hot wallets</a>, ZachXBT asked why Circle had frozen USDC balances tied to what he said was a civil case and argued that a basic onchain review showed the addresses were operational wallets rather than obvious hack wallets or dormant shells.</p>
<figure>
 <div>
  Disputed Wallet Freeze Count
 </div>
 <div>
  16
 </div>
 <figcaption>
  ZachXBT alleged that Circle froze 16 unrelated hot wallets in connection with a civil case. Source: ZachXBT on X
 </figcaption>
</figure>
<p>That allegation is still narrower than the headline rhetoric around "legitimate wallets." The available reporting says the underlying U.S. civil case was sealed, and no public explanation from Circle appeared in the fetched source set, which means the legal basis for freezing the addresses could not be independently reviewed from court documents in this run.</p>
<p>ZachXBT's post is the core primary evidence because it frames the controversy as an accuracy problem, not as a claim that stablecoin issuers lack freeze authority in every circumstance.</p>
<blockquote class="twitter-tweet">
 <p>How come Circle froze the USDC balance of 16 unrelated hot wallets late yesterday for a civil case?<br><br>A basic review of onchain activity makes it obvious they are operational wallets.<br><br>You fail to protect users during actual incidents yet respond to a request riddled with errors… <a href="https://t.co/lSPCnIA1xK" rel="noopener noreferrer nofollow">pic.twitter.com/lSPCnIA1xK</a></p>— ZachXBT (@zachxbt) <a href="https://twitter.com/zachxbt/status/2036472308467224839?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">March 24, 2026</a>
</blockquote>
<h2 id="circle-s-freeze-power-is-documented-but-the-disputed-use-is-not">Circle's freeze power is documented, but the disputed use is not</h2>
<p>Circle's own <a href="https://developers.circle.com/wallets/asynchronous-states-and-statuses" rel="noopener noreferrer nofollow">developer documentation on denylist behavior</a> says a sender or recipient can be added to the token contract's denylist, producing the error "Blacklistable: account is blacklisted." That matters because the current dispute is not about whether Circle can freeze USDC, but whether it used that control accurately in this case.</p>
<p>The gap between documented power and documented explanation is central here. Circle's docs show that denylisting exists at the token-contract level, yet the public record available for this story does not show why the freeze reportedly swept up what ZachXBT described as unrelated business wallets.</p>
<h2 id="why-the-missed-real-hacks-comparison-is-driving-the-backlash">Why the "missed real hacks" comparison is driving the backlash</h2>
<p>The criticism escalated because it did not stay limited to the freeze itself. <a href="https://unchainedcrypto.com/circle-faces-backlash-for-failing-to-freeze-stolen-usdc-during-285-million-drift-exploit-unchained/" rel="noopener noreferrer nofollow">Unchained reported on April 2, 2026</a> that the attacker in the April 1, 2026, Drift exploit moved tens of millions of dollars in USDC from Solana to Ethereum through Circle's Cross-Chain Transfer Protocol over several hours without intervention.</p>
<p><a href="https://www.elliptic.co/blog/drift-protocol-exploited-for-286-million-in-suspected-dprk-linked-attack" rel="noopener noreferrer nofollow">Elliptic's security analysis put the exploit at $286 million</a> and said the attacker mostly swapped the stolen assets into USDC before bridging them to Ethereum. That data point is why ZachXBT's comparison resonates: the allegation is not simply that Circle froze the wrong wallets, but that it allegedly acted faster on a flawed civil request than on a major exploit involving a comparable compliance lever.</p>
<p>The timeline also shifted after the first burst of criticism. <a href="https://cointelegraph.com/news/zachxbt-claims-circle-wrongfully-freezing-exchange-wallets" rel="noopener noreferrer nofollow">Cointelegraph said in a March 26, 2026, update</a> that Circle had unfroze one of the 16 wallets, which added weight to the argument that at least part of the original freeze action may have been overly broad.</p>
<p>Industry reaction widened the issue from one civil-case dispute to the broader question of whether users can treat centrally issued stablecoins as neutral infrastructure once a freeze request reaches the issuer.</p>
<blockquote class="twitter-tweet">
 <p>this is your 10th reminder that centrally issued stablecoins are not actually yours <br><br>they can be frozen, unlike cash <a href="https://t.co/KpBw8PnLc1" rel="noopener noreferrer nofollow">https://t.co/KpBw8PnLc1</a></p>— mert (@mert) <a href="https://twitter.com/mert/status/2036777040947401193?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">March 25, 2026</a>
</blockquote>
<h2 id="what-the-episode-means-for-usdc-trust-and-market-integrity">What the episode means for USDC trust and market integrity</h2>
<p>The combination of ZachXBT's claim about 16 frozen wallets, Unchained's report that tens of millions of dollars in USDC kept moving during the Drift exploit, and Elliptic's $286 million estimate is what turns this into a trust story rather than a routine compliance dispute. If the same issuer can freeze ordinary operational wallets quickly but miss hack-linked flows for hours, users are left judging not just policy, but enforcement accuracy.</p>
<p>That trust question lands in a market already sensitive to credibility and risk narratives, whether traders are parsing institutional flow signals in <a rel="noopener noreferrer nofollow">BTC ETFs Logged $22.6M Inflows in Just 4 Trading Days</a> or broader macro stress in <a rel="noopener noreferrer nofollow">Oil Prices Top $111 as US-Iran Conflict Raises Crypto Risk</a>. For USDC users, the practical issue is simpler: centrally managed dollars can be frozen, and the market will scrutinize how consistently that power is applied.</p>
<p>None of the fetched material shows Circle publicly denying the freeze, explaining the sweep across the wallets, or laying out why the March action and the Drift response looked so different. Until that record is clearer, the strongest defensible version of the story is that a documented compliance power collided with an opaque factual basis and a highly visible comparison to a separate exploit response.</p>
<h2 id="what-readers-should-watch-next">What readers should watch next</h2>
<p>The next concrete questions are whether Circle publishes a public explanation, whether more of the wallets are later released after review, and whether any court filing from the sealed case becomes public enough to test ZachXBT's description against the legal record. The March freeze controversy is now partly a transparency issue because the compliance action is visible onchain, while the rationale behind it is not.</p>
<p>The policy backdrop also matters because centralized dollar rails are already under closer scrutiny across crypto and traditional finance, including in debates that overlap with upcoming events such as <a rel="noopener noreferrer nofollow">Kevin Warsh Fed hearing set for April 16</a>. If Circle or the parties behind the civil request release more detail, the market will have a clearer basis for deciding whether this was a necessary intervention or an avoidable compliance failure.</p>
<h2 id="faq-usdc-freeze-controversy-and-the-zachxbt-claims">FAQ: USDC Freeze Controversy and the ZachXBT Claims</h2>
<p><strong>What did ZachXBT claim?</strong></p>
<p>According to ZachXBT's March 24, 2026, post, Circle froze the USDC balances of 16 unrelated hot wallets tied to a civil case, even though he said a basic onchain review showed they were operational wallets. That is an allegation from ZachXBT, not a court-tested conclusion from the sealed case.</p>
<p><strong>Why does the "missed real hacks" point matter?</strong></p>
<p>It matters because Unchained's April 2 report said tens of millions of dollars in USDC moved through CCTP during the Drift exploit, while Elliptic estimated the attack at $286 million. Those figures give critics a specific benchmark for arguing that response priorities looked inconsistent.</p>
<p><strong>Has Circle confirmed or explained the freeze?</strong></p>
<p>Not in the source set used for this run. The public material available here includes Circle's documentation on denylist mechanics and outside reporting that one wallet was later unfrozen on March 26, 2026, but it does not include a public explanation from Circle for why the broader freeze was executed as reported.</p>
<p>Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making any investment decisions.</p><a href="https://trustscrypto.com/?p=4786" rel="noopener noreferrer nofollow">Read original article on trustscrypto.com</a>

USDC Freeze Controversy: ZachXBT Alleges Circle Froze 16 Legit Wallets

Table of Contents

TrustsCrypto

Other articles published on Apr 4, 2026

Join our free newsletter for daily crypto updates!