Skip to content
PANTHER

Renounced Ownership? Check Who Can Upgrade the Token

A zero-address owner answers one permissions question. Follow the proxy, implementation and upgrade authority before deciding whether an EVM token’s rules can change.

By Panther@0xPnthr

5 min read

Conceptual illustration of a silver token frame with a sliding inner disc exposing a different surface. Text: Who can change the code? Panther Knowledge.
Illustration: Panther Knowledge

Key points

  • Renouncing one owner role does not necessarily remove a separate proxy upgrade permission.
  • Read token state through its proxy, then trace the function and controller that authorize upgrades.
  • Circle’s USDC design illustrates separate token-owner and proxy-admin powers; it is not an example of renounced ownership.
  • Proxy detection, a multisig label or an empty standard slot alone cannot establish that code is immutable.

The owner field shows a row of zeros. The community calls the contract renounced. You are about to close the explorer before checking token upgradeability.

Token upgradeability is the reason to keep it open. In a proxy system, the address you hold can stay the same while the code that handles transfers changes. To assess who can change the rules, identify the proxy pattern, locate its upgrade permission and follow that permission to the controlling account or governance contract. An owner() result alone cannot do that work.

This guide covers EVM token contracts, including Ethereum and Base. It explains a read-only investigation: you do not need to connect a wallet, approve a token or send a transaction.

What renounced ownership actually tells you

In a conventional OpenZeppelin Ownable contract, renouncing ownership removes access to functions protected by onlyOwner. OpenZeppelin’s access-control documentation also describes separate role-based permissions. A minter, administrator or upgrader can have authority through a different check.

So first establish what you read. Was owner() called on the token address, using its implementation’s interface, or directly on an implementation contract? Proxy calls execute implementation code using the proxy’s storage. Reading the implementation address directly can return a different owner because you are reading a different account’s state.

A scanner’s renounced badge is a lead to inspect. The relevant question is which protected functions that ownership result disables, and which powers remain elsewhere.

Token upgradeability starts with the exact address

Find the chain and token contract through the issuer’s own documentation, then cross-check the full address. Panther’s contract-address verification guide covers that first step. A ticker and logo are insufficient identifiers.

On the explorer’s Contract page, look for a proxy label, an implementation link and a Read as Proxy tab. Follow the implementation link to its verified source, but return to the token’s proxy address when reading token state. Read as Proxy supplies the implementation’s interface for calls directed at the proxy.

Etherscan warns that proxy detection has limitations. Its displayed interface is not a guarantee of which code executes. If the source is unavailable, the detected target conflicts with the code, or you cannot establish the delegation path, record the result as unresolved. An absent proxy badge does not establish immutability.

Find the function that changes the implementation

The proxy family determines where to look. OpenZeppelin’s proxy reference distinguishes three common arrangements:

Pattern Where upgrade control normally lives What to trace
Transparent In the proxy’s upgrade path, often through a separate ProxyAdmin contract The actual admin and the authority controlling it
UUPS In the implementation’s upgrade functions The authorization used by _authorizeUpgrade and any roles it checks
Beacon In a separate contract supplying the implementation to several proxies The beacon, its upgrade function and its controller

These are starting points, not universal detection rules. Search verified source for names such as upgradeToAndCall, upgradeTo and _authorizeUpgrade. Then read the modifier or permission check. A function name without its authorization tells you little.

Version details matter. In OpenZeppelin Contracts 5.x, a transparent proxy uses an immutable admin and an associated ProxyAdmin. The ability to authorize upgrades follows ownership of that ProxyAdmin. Do not assume every older or custom proxy behaves the same way.

For a technical cross-check, ERC-1967 defines common implementation, beacon and admin storage slots, readable through eth_getStorageAt. Those slots are useful only after identifying the design. A zero in an ERC-1967 slot is not evidence that a legacy or custom proxy has no upgrade path. Standard ERC-1167 minimal clones, meanwhile, delegate to a fixed target; the word proxy alone does not mean the target can be replaced.

