The key that can freeze your USDT

Freezes are not issued by Tether the company; they are issued by one multisig contract on TRON, by a handful of addresses, under a signature threshold anyone can read. Everything on this page comes from that contract — the signer set from a live call, everything else from our event ledger.

Threshold
2 of 3
Signer changes ever
2
Withdrawn or failed
17
Non-freeze proposals
35

Who holds the key today

Read live from getOwners() and required() on the multisig contract. Any 2 of these 3 addresses can freeze any USDT balance on TRON.

#SignerOn chain
1 TYn9kGVaNbXCsdqDCvKu4ubDvj3ZSxmyN1 Tronscan
2 TKHuVq1oKVruCGLvqVexFs6dawKv6fQgFs Tronscan
3 TRLi4KskHxfACnxKzLrf2wNHauWUQpwziN Tronscan

Every time the key changed hands

  1. signer removed 2021-02-15 17:12 UTC
    TAEVgkzcP1REvNFwvCxEaz5EcjAaPtAyhR
  2. signer added 2021-02-15 17:12 UTC
    TRLi4KskHxfACnxKzLrf2wNHauWUQpwziN

2 changes in everything we have indexed. That is a small number, and it should be read as one: it says the set has been stable, not that it cannot change tomorrow.

What else this key does

The same threshold that freezes balances also mints and burns USDT. Function names are computed from the four-byte selector with keccak-256 and matched against the contract's published ABI — not copied from a lookup table. Anything that doesn't match is shown as raw hex and left undecoded.

FunctionSelectorProposals First seenLast seen
transfer(address,uint256)
move USDT out of the contract
a9059cbb 16 2025-12-02 15:53 UTC 2026-08-24 17:03 UTC
issue(uint256)
mint new USDT
cc872b66 16 2025-12-02 15:53 UTC 2026-08-24 17:03 UTC
not decoded 1 2026-08-25 13:27 UTC 2026-08-25 13:27 UTC
not decoded 99a88ec4 1 2026-09-18 16:41 UTC 2026-09-18 16:41 UTC
redeem(uint256)
burn USDT from treasury
db006a75 1 2025-09-04 16:07 UTC 2025-09-04 16:07 UTC

2 selector(s) didn't match the published ABI. We show the hex rather than guessing a function name.

Withdrawn signatures and failed executions

Two things the chain records that nothing else surfaces: a signer taking their signature back, and an execution that was attempted and reverted. Both are rare — 17 events in everything we have indexed — and both used to be invisible here, folded into “nobody executed it.”

WhatProposalTarget When (UTC)Outcome
signature withdrawn 11208 TQBXakPzttyN4G2XtsU6Y9T1QDe1bJoKLM 2026-09-30 16:06 UTC never executed
signature withdrawn 10771 TLWKaabJJsRUarRFHP4GXGqXB1KTKhH2wa 2026-09-09 16:46 UTC never executed
signature withdrawn 7577 TNif5EdWZCNaFtCW47ExCJTHpKkmcyn27R 2026-03-25 20:26 UTC never executed
signature withdrawn 7578 TQyzUvjrrENU6poCGWoxaTnxXBZtDE5hQM 2026-03-25 20:26 UTC never executed
execution failed 6640 T9znxSUJb3RwemHW4RMMb5YubtqkhhnnXh 2025-12-15 19:48 UTC never executed
execution failed 5153 not a freeze proposal 2025-12-02 14:40 UTC —
execution failed 2981 not a freeze proposal 2025-03-11 23:25 UTC —
execution failed 2943 not a freeze proposal 2025-03-07 17:46 UTC —
execution failed 819 not a freeze proposal 2023-07-06 18:47 UTC —
execution failed 819 not a freeze proposal 2023-07-06 18:46 UTC —
signature withdrawn 639 not a freeze proposal 2022-12-06 15:16 UTC —
signature withdrawn 638 not a freeze proposal 2022-12-06 15:16 UTC —
signature withdrawn 634 not a freeze proposal 2022-11-14 00:03 UTC —
signature withdrawn 618 not a freeze proposal 2022-10-31 13:49 UTC —
signature withdrawn 617 not a freeze proposal 2022-10-31 13:49 UTC —
signature withdrawn 616 not a freeze proposal 2022-10-31 13:49 UTC —
execution failed 598 not a freeze proposal 2022-10-06 18:55 UTC —
What this page is not. It is not an accusation and not a scoring of anyone. A signature threshold that can freeze balances is how this token was designed to work, and it is documented by its issuer. The reason to publish the mechanics is that people holding the token are usually told about the two-step freeze only after it has already reached step two.

↑↓ move ↵ open ↵ look it up esc close Nothing you type here is stored or sent anywhere but this lookup.