Ethereum block 26,437,514 · 17 Nov 2026 21:39 UTC
Ampdat Control · Everything covered
Who controls USDC
USDC (USD Coin) is issued by Circle, with 44.31B USDC on Ethereum. A single key can upgrade its code. Any of 32 accounts can mint. A single key can freeze an address. Nobody can seize or burn a frozen balance. A single key can pause all transfers. No key change is pending.
0xa0b8…eb48 · USD Coin · Ethereum
Who can do what, contract by contract
FiatTokenProxy · 0xa0b8…eb48
Token. Upgradeable: it now runs FiatTokenV2_2 (0x4350…02dd).
| Capability | Held by | What it is | Note |
|---|---|---|---|
| Upgrade | 0x807a…95d2 | A single key | |
| Appoint roles | 0xfcb1…ae3a | A single key | Appoints the pauser, blacklister, master minter and rescuer, and may hand over ownership. |
| Pause | 0x4914…8566 | A single key | |
| Freeze | 0x0a06…78f9 | A single key | blacklist and unBlacklist; FiatToken has no seize. |
| Configure minters | 0xe982…de17 | The MasterMinter contract | |
| Mint | 0x0057…6ba5, 0x0896…869a, 0x119c…3e90, 0x1375…5ef1, 0x1971…2186, 0x19a9…27d8 and 26 more | 27 × a single key; 1 × the GatewayMinter contract; 1 × an upgradeable contract; 1 × the SeizureRegistry contract; 1 × the TokenMinter contract; 1 × the TokenMinterV2 contract | Each within its allowance; any minter may burn its own balance. |
| Rescue tokens | None | — |
MasterMinter · 0xe982…de17
Master minter.
| Capability | Held by | What it is | Note |
|---|---|---|---|
| Appoint controllers | 0xc1d9…c704 | A single key | Points each controller at the one minter it manages, and may hand over ownership. |
| Set minter allowance | 0x08c7…2ec3, 0x0f49…54d3, 0x1238…27f3, 0x130a…246c, 0x14b1…5a3e, 0x162b…682e and 37 more | 43 × a single key | Each for its own minter: configure, raise, lower, remove. |
- A change of the minter manager that logs nothing is caught only by the head checks.
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
- What a minter contract does with its allowance (the CCTP minters, the Gateway minter, SeizureRegistry) and who owns it beyond one named contract.
- 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/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
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)