Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
layer-2-wars-arbitrum-optimism-base-and-beyond
Blog

Why 'Permissionless' Upgrades Are a Governance Fantasy

A technical analysis revealing that true permissionless upgrades are a myth for managed L2s. We dissect the privileged security models of Arbitrum, Optimism, Base, and zkSync, exposing the centralized trade-offs behind decentralized branding.

introduction
THE GOVERNANCE REALITY

The Permissionless Lie

Protocol upgrades marketed as permissionless are, in practice, constrained by social consensus and client diversity, creating a governance bottleneck.

Permissionless is a marketing term. The Ethereum Merge required near-unanimous client team coordination, not a solo developer's code push. Social consensus dictates upgrade timing, not technical capability.

Client diversity creates a veto. A single major client team like Geth or Prysm refusing an EIP halts the entire network. This centralized coordination contradicts the permissionless narrative.

Hard forks require mass migration. Users must upgrade their nodes; validators face slashing risks for non-compliance. This coordination cost is a permissioned governance event disguised as a technical upgrade.

Evidence: The Ethereum Foundation and core developers set the Merge timeline. The DAO fork required a contentious governance vote, proving upgrades are political, not permissionless.

thesis-statement
THE GOVERNANCE REALITY

The Centralized Core of Decentralized Rollups

The promise of permissionless upgrades is a fantasy, as centralized development teams retain ultimate control over core smart contracts and sequencer logic.

Permissionless upgrades are a myth. The core upgrade keys for rollup smart contracts on L1, like the SequencerInbox or L1Bridge, are held by a multi-sig controlled by the founding team. This structure is identical to the admin key risk in early DeFi protocols like Compound or Aave.

Governance is a post-hoc theater. DAO votes for upgrades, as seen in Arbitrum and Optimism, are symbolic. The technical implementation and deployment are executed by the core team, creating a single point of failure that invalidates the decentralized narrative.

Sequencer centralization is the bottleneck. Even with decentralized proposers, the sequencer role remains a centralized service operated by the founding entity (e.g., Offchain Labs, OP Labs). This grants them unilateral power over transaction ordering and censorship, mirroring the miner extractable value (MEV) problems of Ethereum pre-merge.

Evidence: As of 2024, zero major rollups have implemented a trust-minimized, decentralized sequencer set. Proposals like Espresso Systems or Astria remain in testing, while production systems rely on a single entity, creating systemic reorg and liveness risks.

GOVERNANCE FANTASY VS. ON-CHAIN REALITY

L2 Upgrade Mechanism Reality Check

Deconstructing the 'permissionless' narrative by comparing the actual governance and technical control mechanisms for upgrading major L2s.

Governance & Control DimensionOptimism (OP Stack)Arbitrum (Nitro)zkSync EraStarknetBase

Upgrade Initiator

Optimism Foundation Multisig

Arbitrum DAO (via Security Council)

Matter Labs Team Multisig

StarkWare Team Multisig

Base Team (Coinbase) Multisig

Time-Lock Delay Before Execution

0 days

~72 hours (ArbOS upgrades)

0 days

0 days

0 days

On-Chain DAO Vote Required for Upgrade

Can DAO Veto/Cancel a Pending Upgrade?

Upgrade Key Security Council Members

7-of-12 Multisig

12-of-16 Multisig (elected by DAO)

Not Applicable

Not Applicable

Not Applicable

Formalized Escape Hatch / Withdrawal Window

Yes (7-day challenge period)

Yes (Arbitrum One: ~7 days, Nova: ~14 days)

Yes (~30 days for L1->L2, instant for L2->L1)

Yes (~7 days)

