Hermes maps who can upgrade deployed contracts on Base, through every layer between a proxy and the keys behind it, and what else those keys reach. It reads storage and calls functions; it never reads bytecode for bugs. It states what can upgrade a contract, never whether anyone will, and never that a key is compromised.
Addresses come from a hand-curated list and from chain-wide discovery of the three ERC-1967
events (Upgraded, BeaconUpgraded, AdminChanged). Discovery
reads 1,000-block windows at fixed positions spread over Base's history and admits at most a
few addresses per implementation, beacon or admin. The index is a sample, not a
census. Without the cap, clones of a handful of contracts would be most of it. Every
count Hermes publishes is within the sample, and each API answer carries its scope.
Each address's ERC-1967 implementation, admin and beacon slots are read directly, plus the EIP-1822 and ZeppelinOS slots. Implementation and admin set: transparent. Implementation only: UUPS. Beacon: beacon. Admin only: an OP Stack predeploy. Covered kinds are transparent, UUPS, beacon, EIP-1822 and admin-only. Inherited storage, eternal storage, Diamond and the ZeppelinOS slot are recorded and not counted as covered.
| Proxy | Walk starts at | Most confidence |
|---|---|---|
| Transparent, admin-only | the ERC-1967 admin | High |
| Beacon | the beacon, whose controller upgrades every proxy using it | High |
| UUPS | the proxy itself, only after its implementation answers proxiableUUID() with the ERC-1967 slot | Medium: what answers does not prove what gates _authorizeUpgrade |
| Answers | Kind | Keys |
|---|---|---|
| no code on Base, and none at its unaliased address on Ethereum | key | 1 |
| an EIP-7702 delegation designator | key (delegated) | 1: its private key signs whatever the delegate allows |
no code on Base, code at address − 0x1111…1111 on Ethereum | L1 alias: the walk continues on Ethereum | those of the Ethereum contract |
getOwners() and getThreshold() | Safe | sum of the m cheapest owners |
getMinDelay() | timelock: the delay is read | unknown: proposer and executor roles are not listed on chain |
owner() | owned contract: the walk continues to the owner | the owner's |
OpenZeppelin AccessControl | role-gated | the cheapest holder of the upgrade role or of its admin role, when listed |
entryPoint() | ERC-4337 smart account | its cheapest signer, when MultiOwnable; otherwise unknown |
0x…dEaD, 0xff…ff, precompiles | sentinel | none: no one holds these keys |
| none of the above | unrecognized | no root is published |
The walk follows at most four links and stops on a cycle. An unknown owner anywhere under a
Safe makes the whole count unknown, because the unknown one could be a single key. A key that
signs in two places under one root is counted once: summing each branch's cheapest keys would
count it twice and overstate the margin, so the fewest distinct keys are searched for instead,
and the count is unknown (shared_signers) when that search is too large.
A missing number is null, never zero. A covered proxy with no root says why:
unrecognized_interface, uups_unconfirmed, no_upgrade_path
or rpc_undetermined. A root with no key count says why too: truncated,
cycle, owners_unknown, roles_unread,
account_keys_unread, no_known_key or shared_signers. A call the node would not answer
is a third outcome, distinct from a contract answering "no", and never becomes a verdict.
Confidence only falls along a walk.
Every scan reads both chains at their finalized blocks and keeps the graph it walked: each address's answers, and each edge with the blocks it was first and last seen at and the block it closed. A change between two scans is recorded with both blocks, and bisection over archive state then pins single-read changes (an owner, a Safe threshold or signer, a delay, a slot) to the first block the new value holds at; everything else keeps the two scan blocks that bracket it. A change in how Hermes reads the chain (a new model version) is recorded as a reinterpretation and never shown as the chain moving. "First seen" means first seen by Hermes; nothing before the first scan of an address is in the store.
For any address, Hermes lists the indexed proxies whose upgrade walk passes through it, in three groups: those it controls alone, those whose authority it takes part in without being enough alone (one signer of a 2-of-5), and those where the walk cannot tell. A key is taken on both chains, since one private key signs for its address everywhere. Nothing is added up across groups, and no figure is a dollar figure.
The limitations are listed in full in LIMITATIONS.md.