Editor’s note (October 30, 2026): This article has been corrected to state what Tether’s and Circle’s published terms assert, rather than describing every holder’s agreement as established fact; to separate Tether’s verified contract mechanics from the legal authority Circle’s terms claim, including the custodied-address scope of that authority; to remove an unqualified statement about court rulings in Conduit Technology v. Tether that the sources on this record do not establish; and to narrow the closing’s investigation-state statements to what the sources cited here support.
The Freeze Playbook: How $2.3B Was Frozen in Hours
When more than $2.3 billion in stablecoins was locked within hours of a security incident becoming public on October 29, the crypto industry witnessed a demonstration of power that was both swift. Tether froze $1.567 billion in USDT, while Circle locked more than $800 million in USDC. This was not an emergency response requiring new, ad-hoc powers. It was the execution of powers each issuer’s published documents claim: Circle’s USDC Terms state that “by obtaining and using USDC, you understand and expressly agree to these Terms,” while Tether’s terms – as laid out in published terms commentary – let the company freeze tokens in its “sole discretion.” Those are claims inside the issuers’ own documents, not a court’s finding. On October 29, they moved more than $2.3 billion in hours.
While Forkast’s October 29 incident report detailed the immediate impact of these freezes, the mechanics behind them reveal a reality that stablecoin holders, treasury desks, and exchange operators must now treat as a live variable: the speed of a freeze is determined by issuer discretion, not a court clock.
The Authority: Terms of Service
The ability to halt billions of dollars in value rests on legal frameworks established long before this incident. Tether’s Terms of Service (commentary) explicitly permit the company to freeze any tokens held by a user if law requires it, if the holder breaches terms, or if Tether, in its “sole discretion,” determines it is prudent to do so. The text does not require a court order to initiate a freeze, and it allows for blacklisting addresses and reporting to authorities without prior notice to the holder. This “sole-discretion” clause is currently being contested in US federal court, such as in the case of Conduit Technology v. Tether.
Circle’s USDC Terms, specifically Section 13, provide similar authority. Circle may block addresses and freeze assets, either temporarily or permanently, in its sole discretion if it determines the activity is associated with illegal acts or terms violations – a power the terms scope to “certain USDC addresses and, if such addresses are Circle custodied addresses, freeze associated USDC.” While Circle may also act under a valid government legal order, the terms provide the company with the latitude to act independently.
The Mechanics: How a Freeze Executes
On-chain, a freeze is not an abstract concept; it is a technical operation – and the two issuers do not reach it the same way. Tether’s USDT operates as a contract on networks like Ethereum and TRON, and that contract carries a blacklist function, addBlackList, which can be called only by Tether’s owner multisig – a security setup requiring multiple signatures to authorize a transaction. When Tether calls it, the target address is immediately restricted: it can no longer send or receive USDT. That is contract behavior. Circle’s USDC rests on a different class of authority: its own terms reserve the right to block “certain USDC addresses and, if such addresses are Circle custodied addresses, freeze associated USDC” temporarily or permanently in its sole discretion – a power written into a legal document, not a shared function with Tether, and one the terms scope to Circle-custodied addresses rather than describe as universal on-chain enforcement. The two paths converge where a holder feels them: a frozen balance is not destroyed – it stays visible on the blockchain, but it is rendered inert. Burning the funds, which would remove them from circulation, is a separate, subsequent step.
Divergent Postures, Same Result
The incident highlights a notable tension between the stated postures of the two issuers. Tether’s own reporting indicates it has supported more than 2,300 cases globally and frozen over $4.4 billion in assets. In April 2026, for example, Tether coordinated with OFAC and US law enforcement to freeze more than $344 million in USDT across two TRON addresses.
Circle, conversely, has historically emphasized a more cautious approach. CEO Jeremy Allaire stated in April 2026 that Circle does not freeze USDC without a formal legal basis and would not act in real time during active hacks. Yet, in this instance, both issuers moved within hours. This suggests that when the scale or nature of an incident reaches a certain threshold, the practical response may converge regardless of the issuer’s stated preference for court-ordered processes.
Precedent and Risk
This is not the first time these mechanisms have been deployed. In August 2022, both issuers froze balances associated with Tornado Cash addresses after they were added to the OFAC SDN list (the U.S. Treasury’s Office of Foreign Assets Control Specially Designated Nationals list, which identifies individuals and entities subject to economic sanctions). Other instances include a $57 million USDC freeze linked to LIBRA memecoin litigation in 2025 and a 2026 SDNY court order that froze USDC across 16 business wallets. On-chain investigator ZachXBT has estimated that over $420 million in stolen funds escaped recovery across 15 incidents since 2022, partly due to delays in freezing, underscoring why the speed of these actions is so closely watched.
For the market, the takeaway is clear: freeze risk is now a primary consideration. Whether you are a treasury desk managing liquidity or a holder moving assets, the ability of an issuer to lock your balance in hours is a reality of the current stablecoin architecture. Binance paused withdrawals on multiple networks as a precaution after the incident, as Forkast reported on October 29; the cause of the incident has not been established in the sources cited here. The “freeze playbook” needs no post-mortem to be a proven, high-speed tool.