Yes (Inherits Optimism's 7-day period)

Proven Historical Centralization Risk Event

Yes (Bedrock upgrade executed by Foundation)

No

Yes (Boojum upgrade executed by team)

Yes (Protocol upgrades executed by team)

Yes (Inherits OP Stack centralization)

deep-dive
THE FANTASY

Deconstructing the Governance Slippery Slope

Protocols that claim to be permissionless inevitably face a governance paradox where a small group of stakeholders controls the upgrade path.

Permissionless is a marketing term. The initial deployment of a smart contract is permissionless, but its subsequent evolution is not. Every upgrade, from Optimism's Bedrock migration to Uniswap's fee switch proposal, requires a governance vote. The code is immutable, but the roadmap is controlled by token holders.

Governance capture is inevitable. The voting power concentration in protocols like Compound and MakerDAO proves that decentralized ideals collapse under capital weight. A whale or VC syndicate with 10-20% of tokens can veto or pass any proposal, making the network's future a function of its largest bagholders.

The multisig is the real governor. Most L1s and L2s, including Arbitrum and Base, retain an upgradeability multisig for emergency interventions. This creates a two-tiered governance system: token-holder theater for optics, and a centralized failsafe for real power. The multisig is the ultimate backdoor.

Evidence: The SushiSwap governance coup demonstrated this. A single entity, Frog Nation, acquired enough voting power to unilaterally replace the entire leadership and treasury strategy, proving that token-weighted voting is just a leveraged buyout mechanism for protocol control.

case-study
WHY 'PERMISSIONLESS' UPGRADES ARE A GOVERNANCE FANTASY

Case Studies in Centralized Control

On-chain governance votes are often theater; real protocol power resides in centralized, off-chain upgrade keys controlled by core teams and VCs.

01

The Uniswap V4 Hook Factory

The 'permissionless' hook ecosystem is gated by a single, centralized factory contract controlled by Uniswap Labs governance. This creates a kill switch for the entire innovation layer.

  • Governance Fantasy: While anyone can propose a hook, the factory owner can blacklist any deployment.
  • Centralized Reality: Uniswap Labs holds the factory owner key, enabling retroactive censorship of any hook.
  • Precedent: Similar to the V3 factory owner, which has been used to block deployments on specific chains.
1
Owner Key
100%
Hook Control
02

Optimism's Security Council Veto

Optimism's Citizen House votes on upgrades, but a 2/3 multisig 'Security Council' can unilaterally veto or execute any proposal, rendering tokenholder votes advisory.

  • The Problem: A ~$40B+ ecosystem relies on a 14-of-21 multisig for final execution.
  • The Solution?: 'Progressive Decentralization' is a roadmap, not a current state. Real upgrade power is highly concentrated.
  • Wider Pattern: Shared by Arbitrum, Polygon, and most L2s, where a centralized 'sequencer' or 'guardian' holds ultimate keys.
2/3
Multisig Veto
~$40B+
TVL at Risk
03

MakerDAO's Endgame Illusion

Maker's complex 'Endgame' restructuring concentrates power into smaller, VC-heavy 'SubDAOs' (Spark, Scope) while diluting the influence of MKR tokenholders.

  • Governance Fantasy: MKR votes on high-level meta-governance, but daily operations and treasury allocation are delegated to appointed SubDAOs.
  • Centralized Reality: SubDAOs are initially governed by core unit multisigs and venture backers like a16z.
  • Result: The illusion of decentralization masks a shift of operational control to insiders.
6
Core Units
~$8B
RWA Exposure
04

The Lido DAO Staking Monopoly

Lido controls ~30% of all staked ETH, but its governance is dominated by whale voters (VCs, foundations) and a staking operator cartel, creating systemic risk.

  • The Problem: LDO token distribution is highly concentrated; top 10 addresses control >60% of voting power.
  • The Solution?: 'Dual Governance' with stETH is proposed but unimplemented. Current upgrades are dictated by a small cabal.
  • Wider Impact: This centralization threatens the Ethereum consensus layer, prompting calls for client diversity and governance limits.
~30%
ETH Stake Share
>60%
Voter Concentration
counter-argument
THE GOVERNANCE REALITY

Steelman: "But the DAO Votes!"

On-chain governance creates the illusion of permissionless upgrades while centralizing power in a small, non-representative group.

Token-weighted voting is plutocratic. A protocol's upgrade path is not permissionless if control is gated by capital. The whale with the most tokens decides the network's future, not the most qualified developer or active user. This is the governance model of Compound, Uniswap, and Aave.

Voter apathy guarantees capture. Low participation rates make governance a low-cost attack surface. A malicious actor needs to sway only a small, disengaged electorate. The Lido DAO's 2% quorum for critical decisions is a systemic risk, not a feature.

Delegation creates political parties. Users delegate to representatives like Gauntlet or StableLab, creating centralized points of failure. This recreates traditional corporate board dynamics inside the DAO, negating the permissionless ideal. The delegate, not the token holder, possesses the upgrade key.

Evidence: The Maker Endgame. MakerDAO's transition to SubDAOs and locked governance tokens explicitly acknowledges that 'permissionless' governance failed. The protocol is now architecting explicit, centralized veto power to prevent hostile takeovers, proving the initial model was fantasy.

takeaways
GOVERNANCE REALITY CHECK

Key Takeaways for Builders & Investors

The promise of on-chain governance for seamless, permissionless upgrades is a dangerous fantasy; here's what actually matters for protocol survival.

01

The 'Code is Law' Fallacy

Smart contract immutability is a security feature, not a bug. Treating upgrades as a routine governance vote introduces catastrophic systemic risk.

  • Key Risk: A single malicious or buggy proposal can drain $1B+ TVL in minutes.
  • Key Insight: True permissionlessness requires social consensus forks (e.g., Ethereum/ETC), not on-chain votes.
>99%
Voter Apathy
$1B+
Risk per Vote
02

The Sovereign Appchain Escape

Projects like dYdX and Cosmos appchains explicitly reject L1 governance for upgrades, opting for full technical sovereignty.

  • Key Benefit: Upgrades are developer-led operations, not political campaigns, enabling ~1-week iteration cycles.
  • Key Trade-off: Users must actively opt-in to new chains, fragmenting liquidity and community.
~7 days
Upgrade Cycle
High
Sovereignty Cost
03

The Upgrade Gatekeeper Imperative

Successful protocols like Uniswap and Compound use timelocks, multisigs, and delegate thresholds to make upgrades permissioned at the execution layer.

  • Key Mechanism: A 7-day timelock allows users to exit before any change, creating a market-driven safety net.
  • Key Reality: Final authority rests with a ~10-person developer multisig, not token holders.
7 days
Standard Timelock
~10
Key Holders
04

L2s: The Centralization/Upgrade Paradox

Optimism, Arbitrum, and zkSync have upgradeable proxies controlled by centralized 'Security Councils'. This is a feature for rapid iteration, not a bug.

  • Key Tension: To compete on performance, L2s sacrifice short-term decentralization, creating trusted upgrade paths.
  • Key Metric: The time-to-decentralize roadmap is the critical investment thesis.
5/8
Multisig Threshold
2+ years
Decentralization ETA
05

Forkability as the Ultimate Governance

The only truly permissionless 'upgrade' is a fork. Uniswap v3 licenses show that defensibility shifts from code to ecosystem and brand.

  • Key Benefit: Forks like PancakeSwap validate market demand and create competitive pressure.
  • Key Insight: Protocol value accrues to the liquidity and community, not the immutable contract address.
$2B+
Forked TVL
0
Code Barriers
06

Builders: Architect for Obsolescence

Design systems where components can be sunset and replaced via module migration, not monolithic upgrades. Learn from Cosmos SDK and EIP-2535 Diamonds.

  • Action: Use proxy patterns that allow swapping logic for specific functions without full-contract replacement.
  • Action: Treat governance as a coordination tool for migration, not a sudo command.
Modular
Design Goal
Low
Upgrade Blast Radius
ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
Why Permissionless Upgrades Are a Governance Fantasy | ChainScore Blog