Security council (L2)

Rollups depend on complex contracts and proof systems that may still hide bugs. Many keep a security council: a group of individuals or organizations, often a few dozen at most, who jointly control a multisig with special powers. Depending on the design, the council can pause the bridge, upgrade contracts without the usual delay or override a faulty proof, provided a high threshold of members signs.

Councils are central to how L2BEAT's rollup stages framework rates decentralization. A rollup in the earliest stage may be fully controlled by its team. To reach Stage 1, the council's powers must be limited to fixing on-chain-provable bugs and it must meet minimum size, threshold and outside-membership requirements. In Stage 2, it can act only on errors the proof system itself detects. Arbitrum's council, elected by its DAO, is a frequently cited example.

A council is still a trust assumption: if enough members collude, lose keys or are coerced, they could misuse their powers. Users should check who sits on it, the signing threshold and whether ordinary upgrades come with an exit window long enough to withdraw funds.