Ethereum block 26,437,514 · 17 Nov 2026 21:39 UTC
Ampdat Control · Everything covered
Who controls USDT
USDT (Tether USD) is issued by Tether, with 84.3B USDT on Ethereum. A 3-of-6 multisig (MultiSigWallet) can upgrade its code. A 3-of-6 multisig (MultiSigWallet) can mint. A 3-of-6 multisig (MultiSigWallet) can freeze an address. A 3-of-6 multisig (MultiSigWallet) can seize or burn a frozen balance. A 3-of-6 multisig (MultiSigWallet) can pause all transfers. No key change is pending.
0xdac1…1ec7 · Tether USD · Ethereum
Who can do what, contract by contract
TetherToken · 0xdac1…1ec7
Token.
| Capability | Held by | What it is | Note |
|---|---|---|---|
| Upgrade | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | deprecate(address): every ERC-20 call is forwarded to a successor contract. Not a proxy. |
| Mint | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | issue |
| Burn | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | redeem, from the owner's own balance |
| Freeze | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | addBlackList and removeBlackList |
| Seize | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | destroyBlackFunds: burns a blacklisted balance |
| Pause | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | |
| Set fee | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | setParams: a transfer fee, zero so far, within the limits the contract hard-codes |
| Transfer ownership | 0xc6cd…a828 | A 3-of-6 multisig (MultiSigWallet) | At once, with no event. |
- transferOwnership emits no event. The owner here is a head read, not a replay.
MultiSigWallet · 0xc6cd…a828
Owner multisig.
| Capability | Held by | What it is | Note |
|---|---|---|---|
| Sign | 0x25bb…4155, 0x4096…85c1, 0x4d91…8973, 0x61d5…9fed, 0xac3b…1fa0, 0xee52…fc8c | 6 × a single key (3 of 6 must sign) |
- Transactions submitted to the wallet and waiting for confirmations. A pending token action is a Submission with too few Confirmations; this family reads only the wallet's signers and threshold.
Pending key changes (0)
No key change is pending.
How this is checked
Every single holder on this page was compared with the contracts' own getters and storage at block 26,437,514, and they agree. The keys are rebuilt from each contract's admin events, so a change shows here with the transaction that made it.
What this page cannot see
- Any change of the token's owner. TetherToken's transferOwnership emits no event, so the owner is read at the head in each run and has no history; a change and a change back between two runs would not be seen.
- The owner before the block this family first read it at.
- Reserves, redemption rights and anything else off chain.
- The same coin on other chains: each deployment has its own keys.
- Freezes, seizures, mints and burns: the keys being used are not in the record stream, only the keys changing hands.
- Who was behind a sender: where a log names no caller, a record's actor is the transaction's sender (sources.actor: tx_from), which may be a key executing for the role holder.
The same answer for your agent or app
This coin as JSON: every key holder with what it is, the whole chain above it, every key change since the coin was deployed with the log it rests on, and a feed of new ones. Paid per call in USDC on Base with x402; no account needed.
GET https://control.ampdat.com/v1/ethereum/0xdac17f958d2ee523a2206206994597c13d831ec7
From an AI assistant (Claude, ChatGPT, any MCP client): connect the MCP server below. Its tools for who controls a contract and what is pending are free.
https://control.ampdat.com/mcp
Coverage (free)Schema (free)API referenceDocs, MCP setup and the Claude plugin (GitHub)