Worked example: USDC separates token ownership from proxy administration

Start at Circle’s official USDC address list. The Ethereum entry for USDC ($USDC) links to:

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

Open that Ethereum contract on Etherscan. Its verified proxy source is named FiatTokenProxy and includes an AdminUpgradeabilityProxy layer. Its Read as Proxy interface exposes token roles including owner, pauser, blacklister and masterMinter.

Now compare those labels with Circle’s token-design documentation. It assigns implementation upgrades to the admin role. The token owner can reassign other roles but cannot reassign that proxy admin. Circle’s admin-proxy source shows the separate authorization check for administrative operations.

The worked result is a distinction between permissions: token ownership and proxy administration are separate controls. It is not a claim that USDC has renounced ownership. Nor does this guide identify today’s signing keys or guarantee future governance. The published repository describes the design; the deployed code and current onchain state are what you must inspect for a particular deployment.

That distinction gives you a repeatable question for another token: which exact function permits an implementation change, and who can satisfy its check?

Follow the authority beyond the first contract

A nonzero controller address is the next step, not the conclusion. If it is another contract, inspect that contract’s permissions too. A ProxyAdmin may have an owner. An upgrade role may have an administrator able to grant it again. A governance contract may schedule the change through a timelock.

Record the controller’s address, the permission that matters and the evidence for any claimed delay. For an OpenZeppelin TimelockController, the documented minimum delay is available through getMinDelay(). Also determine whether the upgrade must actually pass through that timelock. A delay on one route provides little reassurance if another authorized route skips it.

If a project describes its controller as a multisig, establish the signing threshold and any additional execution paths before repeating the claim as a safeguard. An explorer label alone does not reveal who controls the signers. Where that information is unavailable, say so.

Write down a bounded conclusion

Keep a short inspection record: chain, token/proxy address, implementation address, proxy pattern, upgrade function, controller and evidence timestamp. Record the block height when your tools expose it. Separate values you read from inferences you made.

A useful conclusion might be: “The token uses a transparent proxy. Its upgrade authority is held by this ProxyAdmin, whose owner is this governance contract. I verified this delay, but have not established whether another execution path exists.” That is more informative than a safe/unsafe badge.

Upgradeability can support repairs and planned improvements. It also means an assessment of today’s implementation may not describe tomorrow’s code. Even a contract with no upgrade path can retain minting, pause or transfer restrictions. This check complements, rather than replaces, liquidity-lock checks and token-holder analysis.

Sources and interfaces checked on Nov. 21, 2026. This is a documented reading workflow, not an audit or a transaction test.

Sources

  1. 01Proxy contracts API reference · OpenZeppelindocs.openzeppelin.com/contracts/5.x/api/proxy
  2. 02Access control and timelocks · OpenZeppelindocs.openzeppelin.com/contracts/5.x/access-control
  3. 03ERC-1967: Proxy Storage Slots · Ethereum Improvement Proposalseips.ethereum.org/EIPS/eip-1967
  4. 04ERC-1167: Minimal Proxy Contract · Ethereum Improvement Proposalseips.ethereum.org/EIPS/eip-1167
  5. 05Proxy contracts: explorer detection and limitations · Etherscaninfo.etherscan.com/what-is-proxy-contract/?id=14601
  6. 06USDC contract addresses · Circledevelopers.circle.com/stablecoins/usdc-contract-addresses
  7. 07FiatToken design and roles · Circlegithub.com/circlefin/stablecoin-evm/blob/master/doc/tokendesign.md
  8. 08AdminUpgradeabilityProxy source · Circlegithub.com/circlefin/stablecoin-evm/blob/master/contracts/upgradeability/AdminUpgradeabilityProxy.sol

Responses

Links, wallet addresses and contact details are not allowed.

0/1000

No responses yet. Start the conversation.

Panther Journal — The intelligence brief

Stay ahead of the story.

Free. New investigations delivered when published. Unsubscribe anytime.

Launching something?

Work directly with Panther.

Start a project

More from the library