Upgradeable tokens: what changes when the logic can be swapped

Many contracts on EVM chains are split in two: a proxy that holds the balances and a logic contract that holds the code. Every call to the proxy is forwarded to the logic. Whoever controls the upgrade can point the proxy at a different logic contract, and from that block on the token behaves differently.

Where upgrades hide

Most proxies follow a standard and keep the logic address in a fixed storage slot. The scan reads the EIP-1967 implementation, admin and beacon storage slots, plus the older legacy slot, directly from chain state. It also recognises minimal proxies (EIP-1167), which forward to one fixed logic contract and cannot be upgraded.

Reading the result

• No slot set: the code you can read is the code that keeps running, as far as the standard patterns go.
• Implementation slot set: open the logic contract and the admin address listed in the evidence.
• Beacon: one beacon can upgrade many contracts at once; check who controls the beacon.
• Issuer beacon: official stock tokens use their issuer's beacon. That is a regulated issuer's control, still a control.

Upgradeability is not a red flag on its own; serious projects use it to fix bugs. The useful questions are who holds the key, whether upgrades wait behind a timelock, and whether that wallet is one person.