destroyBlackFunds is a function on the USDT smart contract that lets Tether permanently burn the USDT balance held at a previously blacklisted address, decrementing the total token supply on that chain. Unlike addBlackList, which only blocks an address from moving its USDT, destroyBlackFunds is irreversible at that address: the specific tokens are gone, and there is no on-chain path to recover them. But "destroyed" does not always mean "lost to the victim." In the recovery flow, Tether commonly pairs the burn with a fresh mint of equivalent USDT to a court-designated or victim address, so the tokens are gone while the value is not (per Tether's Token Recovery policy).
In 2025, this function did more work than most explainer content acknowledges. Across Ethereum and Tron that year, Tether blacklisted roughly $1.26 billion in USDT and burned roughly $698 million via destroyBlackFunds. That is a same-period flow ratio of about 55.6% of freeze value to destroy value, per BlockSec's 2025 USDT blacklist analysis. Note: this is a same-period ratio, not a cohort survival rate; some 2025 destroys apply to addresses first blacklisted in 2023-2024, and some 2025 freezes will only be destroyed in later years. The directional takeaway holds: a large share of blacklisted USDT does progress to permanent burn, and often to a reissue. The narrower claim ("55.6% of 2025-blacklisted USDT was destroyed in 2025") is not what the data supports.
This guide is the code-level walkthrough of that mechanic: the exact function on the USDT contract, who can call it, when Tether uses destroy versus a plain freeze, the burn-and-reissue victim-recovery pattern, the notable 2026 destroy events, and how researchers and journalists should frame destroy volume when reporting on it.
Companion spoke: for the
removeBlackList(unfreeze) side of the mechanic, the three paths a legitimate owner can pursue, realistic odds, and the on-chain playbook, see How to Unfreeze a USDT Address. For the full compliance context, see the pillar USDT Freeze: The Complete 2026 Guide.
destroyBlackFunds: the burn function
destroyBlackFunds(address) is the third function in the USDT contract's three-function enforcement set, the other two being addBlackList (the freeze) and removeBlackList (the unfreeze). It is the only one of the three that changes the target's USDT balance and the total token supply on-chain.
The actual code from the deployed USDT contract
Here is the relevant snippet from the deployed Ethereum USDT contract at 0xdAC17F958D2ee523a2206206994597C13D831ec7 (pragma solidity ^0.4.17, so event emission uses the pre-0.4.21 syntax: the function name alone, no emit keyword):
function addBlackList (address _evilUser) public onlyOwner {
isBlackListed[_evilUser] = true;
AddedBlackList(_evilUser);
}
function removeBlackList (address _clearedUser) public onlyOwner {
isBlackListed[_clearedUser] = false;
RemovedBlackList(_clearedUser);
}
function destroyBlackFunds (address _blackListedUser) public onlyOwner {
require(isBlackListed[_blackListedUser]);
uint dirtyFunds = balanceOf(_blackListedUser);
balances[_blackListedUser] = 0;
_totalSupply -= dirtyFunds;
DestroyedBlackFunds(_blackListedUser, dirtyFunds);
}Five lines of Solidity encode the entire destroy mechanic: verify the address is blacklisted, read its balance into a local variable named dirtyFunds, zero out the balance, decrement _totalSupply, and emit an event.
The require: destroy can only follow a freeze
require(isBlackListed[_blackListedUser]) is the guard in the deployed contract. If the target address is not already blacklisted, the transaction reverts. Destroy always follows a freeze, every destroy event on-chain has a precursor freeze event, both publicly indexable in order via the BlockSec USDT Freeze Tracker.
The event, and the two non-reversible effects
Every successful destroy call emits DestroyedBlackFunds(_blackListedUser, dirtyFunds), indexed by Etherscan, Tronscan, and the BlockSec USDT Freeze Tracker. Two on-chain effects are non-reversible: the target address's balances mapping is zeroed (no undoDestroy function exists), and _totalSupply is permanently decremented by the burned amount. Tether can compensate the value via a fresh mint elsewhere (see the burn-and-reissue section and Tether's Token Recovery policy), but the original tokens and supply-slot are gone.
For contrast with the sister functions (all three visible in the deployed contract source): addBlackList only flips the isBlackListed boolean and blocks transfers; balance untouched. removeBlackList clears the flag and restores transferability; again, balance untouched. Only destroyBlackFunds changes the balance and the total supply.
Who can call destroyBlackFunds
destroyBlackFunds is an onlyOwner function on both the Ethereum USDT contract and the TRC-20 USDT contract on Tron at TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. The owner is not a single hot key. It is a multisig address controlled by Tether Ltd., with a delay period between transaction proposal and execution.
No external actor can trigger a destroy at the contract layer (the onlyOwner modifier in the deployed source is the enforcement point). Not a court, not a regulator, not an exchange, not a DAO, not another issuer. When a court order for civil forfeiture arrives, the sequence is: court order → Tether compliance receives + internally validates (per the Tether Token Recovery process) → Tether's multisig proposes and executes the destroy → the on-chain event lands. Tether is the actor of record on-chain even when a government agency is the underlying authority.
The multisig delay is public information. Anyone watching Tether's owner-multisig activity can see a proposed destroy before it executes. The delay-window issue that lets a subset of freeze targets move their USDT before a freeze lands is a freeze-side concern, not a destroy-side concern: by the time a destroy is proposed, the target's isBlackListed flag is already true, so the tokens are already immobilized.
The same three-function set exists on the TRC-20 contract with equivalent owner-only controls. Tron dominates USDT destroy volume in 2026 (typically 85-97% of activity by both count and value in a given week, per the BlockSec USDT Freeze Report Archive), but the mechanic is identical: same guard, same event structure, same _totalSupply decrement.
When Tether uses destroy vs just freeze
Tether uses addBlackList alone (freeze, no destroy) when the situation is under active investigation. Tether uses destroyBlackFunds when the case has resolved into a formal disposition: a court order for civil forfeiture, an OFAC designation with an implied disposition path, or a Tether-verified victim petition for recovery-via-reissue (per Tether's Token Recovery policy and confirmed in aggregate by BlockSec's 2025 blacklist analysis).
The pattern breaks into a two-tier authorization structure. Tier 1: freeze only. addBlackList runs on Tether's discretion, no court order required, minutes to hours from a law-enforcement information request to the executed freeze (per Tether's Token Recovery process). The USDT is immobilized on-chain, balance intact. Tier 2: destroy plus reissue. destroyBlackFunds, especially when paired with a fresh mint, requires a stronger legal predicate: a court order for civil forfeiture (typical timeline of months from freeze to destroy for civil cases, consistent with the freeze-to-destroy lag documented in BlockSec's 2025 $1.26B report; faster with criminal proceedings), or a Tether-verified victim petition with tracing evidence that meets Tether's internal compliance bar. Tether internally re-audits the tracing before pulling the trigger, because destroying tokens belonging to an innocent third party would expose Tether to conversion and breach-of-fiduciary-duty risk.
The categorical breakdown of what ends up destroyed: sanctions-related destroys (OFAC, terror-financing programs), which move fastest once the underlying determination is final (see BlockSec's terrorist-financing on-chain analysis); fraud-recovery cases where the victim has been identified, almost always paired with a reissue via Tether Token Recovery; and law-enforcement seizures (civil or criminal forfeiture) where the reissue goes to a government-controlled custodian wallet.
The 2025 headline number. In 2025, destroy volume via destroyBlackFunds came in at roughly $698 million against roughly $1.26 billion of same-year freeze value, a same-period ratio of about 55.6% per BlockSec's $1.26B report. Two caveats worth stating explicitly: (1) this is a same-period flow ratio, not a per-freeze cohort survival rate: some destroys landing in 2025 correspond to freezes from 2023 or 2024, so the number describes pipeline throughput, not the fate of any specific 2025-blacklisted dollar; (2) the direction is nonetheless clear: a large share of blacklisted USDT does end up burned, and, as the next section covers, that burn is very often paired with a reissue somewhere on-chain.
Follow every destroy event in real time on the BlockSec USDT Freeze Tracker →.
"Destroyed" doesn't mean "lost": the burn-and-reissue mechanism
When Tether calls destroyBlackFunds, the tokens at that address are permanently burned. But Tether often pairs the burn with a fresh mint of equivalent USDT to a court-designated or victim address (per Tether Token Recovery policy), so the tokens are gone; the value is not. This is the single most misunderstood aspect of the destroy mechanic in 2022-era SERP content, and it changes how the ~55.6% same-period destroy-to-freeze ratio should be interpreted.
How burn + reissue works: the 2-step
The pattern has two distinct on-chain steps:
- Destroy at the bad address.
destroyBlackFunds(bad_address). Balance goes to zero,DestroyedBlackFundsfires, total supply decrements. - Mint at the good address. Tether calls the standard issuance function (also
onlyOwner) to mint an equivalent amount of USDT to a court-designated or victim address. Total supply increments back by the same amount.
Net effect on USDT total supply: zero. Net effect on the specific tokens that were at the bad address: gone. Net effect on the value: it now sits at a different address, controlled by the rightful owner or a government custodian.
Why the two-step rather than "reassign balance"? Because the USDT contract has no such function. transfer and transferFrom, the standard ERC-20 movement primitives, require the private key of the sending address, and by definition the good-faith victim doesn't have that key. Burn-and-reissue is the mechanism that lets the value reach the victim without needing the attacker's private key or reversing the source address.
Tether's official recovery policy
Tether publishes a formal Tether Token Recovery policy that spells out the process for victims:
- Recovery requests accepted for amounts greater than $1,000.
- Fee: up to 10% of the recovery amount, or $1,000 minimum, whichever is greater.
- Tether's evaluation is at "sole and absolute discretion" and is final.
- Formal channel: the Tether Information Requests team.
The 10% fee is not trivial for large recoveries, and "sole discretion" per Tether's policy means there is no formal right to recovery. But the pathway exists and it is used at real scale. See BlockSec's 2025 blacklist analysis for aggregate flow-through.
Tether's internal secondary audit
Before executing a destroy-and-reissue, Tether's compliance team performs a secondary internal audit of the tracing evidence: re-running address clustering, cross-checking the ownership claim, and verifying no innocent third-party wallet is entangled with the destroy target (this "sole and absolute discretion" review is baked into the Tether Token Recovery policy itself). The motive is legal exposure: destroying USDT that belonged to an innocent counterparty (a fresh custodial deposit, an exchange hot wallet, a downstream OTC party) exposes Tether to conversion and breach-of-fiduciary-duty risk. This is why the freeze-to-destroy timeline typically runs many months for civil forfeiture cases, and why the destroy volume in any given month tends to be freeze cases from months prior, a lag structure visible in BlockSec's 2025 $1.26B report.
Cases at scale
- Drift Protocol (April 2026): a Solana perp DEX exploit that drained ~$285M initially, revised to ~$295M in user losses after Mandiant attributed the operation to DPRK-linked actors who had spent months infiltrating the team. Tether then led a rescue package of up to $127.5M plus $20M from partners ($147.5M in total funding) with USDT replacing USDC as Drift's settlement layer at relaunch. The nine-figure scale in a single victim-recovery event shows the burn-and-reissue / recovery-funding pattern operates well beyond one-off five-figure cases.
- $344M Iran freeze (April 23, 2026), the largest single Tether freeze on record: two Tron addresses (
TNiq9...QZH81at $213M andTTiDL...pjSr9at $131M), executed in coordination with U.S. authorities. OFAC designated both addresses as property of Iran's Bank Markazi (Central Bank of Iran) with linkages to the IRGC-Qods Force and Hizballah; both addresses' behavior fit sovereign reserve storage rather than active laundering. Tether CEO Paolo Ardoino confirmed the coordination in the official Tether announcement. Frozen USDT is expected to progress through civil forfeiture to government custody viadestroyBlackFunds+ reissue. - $131M Iran IRGC freeze (July 14, 2026): Treasury Secretary Scott Bessent announced OFAC designations against four Tron wallets tied to Iran's IRGC and Central Bank under Executive Order 13902, part of Operation Economic Fury. Tether executed the freeze on all four within hours (per Decrypt). Combined with the April action, publicly-disclosed Iran-linked USDT freezes in 2026 total at least $475M ($344M + $131M), a conservative floor since additional Iran-linked freezes are not always individually announced. All candidates for destroy-and-reissue as forfeiture proceedings mature.
What the ~55.6% destroy-to-freeze ratio really means
The ~55.6% same-period destroy-to-freeze ratio is often reported as "$698 million lost." That framing is incomplete on two counts. First, it treats a pipeline flow ratio as if it were a cohort survival rate: some of the 2025 destroys correspond to freezes from earlier years, so it does not say "55.6% of 2025-blacklisted USDT was destroyed." Second, for the address that was blacklisted, the USDT is indeed gone. But for the value those tokens represented, the destroy is often paired with a fresh mint to the rightful owner or a government custodian (per Tether's recovery policy). That new USDT then goes to law enforcement, to the victim, or to a court-controlled disposition process.
The right frame: destroyBlackFunds is a recovery primitive, not a punishment. Journalists writing about a specific destroy event should always ask whether the destroy was paired with a reissue somewhere on-chain, and where the reissued tokens landed. That is the story of what actually happened to the value.
Notable destroy events
Compact reference of destroy-relevant cases on the 2024-2026 docket, in addition to the Drift Protocol and $344M / $131M Iran cases already covered above:
- January 2026 $182M across 5 Tron wallets, an earlier tranche of Operation Economic Fury, largely undisclosed as to specific attribution but part of the ~$1B in Iranian crypto that Treasury Secretary Bessent said the U.S. had seized since the campaign began (context: Decrypt on the July 2026 IRGC action).
- Iran IRGC $6.76M (2024): Tether coordinated with U.S. and Israeli authorities to freeze USDT tied to Iran's Islamic Revolutionary Guard Corps and Houthi forces (BlockSec case study). Portions have progressed through destroy per BlockSec's on-chain tracking.
- Hamas terrorist-financing patterns (2023-2025): multiple freezes targeting USDT flows to Hamas-affiliated wallets, documented in BlockSec's Following the Frozen analysis. Destroys have followed for the subset tied to formal designations.
For aggregate destroy volume, the BlockSec USDT Freeze Report Archive publishes daily, weekly, and monthly counts across both chains. Recent samples: June 2026 monthly, 65 burns, $37.58M destroyed (Tron $29.08M / Ethereum $8.50M); Week 29 (July 13-19, 2026), 12 burns. Destroy activity runs lower than freeze activity in any given week. Freezes are the front door and destroys are the back door of the same pipeline, with 6-18 months of case-processing latency between the two.
What "destroy" means for compliance and receivers
For the receiver whose address gets destroyed against, contract-level recovery is nil, no undoDestroy, no admin path to restore the burned balance. The only route is Tether's recovery policy, pursued as a petition with tracing evidence. Realistic outcome depends on demonstrating innocent ownership to Tether's satisfaction; if the address was flagged for legitimate cause (sanctions match, LE request), the odds of a reissue are effectively zero.
For the compliance operator monitoring their book, a destroy event on an address you had exposure to is a case-management trigger even after the initial freeze workflow closed. Regulatory reporting obligations continue through the destroy-and-reissue lifecycle. The audit-trail artifact should record all three events on that address: AddedBlackList, DestroyedBlackFunds, and (if visible) the paired reissue on the destination address.
For the tax and accounting picture, treatment varies by jurisdiction. In some jurisdictions the destroy is treated as a loss and the reissue as a fresh acquisition (potentially triggering a taxable event even though economically the victim is back where they started); in others, the paired transactions are treated as a single continuous holding. The IRS has not issued specific guidance on destroyBlackFunds/reissue pairs as of mid-2026, and the EU MiCA framework is silent on the tax side. Document both legs on-chain with block numbers and timestamps, and engage tax counsel in your jurisdiction. For OTC desks and merchants, destroy risk is downstream of freeze risk. By the time destroy fires the OTC exposure is usually already resolved via the freeze case (see aggregate freeze-to-destroy flow in the BlockSec 2025 report); the playbook is the same pre-transaction screening plus post-transaction event monitoring.
Academic and industry context
The academic-industry connection here is Andy's broader work on illicit on-chain fund flows, including the SIGMETRICS 2026 paper Shedding Light on Shadows, which introduces the MFTracer framework for tracing money flows through complex on-chain paths. That analytical lineage is what informs BlockSec's USDT Freeze Tracker instrumentation of the blacklist / destroy / reissue event stream. The tracing side (following the money) is complementary to the discretion side (what Tether does with what it finds). Treating destroy volume in any period as an independent compliance signal misreads the data, because destroy is a lagging function of freeze volume from months prior.
The regulatory implication is that destroy capability is becoming a de-facto licensing prerequisite for payment stablecoin issuers. Under the U.S. GENIUS Act (2025), permitted payment stablecoin issuers are treated as regulated financial institutions under the Bank Secrecy Act, with Recordkeeping / Travel Rule obligations for transfers of $3,000 or more and mandatory sanctions-list screening under the Treasury's proposed implementing rule. Freeze (and downstream destroy under a formal legal disposition) is no longer a nice-to-have; it is a licensing precondition. Hong Kong's Stablecoins Ordinance (effective August 1, 2025) implies the same capability through its AML/CFT and sanctions-cooperation requirements, and the EU's MiCA regime pushes issuers in the same direction. Expect every payment stablecoin issuer (USDC, PYUSD, RLUSD, FDUSD, and future HKD-referenced tokens) to build equivalent destroy and reissue capabilities as licensing regimes mature.
Frequently asked questions
Can destroyed USDT be recovered?
Not at the address it was destroyed against: destroyBlackFunds zeros the balance and decrements the total supply, with no contract-level reverse. But when Tether pairs the destroy with a fresh mint to a victim or court-designated address (the burn-and-reissue pattern), the value is recovered as newly-minted USDT. Victims should pursue this via Tether's official Tether Token Recovery process.
What's the difference between destroyBlackFunds and a normal token burn?
A normal burn requires the token holder's private key: the holder calls the burn function on their own balance, in line with the ERC-20 movement model. destroyBlackFunds is onlyOwner, works on someone else's balance, and is guarded by a require that the target address is already blacklisted. It is an issuer-controlled enforcement/recovery mechanism, not a user-facing burn.
Who can call destroyBlackFunds?
Only Tether's owner multisig, on both the Ethereum USDT contract at 0xdAC17F958D2ee523a2206206994597C13D831ec7 and the TRC-20 USDT contract at TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. No court, regulator, or exchange can trigger the destroy at the contract layer.
Does destroyBlackFunds work on Tron USDT?
Yes. The same three-function set exists on both chains with equivalent owner-only controls. In 2026, Tron dominates destroy activity, typically 85-97% of a given week's total per the BlockSec USDT Freeze Report Archive.
How much USDT has been destroyed to date?
BlockSec's 2025 report recorded roughly $698 million destroyed against roughly $1.26 billion blacklisted in the same year, a same-period flow ratio of about 55.6% (not a cohort survival rate, since some destroys correspond to freezes from earlier years). Monthly destroy volumes in 2026 have been in the tens of millions (e.g., $37.58M in June 2026, per the BlockSec USDT Freeze Report Archive). Cumulative all-time volume can be reconstructed from the DestroyedBlackFunds event stream on both chains via Etherscan and Tronscan.
If my USDT was destroyed, can I still get compensated? If you are a legitimate third-party victim (not the flagged address holder), yes: submit a recovery request via the official process. Requests above $1,000 are accepted; fee up to 10% or $1,000 minimum. If you were the flagged address holder and the freeze was for legitimate cause, practical odds are effectively zero.
Related reads
- Pillar: USDT Freeze: The Complete 2026 Guide
- Companion spoke: How to Unfreeze a USDT Address, the
removeBlackListside of the mechanic - How to Check If a USDT Address Is Frozen
- The USDT Blacklist, Explained (2026)
- External:
About the author
Andy is co-founder of BlockSec and the technical lead behind MetaSleuth, Trace AI, and Phalcon Compliance. He is also an Associate Professor at The Chinese University of Hong Kong, where his research on system and blockchain security includes the SIGMETRICS 2026 Best Paper Runner-Up Shedding Light on Shadows. Personal homepage: yajin.org.
Follow: X / Twitter · LinkedIn
