Internet Computer

ZachXBT

American Bitcoin

USDC

Read

<p><strong>ZachXBT says Circle froze 16 legitimate wallets for a civil case, turning a compliance action into a digital property rights fight over who really controls USDC when working business wallets are caught in the net.</strong></p>
<div>
 <p><strong>TLDR Keypoints</strong></p>
 <ul>
  <li><a href="https://x.com/zachxbt/status/2036472308467224839" rel="noopener noreferrer nofollow">On March 24, 2026</a>, ZachXBT said a basic onchain review showed the frozen addresses were operational wallets, not obviously idle stash addresses.</li>
  <li><a href="https://www.circle.com/legal/usdc-terms" rel="noopener noreferrer nofollow">Circle's USDC Terms</a> say the issuer can block addresses and freeze associated balances, while <a href="https://cointelegraph.com/news/zachxbt-claims-circle-wrongfully-freezing-exchange-wallets" rel="noopener noreferrer nofollow">Cointelegraph's March 26, 2026 update</a> said one wallet was later unfrozen.</li>
  <li><a href="https://forum.dfinity.org/t/ckbridge-ethereum-address-blacklisted-by-circle-usdc-withdrawals-failing/65773" rel="noopener noreferrer nofollow">A March 25, 2026 ckBridge incident report</a> showed how a blacklist can disrupt live withdrawals, while the sharper allegation that Circle missed <a href="https://www.theblock.co/post/396296/blockchain-sleuth-zachxbt-accuses-circle-slow-usdc-freezes-420-million-illicit-funds" rel="noopener noreferrer nofollow">more than $420 million across 15 exploit cases</a> remains unconfirmed.</li>
 </ul>
</div>
<h2 id="what-zachxbt-actually-alleged">What ZachXBT actually alleged</h2>
<p>In his March 24, 2026 post, ZachXBT asked why Circle had frozen those wallets for a civil case and said a basic onchain review made it obvious they were operational addresses. Cointelegraph later reported on March 25, 2026 that he argued the sealed New York case gave Circle no basis to freeze all of those business addresses.</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>
<p>Cointelegraph reported that the affected wallets were tied to operating businesses, including crypto exchanges, online casinos and foreign exchange firms. That description matters because it frames the incident as a potential false-positive freeze on active commercial infrastructure, not a takedown of obviously tainted holding wallets.</p>
<p>In its March 26, 2026 update, Cointelegraph said one wallet had already been unfrozen and identified it as Goated, a Solana-based crypto casino platform. That change suggests the facts were still moving even as the accusation spread across crypto X.</p>
<h2 id="why-this-hits-a-nerve-for-usdc-holders">Why this hits a nerve for USDC holders</h2>
<p>Circle's USDC Terms say the company may block certain addresses, freeze associated USDC and may be required to do so after a valid government legal order. The backlash exists because that clause confirms USDC can be switched off at the issuer layer even when the wallet in question looks like ordinary business infrastructure onchain.</p>
<p>The risk tradeoff is the same one compliance teams always face: move too aggressively and you can freeze legitimate users; move too slowly and you can miss bad actors. In this case, the dispute rests on Cointelegraph's business-wallet characterization and Circle's own freeze language, not on a public court filing that outsiders can review line by line.</p>
<p>That tension fits the broader compliance infrastructure debate more than a treasury story like <a href="https://nftenex.com/american-bitcoin-tops-7000-btc-after-nasdaq-debut/" rel="noopener noreferrer nofollow">American Bitcoin Tops 7,000 BTC After Nasdaq Debut</a>. It also sits near the regulatory plumbing questions raised in <a href="https://nftenex.com/mica-deadline-decoded-why-july-1-wasnt-the-main-cutoff-for-most-crypto-service-providers/" rel="noopener noreferrer nofollow">MiCA Deadline Decoded: Why July 1 Wasn't the Main Cutoff for Most Crypto Service Providers</a>, because the core issue here is issuer discretion over access.</p>
<p>The cultural reaction followed quickly. Mert argued that centrally issued stablecoins are not really cash-like bearer assets because they can be frozen at the issuer level.</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="ckbridge-offers-a-concrete-collateral-damage-example">ckBridge offers a concrete collateral-damage example</h2>
<p>In a March 25, 2026 DFINITY forum post, contributors said Circle blacklisted the ckBridge Ethereum minter address 0xb25eA1D493B49a1DeD42aC5B1208cC618f9A9B80, which caused USDC withdrawals from Internet Computer to Ethereum to fail with the message "Blacklistable: account is blacklisted."</p>
<p>That report matters because it shows how a blacklist action against infrastructure can spill past the flagged address and break a live bridge path for ordinary users. Readers tracking other access-risk stories, including <a href="https://nftenex.com/human-error-tops-hacking-as-main-cause-of-crypto-access-loss-oobit-survey-finds/" rel="noopener noreferrer nofollow">Human Error Tops Hacking as Main Cause of Crypto Access Loss, Oobit Survey Finds</a>, will recognize the same operational truth: access can disappear through control systems as well as through theft.</p>
<h2 id="what-still-needs-to-be-proved">What still needs to be proved</h2>
<p>The most explosive version of the story remains the least substantiated one. The claim that Circle missed more than $420 million across 15 exploit cases came from later unconfirmed reporting citing ZachXBT, and that evidence was not independently verified in the source material available at publication.</p>
<p>What would move the story from accusation to conclusion is straightforward: a public response from Circle, wallet-by-wallet evidence for the broader freeze set, or access to the sealed civil filing ZachXBT referenced on X. Until then, the strongest sourced picture is narrower: a prominent onchain investigator says Circle froze business wallets, Circle's terms confirm it has the power to do that, and the reported unfreeze shows the initial sweep may not have been final.</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 decisions.</p><a href="https://nftenex.com/?p=6756" rel="noopener noreferrer nofollow">Read original article on nftenex.com</a>

USDC Freeze Controversy: ZachXBT Says Circle Froze 16 Legit Wallets

Table of Contents

NFTENEX

Other articles published on Apr 4, 2026

Join our free newsletter for daily crypto updates!