Glossary

Stablecoin Blacklist (Freeze Function)

The ability of centralized stablecoin issuers to freeze or blacklist specific addresses, preventing them from transacting.

Key Takeaways

  • Stablecoin blacklists are smart contract functions that allow issuers like Circle (USDC) and Tether (USDT) to freeze specific addresses, preventing them from sending, receiving, or burning tokens.
  • Freeze powers have been used to comply with OFAC sanctions, assist law enforcement investigations, and recover stolen funds: Tether alone has frozen over $5 billion across nearly 10,000 addresses since the feature was introduced.
  • The existence of centralized freeze functions raises fundamental questions about censorship resistance and self-custody, driving interest in architecturally different approaches like Bitcoin-native stablecoins.

What Is a Stablecoin Blacklist?

A stablecoin blacklist (also called a freeze function) is a mechanism built into a stablecoin's smart contract that gives the issuer the power to block specific addresses from transacting. When an address is blacklisted, it cannot send, receive, or redeem the stablecoin: the tokens in that wallet are effectively frozen in place.

Every major fiat-backed stablecoin includes this capability. It exists primarily for regulatory compliance: stablecoin issuers operating under U.S. law must comply with sanctions enforced by the Office of Foreign Assets Control (OFAC) and cooperate with law enforcement. The 2025 GENIUS Act formally codified this requirement, mandating that all permitted stablecoin issuers maintain the technical ability to "seize, freeze, or burn" tokens on lawful orders.

While freeze functions serve legitimate compliance purposes, they also represent a single point of centralized control over what are otherwise permissionless digital assets. This tension sits at the heart of ongoing debates about stablecoin design and regulatory frameworks.

How It Works

Stablecoin freeze functions are implemented at the smart contract level. Every transfer operation checks whether the sender or recipient is on the blacklist before executing. If either address is flagged, the transaction reverts.

USDC: Blacklistable.sol

Circle's USDC contract uses a dedicated Blacklistable module with a role-based access pattern. A designated "blacklister" address (separate from the contract owner) can add or remove addresses from the blacklist:

// Simplified from Circle's Blacklistable.sol
mapping(address => bool) internal blacklisted;

modifier notBlacklisted(address _account) {
    require(!blacklisted[_account], "Blacklistable: account is blacklisted");
    _;
}

function blacklist(address _account) external onlyBlacklister {
    blacklisted[_account] = true;
    emit Blacklisted(_account);
}

function unBlacklist(address _account) external onlyBlacklister {
    blacklisted[_account] = false;
    emit UnBlacklisted(_account);
}

// The notBlacklisted modifier is applied to transfer(), transferFrom(),
// mint(), and burn() functions

In the FiatTokenV2.2 upgrade, Circle introduced a gas optimization that packs the blacklist flag and balance into a single uint256 storage slot per account. Bit 255 stores the blacklist flag, while bits 0 through 254 store the balance. This reduced gas costs for USDC transfers by saving a storage read on every transaction.

USDT: AddedBlackList and DestroyBlackFunds

Tether's USDT contract takes a more aggressive approach. Beyond simply freezing an address, Tether can permanently destroy the tokens held by a blacklisted address:

// Simplified from Tether's TetherToken.sol
mapping(address => bool) public isBlackListed;

function addBlackList(address _evilUser) public onlyOwner {
    isBlackListed[_evilUser] = true;
    emit AddedBlackList(_evilUser);
}

function destroyBlackFunds(address _blackListedUser) public onlyOwner {
    require(isBlackListed[_blackListedUser]);
    uint dirtyFunds = balanceOf(_blackListedUser);
    balances[_blackListedUser] = 0;
    _totalSupply -= dirtyFunds;
    emit DestroyedBlackFunds(_blackListedUser, dirtyFunds);
}

This "freeze, burn, and reissue" model lets Tether permanently remove tainted tokens from circulation and mint replacements to victim or law enforcement wallets. In 2025 alone, Tether destroyed approximately $698 million in USDT from blacklisted addresses.

The Freeze Process

When a stablecoin issuer decides to freeze an address, the typical process follows these steps:

  1. A trigger event occurs: OFAC adds an address to the Specially Designated Nationals (SDN) list, law enforcement submits a request, or the issuer detects illicit activity
  2. The issuer's compliance team reviews the request and verifies the address
  3. The blacklister (USDC) or contract owner (USDT) calls the freeze function on-chain
  4. The transaction is confirmed, and the address can no longer transact with the token
  5. All subsequent transfer attempts involving that address revert automatically

Scale and Notable Freezes

The scale of stablecoin freezing has grown significantly since these features were first used. As of early 2026, Tether has blacklisted nearly 10,000 addresses with over $5 billion in frozen value. Circle has blacklisted approximately 370 addresses with around $109 million frozen: a far smaller footprint reflecting different compliance philosophies.

