A portrait gallery of rollup governance

Who holds the keys?

Ethereum's rollups promise to inherit its security. Yet almost every one of them can be rewritten by a small group of people, often with no warning at all.

82rollups and validiums, painted
1,128keys on the walls, one per upgradable contract
71chains where the most powerful group can swap core contracts instantly
4chains where no one is named as a key-holder

Also in the gallery

Public companies

The same question asked of Meta, Alphabet, Tesla and Apple, read from their proxy statements.

How to read a painting

Seated in the gallery are the groups who can upgrade the chain's contracts, that is, replace their code with anything they like. Hanging below each group are its keys, one for every contract it can replace.

Who is in the room

  • Black robes and ruffsA security council: a multisig of named, mostly independent signers.
  • Coloured coatsA team or company multisig. Each colour is a different group.
  • The lone clerkA single private key. One person, one signature.
  • The crowd at the urnA token vote. Slow, public, and usually behind a long timelock.
  • Grey visitorsAnother system's operators, holding keys to infrastructure the chain relies on.

What their keys open

  • Gold key: a core contractThe bridge, the portal, the proof system, the messengers. A malicious upgrade here can reach users' funds.
  • Iron key: a peripheral contractFee vaults, the gas oracle, the NFT bridge, the pause switch. They matter, but they can't move your funds.
  • A ring of small keys: someone else's systemContracts the chain depends on but doesn't run, such as EigenLayer. Drawn once, however many there are.

Speed matters

⏳ marks a key behind a timelock. A long enough delay lets users see an upgrade coming and leave before it lands; a key with no delay can change the rules overnight.

Why it matters

Code is only as trustless as the people who can change it.

A rollup's contracts hold the money that crossed its bridge. Whoever can upgrade those contracts can, in principle, redirect it. Most teams keep that power on purpose: young systems have bugs, and someone has to be able to fix them fast.

The question is who that someone is. Is it a council of independent signers, a company's own multisig, or one key on one laptop? Does the change land instantly, or after a delay long enough for users to leave? These paintings answer that at a glance, for every chain.

Snapshot of 23 October 2026.