Risk exposure

USDT and USDC frozen addresses

Tether and Circle can freeze an address inside their token contracts. CompliAPI reads the contracts' freeze and release events every 15 minutes and screens against the addresses frozen right now. Matches are risk exposure — flagged, with the freezing transaction attached — never sanctions hits.

Publisher
CompliAPI on-chain crawl
List type
Risk exposure
Refresh
Every 15 minutes (on-chain crawl)
API list slugs
usdt_frozenusdc_frozen
Official source
USDT and USDC token contract events (Ethereum, TRON)
Download
Full list as CSV or JSON on paid plans. Screening single values is free.

About this list

The two largest dollar stablecoins are issued by companies that keep an administrative control in the token contract: a list of addresses that may no longer move the token. Tether's USDT contracts reject transfers sent from a listed address and let Tether destroy its balance; Circle's USDC contract blocks a listed address from sending and receiving. The issuers use the control after hacks and scams, at the request of law enforcement and to enforce sanctions.

The chain records that an address was frozen, when, and by which transaction — not why. So CompliAPI classes these lists as risk exposure rather than sanctions: a match sets flagged and leaves sanctioned false, the same treatment as the Tornado Cash association lists. For a payments or exchange business the signal is practical as well as reputational, because funds paid to a frozen address cannot be moved on.

There are two lists. usdt_frozen holds the addresses Tether has frozen on Ethereum, TRON, Arbitrum, Polygon and Avalanche; usdc_frozen holds the addresses Circle has frozen on Ethereum, Arbitrum, Base, Optimism, Polygon and Avalanche. An issuer freezes per network, so an address frozen on several networks returns one match for each, naming its network. Solana and the other chains the two tokens run on, and other stablecoins, are not covered.

What CompliAPI extracts

  • Addresses frozen by Tether (USDT) on Ethereum, TRON, Arbitrum, Polygon and Avalanche
  • Addresses frozen by Circle (USDC) on Ethereum, Arbitrum, Base, Optimism, Polygon and Avalanche

How CompliAPI handles it

  1. Read from the contracts' own events

    Each freeze and release is an event the token contract emits: AddedBlackList and RemovedBlackList on USDT (BlockPlaced and BlockReleased on Tether's newer contracts), Blacklisted and UnBlacklisted on USDC. The crawl reads them from Ethereum, Arbitrum, Base, Optimism, Polygon and Avalanche over JSON-RPC and from TRON through TronGrid's contract-events API, back to each contract's first freeze.

  2. Releases are tracked, not just freezes

    Issuers release addresses, so the events are applied in chain order and the last one decides: a released address stops matching and is recorded as delisted with the on-chain release time, and a re-frozen one is restored. Screening only ever sees addresses frozen now.

  3. Evidence and dates from the chain

    Every record carries the issuer, token, network, the block time of the freeze and the freezing transaction, linked on that network's block explorer. The crawl stays a safety margin behind the chain head and resumes from a stored position per contract.

Screen against this list

Every /screen endpoint checks all enabled lists by default and names the list behind each match. Add the ?lists= filter to restrict a request to this source.

GET /api/v1/screen/crypto/{address}?lists=usdt_frozen,usdc_frozen

curl "https://api.compliapi.com/api/v1/screen/crypto/0x1a2b3c4d5e6f708192a3b4c5d6e7f80912a3b4c5?lists=usdt_frozen,usdc_frozen" \
  -H "Authorization: Bearer $COMPLIAPI_TOKEN"

Response

{
  "value": "0x1a2b3c4d5e6f708192a3b4c5d6e7f80912a3b4c5",
  "flagged": false,
  "sanctioned": false,
  "lists_checked": ["usdt_frozen", "usdc_frozen"],
  "matches": []
}

Frequently asked questions

Does a stablecoin freeze match mean the address is sanctioned?

No. A freeze is the issuer's own action and the chain does not record its reason, so matches carry list_type "risk" and set only flagged — sanctioned stays false. An address that is also on a sanctions list returns a separate match from that list.

What puts an address on usdt_frozen or usdc_frozen?

A freeze event from the token contract: AddedBlackList on Tether's USDT contracts on Ethereum and TRON, BlockPlaced on Tether's newer contracts on Arbitrum, Polygon and Avalanche, or Blacklisted on Circle's USDC contracts. Every record links the transaction that emitted it.

What happens when an issuer releases a frozen address?

The release event (RemovedBlackList, BlockReleased or UnBlacklisted) takes the address off the list at the next 15-minute crawl. It stops matching in screening, is recorded as delisted with the on-chain release time, and a monitored address triggers a delisted alert.

How current is the stablecoin freeze data?

The crawl runs every 15 minutes and stays a short safety margin behind the chain head — 12 blocks on Ethereum, a few minutes of blocks on the faster networks and about ten minutes on TRON — so a new freeze is normally screened within half an hour.

Does the list cover USDT and USDC on every chain?

No. It covers USDT on Ethereum, TRON, Arbitrum, Polygon and Avalanche, and USDC on Ethereum, Arbitrum, Base, Optimism, Polygon and Avalanche. The issuers deploy on other chains too — Solana among them — and freezes there are not in these lists.

Related

Screen against Stablecoin freezes data

Get a free API key and make your first request in minutes — every screen checks all enabled lists in one call.

Free tier: 1,000 requests a month. No credit card required.

CompliAPI provides data and tools that support compliance workflows. It does not provide legal advice, and organizations should determine their obligations with qualified counsel.