Contract Powers Registry / base

cbETH

0x2ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec22 on base

In one line: upgradeable proxy (eip1967.implementation); retained powers: burn_others, mint, upgrade.

UpgradeableYes
Source verifiedYes
Controlled byA contract
Confirmed powers3

Can this code be replaced?

Yes — this is a proxy. The address you interact with holds no logic of its own; it forwards calls to a second contract. Whoever holds the upgrade right can point it somewhere else, and every behaviour described on this page changes with it.

Patterneip1967.implementation
Current logic0x07a71b9b835c9eba242836704d17da0953324e1f
Logic nameUpgradeableOptimismMintableERC20
Logic source verifiedYes
Raw storage evidence (2)

Who holds the keys?

Owner / admin0xd94e416cf2c7167608b2515b7e4102b41efff94f
Found viaadmin()
That address isA contract

owner is a contract — could be a multisig or timelock; this endpoint does not verify which. It could be a multisig, a timelock, or a single-key wrapper — this registry does not open it. Follow the link above to see what that contract can do.

What the privileged role can still do

Each card is a capability found in the code. declared = the contract’s published interface exposes it. bytecode-heuristic = the 4-byte selector appears in the compiled code, which often means the contract implements it — but it can equally be a function this contract calls on another contract. Only a verified source settles that.

Balances can be destroyed

declared

Tokens can be burned from an address other than the caller’s own.

Evidence (2)
  • burn(address,uint256) implementation-abi
  • burn(address,uint256) implementation-bytecode

New tokens can be created

declared

Supply is not fixed by the code — the privileged role can issue more.

Evidence (2)
  • mint(address,uint256) implementation-abi
  • mint(address,uint256) implementation-bytecode

Code can be replaced

declared

The logic behind this address can be swapped for different code. Everything below can change with it.

Evidence (4)
  • changeAdmin(address) abi
  • upgradeTo(address) abi
  • upgradeToAndCall(address,bytes) abi
  • changeAdmin(address) bytecode-selector

Is there a bug bounty on this?

No live bug-bounty program matched this contract’s name in my index (186 Immunefi + 52 Cantina programs, rebuilt daily). Matching is by name, not by address — a program can cover this contract without the names lining up. Browse the full index at Bounty Radar.

Raw facts

Chainbase (chainId 8453)
Contract nameProxy
Compilerv0.8.15+commit.e14f2714
LicenseMIT
Bytecode size2,096 bytes (logic: 7,322)
DELEGATECALLpresent
SELFDESTRUCTabsent
CREATE2absent
Explorerview on block explorer ↗

How this was produced, and what it cannot tell you

Storage slots, bytecode and eth_call results were read from public RPC nodes; where the source is verified, the published interface was read too. Nothing here is copied from another site’s opinion. Generated in 1341 ms on 2026-08-29.

What would change the answer: an upgrade after the date above; a power reachable only through a contract this one trusts; or role-based access control, whose holders this registry does not enumerate. Re-read the chain before you rely on it.

Machine-readable

Same facts as JSON, free, no key: /c/base/0x2ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec22.json. Live lookups for any address (not just this list) are $0.05 per call.

Want a human-grade read?

This page is automated pattern-matching. If you need someone to actually read the code and tell you what breaks, I do fixed-scope micro-audits — you pay after you read the report.