A stablecoin freeze is an on-chain control action targeting an address or token account. Its effect depends on the exact token and network. Eagle Virtual's covered freeze-and-seizure series begins in 2018. Recorded completed-year counts rose through 2025; the 2026 count is year to date and is not a completed-year comparison. This article separates what an on-chain action proves from the context supplied by primary company and government sources. Browse covered blacklist events for the latest data.

The Early Years: 2018–2019

Eagle Virtual's earliest covered restriction record is in 2018. Across covered tokens, the 2018 aggregate contains one restriction and one seizure action. Those early counts are small compared with later completed years. The chain records identify the action and target, but do not by themselves identify a hack, scam, exchange incident, or other reason.

These early actions demonstrate that the contract control was used, rather than merely present in the code. The exact effect follows the deployment's blacklist functionality and should not be generalized to a different token or network.

Circle's USDC, launched in 2018, also included blacklist functionality, and covered on-chain records show use of that control. The action count does not explain Circle's internal decision or public posture. For a detailed comparison of how the two issuers differ, see Tether vs Circle: Comparing Freeze Policies.

Company Statements About Security Incidents

Issuers have attributed selected control actions to security incidents in public statements. Those statements can supply context that is not encoded in a contract log or network-native instruction. The on-chain record alone should not be labeled as a hack response.

When reviewing a claimed incident response, compare the company's announcement with the dated on-chain action and the exact token deployment. A transfer or control action on one network does not automatically propagate across a cross-chain bridge or to another deployment.

There is no universal issuer response time. Public announcements may describe selected cases, but they do not establish a standard turnaround for other requests or incidents.

The Tornado Cash Sanctions Response

The August 2022 OFAC designation of Tornado Cash was followed by Circle control actions involving USDC at listed addresses. Tether publicly stated that it would wait for law-enforcement instruction rather than mirror the listed addresses automatically. The primary references are Treasury's August 8, 2022 designation, Tether's public response, and Treasury's March 21, 2025 delisting.

The government designation and each issuer's control records are separate sources. Treasury's list establishes the official sanctions action. A token-contract record establishes the issuer action. Tether's statement supplies the company's description of its own response.

These records show different public responses by Circle and Tether. They do not establish a broad motive or decision rule for every later action. A restriction on one token deployment also does not automatically change control state for a different token or network.

The designation was challenged in litigation. Treasury later removed the Tornado Cash addresses from its sanctions list on March 21, 2025. That chronology should not be converted into a causal claim about why Treasury delisted the addresses without a primary source making that connection.

Tether's Announced $225M Action

Tether has published selected statements describing cooperation with law-enforcement agencies. Those statements provide company-attributed context for particular actions; the on-chain record alone does not identify which agency, request, or investigation was involved.

In late 2023, Tether announced it had frozen approximately $225 million in USDT as part of an investigation that the company described as involving an international human-trafficking and “pig-butchering” syndicate in Southeast Asia. Tether said the action followed an investigation with OKX and the US Department of Justice. Tether described the case in its initial announcement and a later Tether statement describing DOJ acknowledgment of its cooperation.

This is a source-attributed case, not a basis for assigning the same reason to other on-chain actions. There is no universal published response time for issuer requests.

Freeze patterns by year

Freezes and seizures by year. The current year is marked as year to date and carries no bar.

YearFreezesSeizuresTotal actions
2018112
20198715
2020242113355
2021360203563
20221,3334351,768
20231,8041081,912
20244,2672934,560
202511,45370212,155
2026 (year to date)15,18847915,667

Dated by when each action happened on-chain (UTC). Bars scale to the largest completed year.

The table reports covered actions, not their cause. Counts can change as new actions occur and as token or network coverage changes. The 2026 row is year to date; it should not be compared with a completed year without accounting for the shorter period.

The network coverage also changes over time. Early covered records are on Ethereum. Covered USDT and USDC deployments now span Ethereum, TRON, Arbitrum, Optimism, Base, Solana, Sonic, HyperEVM, Avalanche, and Celo, and covered control actions appear across this network set. Each token deployment has its own control state and mechanics. An action on one network does not automatically propagate to another.

The Destruction of Frozen Funds

Certain reviewed Tether contracts let the administrator permanently destroy the entire token balance held at a currently blocked address. This burns the token units and reduces supply; it does not transfer them to Tether, law enforcement, or another wallet.

A burn is recorded on-chain. Its public record establishes the action, target, amount, and time, but it does not by itself establish the private rationale or legal process behind the action. This burn function is not the control mechanic on every USDT deployment.

A reversible freeze or restriction should not be described as permanent: the authorized controller may later remove it. A balance already burned cannot be restored merely by removing the restriction.

Lessons for Stablecoin Users

These cases show why the exact token and network matter. A control record establishes an action, not a verdict about a person or the issuer's private reason. Interaction with a restricted address does not automatically give another address the same direct status. Current and historical direct status should be stated only where the source record supports it.

For compliance work, check the source, covered deployment, and freshness before relying on a result. Eagle Virtual's source-backed direct screening reports covered current or historical direct status with the exact token and network, supporting source, and data timestamp.

Frequently Asked Questions

What is a stablecoin freeze?

A stablecoin freeze is an on-chain control action targeting an address or token account. Its effect depends on the exact token and network. The record establishes that an action occurred; it does not by itself establish the reason or wrongdoing. Some deployments expose a separate function that can burn the full balance of a currently blocked address.

Can Tether freeze my USDT?

Tether has controls on covered USDT deployments, but their effect is network-specific. On reviewed Ethereum, TRON, Avalanche, and Celo deployments, a restricted address cannot send USDT but can still receive it. On Solana, a frozen USDT token account cannot receive, transfer, or burn until thawed. Eagle Virtual's covered stablecoin-control series begins in 2018.

How quickly can stablecoins be frozen?

There is no universal issuer response time. Once a valid on-chain action is confirmed or finalized, that deployment enforces its control. Time before submission depends on the company and circumstances.

What happens to frozen stablecoin funds?

The effect depends on the token and network. Some reviewed Tether contracts let the administrator burn the entire balance of a currently blocked address, reducing supply rather than transferring those units. A frozen Solana USDT token account cannot receive, transfer, or burn until thawed. Removing a restriction restores permitted transfers only for any balance that remains.

How can I check whether a wallet has a direct stablecoin blacklist status?

Eagle Virtual records covered blacklist actions and preserves current or historical direct status where the record supports it. Results identify the supported token and network and show source and freshness information. An interaction with a restricted address does not automatically give another address the same direct status.

Primary Sources

Related Reading

Access Full Freeze Data

Explore the recorded stablecoin blacklist actions across the networks Eagle Virtual covers.

View Blacklist Events