Can a Stablecoin Be Frozen? What the Contracts Allow

The standard does not include freezing

Start with what the token standard actually specifies. The ERC-20 standard, EIP-20, defines six functions - total supply, balance lookup, transfer, transfer from, approve and allowance - and two events. Reading the specification end to end turns up no occurrence of “freeze”, “blacklist”, “pause” or “block” in any form.

So freezing is not something ERC-20 tokens do. It is something a specific token’s contract adds on top of the standard, and the safest way to know whether a given token can do it is to read that contract’s interface.

That matters for a practical reason: the answer is not uniform across stablecoins. It is a property of each contract, and it is verifiable rather than a matter of trust. Both contracts below are verified on Ethereum, so the function list that follows is read from the published interface rather than from documentation describing it.

What USDC’s contract can do

The USDC contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 is a proxy. Its implementation, read on 2026-10-15, is named FiatTokenV2_2, compiled with Solidity 0.6.12, and its verified interface declares these functions alongside the standard ERC-20 set:

Three observations follow from reading that list rather than a summary of it.

Blocking and pausing are different powers with different scopes. blacklist targets one address. pause stops transfers for the whole contract, which affects every holder, not just the blocked one.

The powers are separated by role. The interface does not expose a single administrator. Blocking, pausing, minting and ownership each have their own role and their own reassignment function. That is a design choice with a real consequence: an account holding the blacklister role cannot mint, and an account holding the pauser role does not need the owner key to halt the token.

The contract can also burn. burn is present in the interface, which means balances can be destroyed rather than merely frozen.

What USDT’s contract can do

USDT at 0xdAC17F958D2ee523a2206206994597C13D831ec7 is a different design. The verified contract read on the same date is named TetherToken, compiled with Solidity 0.4.18, and its interface declares:

The structural contrast with USDC is the point of the section:

• The powers are concentrated. There is a single owner and no separate blacklister, pauser or minter roles in the interface. Whoever holds the owner key holds all of these capabilities.
• Blocking is paired with destruction. USDT’s interface includes both addBlackList and destroyBlackFunds, and the second one’s name describes what it does to the balance of an address that has been blocked. A frozen USDC balance and a destroyed USDT balance are not the same outcome for the holder.
• There is a fee parameter. basisPointsRate and maximumFee sit in the interface, a vestige of a transfer-fee mechanism that has no equivalent in the USDC interface.
• There is a redirection path. deprecate and upgradedAddress allow the contract to point at a successor, which is a different mechanism from USDC’s proxy pattern.

What the issuers’ terms say

The contracts establish what is technically possible. The terms establish what the issuer says it may do, and on this question both documents are unusually direct.

Circle, on USDC. The USDC Terms contain a section headed “Blocked Addresses & Forfeited Funds”. It states that Circle “reserves the right to ‘block’ certain USDC addresses and, if such addresses are Circle custodied addresses, freeze associated USDC (temporarily or permanently) that it determines, in its sole discretion, may be associated with illegal activity or activity that otherwise violates these Terms.”

The same section addresses what happens to people who are not the blocked party: “In the event that you send USDC to a Blocked Address, or receive USDC from a Blocked Address, Circle may freeze such USDC and take steps to terminate your USDC Account.”

It goes further on the consequence: “In certain circumstances, Circle may deem it necessary to report such suspected illegal activity to applicable law enforcement agencies and you may forfeit any rights associated with your USDC, including the ability to redeem USDC for USD.”

And it addresses orders from outside: “Circle may also be required to freeze USDC and/or surrender associated USD held in Segregated Accounts in the event it receives a legal order from a valid government authority requiring it to do so.”

A separate section, “Blocklisting”, states that USDC “is issued and redeemed in accordance with Circle’s blocklisting policy” and that Circle “reserves the right to block the transfer of USDC to and from an address on chain as permitted under the blocklisting policy.”

Tether, on USDT. Tether’s terms describe a comparable power. They state that Tether “may suspend or terminate your access to the Site or any of the Services, freeze any Tether Tokens held by you, or terminate your Tether Token Wallet, as required by applicable Law or where Tether, in its sole discretion, determines it is prudent to do so.”

Where Tether suspects a prohibited use, the terms describe a menu of sanctions: making a report to any government or law enforcement authority “without providing any notice to you about any such report”; “freezing or confiscation of any Fiat, funds, property, proceeds, Tether Tokens or any Digital Tokens”; “blacklisting any Digital Tokens Address which holds Tether Tokens”; and suspending access.

The terms then add: “Tether may, at its sole and absolute discretion, seize and deliver your property to any applicable Government, law enforcement, or other authorities where circumstances warrant or in accordance with Laws.”

Two further details in the same document are worth knowing for anyone checking the entity behind the token. Tether’s terms state that Tether International Limited has redomiciled from the British Virgin Islands to the Republic of El Salvador and is now named Tether International, S.A. de C.V., and that the terms are governed by the laws of the British Virgin Islands. The terms also describe authorisation as a stablecoin issuer and digital asset service provider under El Salvador’s regulations for stablecoin public offerings, subject to that country’s National Commission of Digital Assets.

What this means if you hold either token

Putting the code and the paperwork together produces a short list of things that are true rather than alarming.

• Both tokens can be blocked, and both issuers say so. This is not a discovery about a hidden capability. It is a documented feature of the contracts and a reserved right in the terms.
• Being the counterparty is enough to be affected. Circle’s terms explicitly cover USDC sent to or received from a blocked address. The risk is not confined to whoever the blocklist names.
• The two tokens differ in what freezing can turn into. USDC’s interface includes burn; USDT’s includes destroyBlackFunds, whose name describes removal rather than suspension.
• A blocklist check is a read, not a transaction. Anyone can query it. That is a difference from almost every other risk in a portfolio, which usually has to be inferred.
• Centralisation is not a side effect here; it is the product. A dollar token that can be redeemed with the issuer is a claim on that issuer, and the ability to block is part of how an issuer is expected to operate. Whether that is acceptable is a judgment about the asset, not a defect to be found.

How to check the contract state yourself

Everything above describes interfaces and terms. Current state - which addresses are blocked, and which role holders are active - changes, and the way to read it is from the chain rather than from an article.

1. Open the contract on a block explorer and look at the “Read contract” tab. Both contracts are verified, which is what makes the function names legible.
2. Read the role accessors. blacklister(), pauser(), masterMinter(), owner() on USDC; owner() on USDT. These return the addresses currently holding each power, and they can change.
3. Read the blocklist status for an address with isBlacklisted(address) on USDC or isBlackListed(address) and getBlackListStatus(address) on USDT.
4. Watch for a pause. paused() returns the contract-wide state. A paused token is a different situation from a blocked address, and it affects everyone holding it.

One limit on this article should be stated plainly: the function lists above come from the verified interfaces of both contracts as read on 2026-10-15, but the current holders of those roles were not read while writing this, and no count of blocked addresses is given, because a number of that kind goes stale within days and cannot be verified from a document. Both are readable at the two explorer links in the sources below.

For how the two tokens differ in other respects, see how USDT and USDC differ. For what the reserve reports behind them do and do not establish, see what a reserve attestation does and does not prove, and for what happens at the point of redemption, see stablecoin redemption and network compatibility.

Risk note. This article describes what two published contracts include and what two issuers’ published terms state. It is not a statement that any particular address has been or will be blocked, and no view is expressed on whether these powers are exercised appropriately. The contracts and the terms can both change, and a token can be blocked or destroyed while you hold it, which is a total loss of that balance. Nothing here is investment advice.