How is a layer 2 governed?

Through a mix of token holder voting on ecosystem matters and a security council or timelocked upgrade process for the contracts controlling sequencing, bridging and proofs.

Why do rollups need a security council?

Because some failures, such as a broken proof system, need intervention faster than a full vote allows. The council operates under published, bounded powers.

Do L2 governance decisions execute on the base chain?

Often yes. Contracts controlling the bridge and upgrades typically live on the base layer, so an approved change has to be executed there as well.

Use cases

Governance for L2s and rollups

Layer 2 and rollup governance settling approved decisions to a base chain

Rollups concentrate enormous power in upgrade keys. Governance has to constrain them credibly.

Upgrade keys need public rules

Who can upgrade, under what delay, and how users are notified should be documented and enforced by contracts.

Security councils

A council with a narrow emergency mandate and public membership is preferable to an anonymous key holder.

Home chain, remote effect

Most rollup governance votes on L1 and executes on L2. Confirmation on the destination chain is part of execution.

Two governance surfaces at once

A rollup has social governance over grants, incentives and ecosystem direction, and technical governance over sequencers, bridges, proof systems and upgrade keys. The second category can affect user funds directly, so it warrants stricter process.

Publish which contracts are upgradeable, who can upgrade them and what delay applies. For rollups this disclosure is not paperwork, it is the honest description of how much trust a user is extending.

Settling decisions back to the base layer

Where a rollup's governance settles to a base chain, execution involves both networks and the latency between them. Decisions can appear approved on one layer and unexecuted on the other for a meaningful window.

Track that window explicitly. A status view that distinguishes approved, queued, relayed and settled prevents the community from assuming a change is live before it is.

Keep the execution path connected: this guide pairs well with onchain audit trail, dao tooling and protocol parameter change, which cover the neighbouring steps between an approved vote and a settled onchain transaction.

Key concepts explained

New to this topic? These are the core terms you will meet again and again in governance work. Understanding them makes every proposal easier to read.

Sequencer governance: Control over the component that orders transactions on a rollup. Whoever governs the sequencer governs censorship resistance itself.
Upgrade key: The key or contract that can change rollup code on L1. Decentralizing it through governance and timelock is the defining milestone of a maturing L2.
Escape hatch: A mechanism letting users withdraw to L1 if the rollup operator misbehaves. Its parameters are themselves a governance decision.
Stage rating: A public classification (Stage 0, 1, 2) of how decentralized a rollup's governance and upgrade process is. Advancing stages is mostly an execution-layer problem.

Frequently asked questions

How is a layer 2 governed?: Through a mix of token holder voting on ecosystem matters and a security council or timelocked upgrade process for the contracts controlling sequencing, bridging and proofs.
Why do rollups need a security council?: Because some failures, such as a broken proof system, need intervention faster than a full vote allows. The council operates under published, bounded powers.
Do L2 governance decisions execute on the base chain?: Often yes. Contracts controlling the bridge and upgrades typically live on the base layer, so an approved change has to be executed there as well.