Tornado Cash Sanctions (August 2022)

The most significant test of stablecoin freeze powers came when OFAC sanctioned Tornado Cash, an Ethereum privacy mixer, citing $7 billion in laundered funds including $455 million by North Korea's Lazarus Group. OFAC designated 53 Ethereum addresses, and Circle froze approximately $75,000 in USDC held in those wallets. Tether notably declined to freeze Tornado Cash addresses at the time, calling such action potentially "reckless."

The sanctions were eventually lifted in March 2025 after a federal court ruled that immutable smart contracts cannot be classified as "property" under the International Emergency Economic Powers Act (IEEPA).

Iran-Linked Freezes ($344 Million, 2024-2026)

In one of the largest single freeze events, Tether froze $344 million in USDT across two addresses linked to Iran's Central Bank and the IRGC-Qods Force. The wallets had received approximately $370 million across roughly 1,000 transactions since 2021. This action was part of "Operation Economic Fury," a U.S. campaign targeting Iranian cryptocurrency flows.

The Drift Protocol Debate (April 2026)

A $286 million exploit of Solana-based Drift Protocol, attributed to North Korean hackers, exposed tensions in freeze-power design. Circle took over six hours to freeze approximately $232 million in stolen USDC, with CEO Jeremy Allaire stating that freezes require court orders or law enforcement direction. The delay allowed significant funds to escape, prompting a class-action lawsuit and renewed debate over whether stablecoin issuers should have the ability (or obligation) to freeze proactively during active exploits.

Regulatory Framework

Freeze capabilities are no longer just a voluntary compliance tool: they are increasingly mandated by law.

  • The GENIUS Act (signed July 2025) requires all U.S. permitted payment stablecoin issuers to maintain the technical capability to seize, freeze, or burn tokens on lawful orders and subjects them to the Bank Secrecy Act
  • OFAC lists cryptocurrency addresses directly on the SDN list, and U.S. persons (including stablecoin issuers) are legally prohibited from processing transactions involving those addresses
  • The EU's MiCA framework grants regulators the power to freeze stablecoin funds during reserve investigations, with full enforcement beginning July 2026
  • In April 2026, FinCEN and OFAC issued a joint proposed rule implementing GENIUS Act requirements for stablecoin issuers' anti-money laundering and sanctions compliance programs

Implications for Censorship Resistance

The existence of freeze functions creates a fundamental tension in stablecoin design. On one hand, these powers have demonstrably aided law enforcement: Tether reports supporting over 2,300 law enforcement cases globally and recovering billions in stolen or illicit funds. On the other hand, a single entity's ability to unilaterally freeze assets contradicts the permissionless ethos that underpins cryptocurrency.

Several concerns arise from centralized freeze powers:

  • Jurisdictional overreach: freeze powers extend globally, meaning a U.S. regulatory action can immobilize funds held by users in any country
  • False positives: addresses can be frozen due to associations with sanctioned entities, even if the address owner is not the target
  • No due process: freezing typically occurs before any judicial review, and unfreezing requires cooperation from the issuer
  • Composability risk: in DeFi protocols, frozen stablecoins in liquidity pools or collateral positions can cascade into broader systemic issues

Why It Matters: Bitcoin-Native Alternatives

The centralized freeze model of EVM-based stablecoins has driven interest in architecturally different approaches. Bitcoin-native stablecoins built on protocols like Spark offer a different trust model.

On Spark, tokens exist as TTXOs (Token Transaction Outputs) within a UTXO-like structure rather than as balances in a smart contract mapping. Issuers can optionally implement freeze capabilities, but the protocol itself does not require them. Critically, even if an issuer freezes a token, users retain self-custody of their Bitcoin and can perform a unilateral exit to Bitcoin L1: a guarantee that EVM-based stablecoins cannot provide.

This design separates two concerns that are entangled in EVM stablecoins: compliance tooling (which issuers may need for regulatory reasons) and custodial control (which users should never lose). Whether a stablecoin can be frozen is a policy question; whether a user can always exit with their underlying Bitcoin is an architectural one.

Risks and Considerations

  • Counterparty risk: holding any stablecoin with a freeze function means trusting that the issuer will only use that power legitimately and will process unfreeze requests fairly
  • Regulatory uncertainty: as regulations like the GENIUS Act and MiCA evolve, the scope and frequency of freezes may expand, potentially affecting more users
  • Speed tradeoffs: the Drift Protocol incident showed that both slow and fast freezes carry risks: slow responses let hackers escape, while preemptive freezes risk harming innocent users
  • Network concentration: the majority of Tether freezes (over 84% of addresses) occur on TRON, suggesting that network choice affects freeze exposure
  • No guaranteed recourse: unlike traditional banking, where deposit insurance and established legal frameworks protect account holders, frozen stablecoin holders have limited and inconsistent paths to recovery

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.