How Tether's own proposals tip off a freeze before it lands
When a USDT deposit lands in your exchange account and the account gets reviewed soon after, the review is rarely about you. It is about where that USDT has been. Tether freezes an address by publishing a multisig proposal to its contract, and that proposal is visible before the freeze actually executes.
TrustSniffer reads those proposals as they appear and has flagged 924 wallets this way since 2026-07-14, ahead of the issuer's own freeze. Of the 921 flagged wallets with a known outcome, 918 were frozen by Tether afterward, a 99.7% hit rate. The flag is a read of the paperwork before the signature count is reached, not a guess.
The gap between the flag and the freeze is short. The median lead time is 10 minutes, and even the slower cases resolve within 3.2 hours at the 90th percentile. At the moment of freeze, the wallets caught this way held $413.3 million between them, money that moved from spendable to locked inside that same window.
834 TRON freezes in 7 minutes, 80 on Ethereum in 33
Not all networks move at the same pace. On TRON, 834 of the tracked freezes were flagged in advance, with a median lead of 7 minutes. On Ethereum, 80 were flagged in advance, with a median lead of 33 minutes.
That difference matters if you are holding a deposit while an exchange reviews it. A TRON-based USDT transfer tends to resolve into a freeze, or not, inside a few minutes. An Ethereum-based transfer gives roughly four times as long before the same outcome lands, which is also roughly four times as long for an exchange's own screening to catch up with the issuer.
If you want to see whether a wallet you are about to receive funds from sits anywhere near this kind of activity, running it through the wallet checker before you accept the transfer takes less time than either median lead.
The four wallets caught by their own cross-chain twin
Four wallets were flagged for a different reason entirely. Each was the cross-chain twin of a key that Tether had just frozen on another network, and each was then frozen in turn.
A wallet does not have to show its own history on the chain you are watching to end up frozen. It can be caught purely because the same key holder controls the matching address on both TRON and Ethereum.
Pending freeze proposals are published without the address or the exact amount until the freeze executes, which is why even a live record like the live USDT freeze tracker cannot warn the person holding the funds in time to move them. Knowing a freeze is coming in general is not the same as knowing whose wallet it will be.
Why a 10-minute head start rarely reaches the person holding the funds
If an exchange froze your account after a USDT deposit, the funds you received were likely already inside this window, flagged or about to be, before your account was ever reviewed. Nothing you did at the exchange caused the hold. The exposure sits upstream, in whichever wallet sent you the deposit.
A median lead of 10 minutes is not enough time to act once a deposit has already cleared into your account. The only real window is before you accept a large or unfamiliar transfer, not after.
- Check the sending wallet against known freeze activity with the wallet checker before you treat a large USDT deposit as settled.
- If the deposit came through a platform rather than a direct transfer, run that site through the website checker as well.
How TrustSniffer reads the freeze proposals before they execute
The tracker behind these numbers is built from reading Tether's multisig proposals on TRON and Ethereum before they execute, matching each one against its eventual outcome, and recording how long the gap lasted. The running record is public at the live USDT freeze tracker.
This sits alongside TrustSniffer's wider first-party dataset of 5,463 website analyses and 17,666 wallet assessments, though the freeze tracker itself only covers these two networks.
Because pending proposals withhold the exact address and amount until execution, most of this lead time is only visible after the freeze has already happened. The method confirms what caused a hold; it does not give a holder advance notice.
