Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
the-ethereum-roadmap-merge-surge-verge
Blog

Rollup Teams Maintain More Infrastructure Than Expected

The promise of rollups was to inherit Ethereum's security while offloading execution. The reality is a sprawling, expensive operational burden that challenges the modular thesis. This is the infrastructure tax of L2 scaling.

introduction
THE INFRASTRUCTURE BURDEN

The Modular Mirage

Rollup teams are discovering that modularity shifts, rather than eliminates, the core infrastructure burden.

Rollups own the data layer. The modular thesis promised specialization, but rollups like Arbitrum and Optimism now operate their own sequencers and manage data availability on Celestia or EigenDA. This is a full-stack operation, not a simple smart contract deployment.

The interoperability tax is real. A rollup must integrate with Across, Stargate, and LayerZero for cross-chain liquidity. Each bridge adds security assumptions and engineering overhead, creating a fragmented integration surface that monolithic chains like Solana avoid.

Sequencer decentralization is a multi-year project. Current rollups run centralized sequencers for performance. Decentralizing this component, as seen with Espresso Systems or Astria, requires building a consensus layer and a validator network, which is L1-level complexity.

Evidence: The OP Stack codebase has over 50 repositories. Maintaining a production-grade rollup with fraud proofs, indexers, and cross-chain messaging is comparable to running a small L1, contradicting the 'plug-and-play' modular narrative.

CENTRALIZATION RISK AUDIT

The Rollup Infrastructure Matrix: Who Runs What?

A first-principles breakdown of critical infrastructure control for leading rollups, revealing hidden centralization vectors beyond the sequencer.

Infrastructure ComponentArbitrum (Nitro)Optimism (OP Stack)zkSync EraStarknetBase

Sequencer Control

Offchain Labs

OP Labs

Matter Labs

StarkWare

Base (Coinbase)

Proposer/Prover (ZK)

N/A

N/A

Matter Labs

StarkWare

N/A

Data Availability (Primary)

Ethereum Calldata

Ethereum Calldata

Ethereum Calldata

Ethereum Calldata

Ethereum Calldata

Bridge Guardians/Multisig

9-of-12 Multisig

2-of-4 Multisig

Security Council

10-of-16 STARK Multisig

Base (Coinbase)

Upgrade Delay (Timelock)

~10 days

None

10 days

None

None

Client Diversity (Execution)

Single (Nitro Geth Fork)

op-geth, op-reth (Emerging)

Single (ZK Stack)

Single (Pathfinder, Juno)

op-geth

Proposer Decentralization (Stage)

Stage 1: Training Wheels

Stage 0: Training Wheels

Stage 0: Training Wheels

Stage 0: Training Wheels

Stage 0: Training Wheels

Can Force TX Inclusion?

deep-dive
THE ARCHITECTURAL TRAP

Why The Burden Persists: First-Principles Analysis

Rollups inherit the full-stack complexity of L1s while adding new, unsolved layers of infrastructure.

Sequencer centralization is temporary. The initial design outsources block building and ordering to a single, trusted operator for speed. This creates a technical and economic dependency that teams cannot sunset without solving decentralized sequencing, a problem as hard as L1 consensus.

Data availability is a persistent cost center. Even with validiums or EigenDA, rollups must orchestrate a multi-provider system. This requires continuous integration, monitoring, and fallback logic for Celestia, Avail, and Ethereum—a new ops burden L1s never had.

Proving infrastructure is non-trivial. Teams must manage prover hardware, fraud proof watchers, or ZK circuit upgrades. This is a specialized devops stack distinct from node operations, requiring expertise in Risc Zero, SP1, or custom provers.

Evidence: Arbitrum, Optimism, and zkSync still operate their primary sequencers and provers. Their roadmaps show decentralization timelines measured in years, not months, confirming the burden's persistence.

risk-analysis
THE INFRASTRUCTURE TRAP

Centralization Vectors & Systemic Risks

Rollups promised decentralization but have recreated single points of failure in their core operational stack.

01

The Sequencer Monopoly

The sequencer is a centralized profit center and a critical liveness dependency. Most rollups run a single, permissioned sequencer operated by the core team, creating a single point of censorship and failure.\n- Liveness Risk: If the sequencer goes down, the chain halts for all users.\n- MEV Capture: Teams control the ordering of all transactions, creating a massive, opaque revenue stream.

>95%
Centralized
~0s
Finality Lag
02

Prover Centralization

Zero-knowledge rollups like zkSync Era and Starknet outsource proving to centralized, team-operated provers. This creates a verification bottleneck and reintroduces trust.\n- Trust Assumption: Users must trust the team's prover is honest.\n- Cost & Speed: Proving is computationally intensive, creating high barriers to permissionless participation and limiting decentralization roadmaps.

Specialized HW
Barrier
1-of-N
Trust Model
03

The Upgrade Key Dilemma

Rollups use proxy upgrade patterns for their core contracts (e.g., L1 Bridge, Verifier). A multi-sig controlled by the team holds the power to arbitrarily change contract logic, freeze funds, or mint tokens. This is a systemic risk for $10B+ in bridged assets.\n- Time-Lock Theater: Many implement timelocks, but governance is still centralized.\n- Bridge Risk: The canonical bridge is the ultimate custodian, not a trustless protocol.

5/8 Multisig
Typical Control
$10B+ TVL
At Risk
04

Data Availability Reliance

Optimistic and Validium rollups are completely dependent on their chosen Data Availability (DA) layer. Using a centralized DA solution like a DAC (Data Availability Committee) or a single Celestia sequencer reintroduces a liveness assumption. If DA fails, the chain cannot reconstruct its state and funds are frozen.\n- Validium Trap: Security downgraded to committee honesty.\n- Systemic Coupling: Failure of a major DA layer could cascade across multiple rollup ecosystems.

7-10 Members
Typical DAC Size
~100%
Liveness Dep.
05

RPC & Indexer Bottlenecks

End-user access is gated by centralized RPC endpoints and indexers, often operated by the rollup team or a single provider like Alchemy or Infura. This creates metadata surveillance risks and liveness dependencies distinct from the chain itself.\n- Censorship Vector: RPC providers can filter or block transactions.\n- Performance Single Point: Downtime for the primary RPC cripples dApp UX across the ecosystem.

<5 Providers
Dominant RPCs
~200ms
Latency Variance
06

The Shared Sequencer Illusion

Proposed solutions like Espresso, Astria, or Radius aim to decentralize sequencing. However, they risk creating a new centralized layer that multiple rollups depend on, transforming chain-level risk into ecosystem-wide risk. Atomic cross-rollup composability depends entirely on this new sequencer's liveness and honesty.\n- Meta-Game Theory: Incentives may lead to re-centralization.\n- Cascading Failure: A bug or attack on the shared sequencer halts all connected rollups.

1 Layer
New SPOF
N Chains
Impact Scale
future-outlook
THE INFRASTRUCTURE TRAP

The Path to True Modularity: Shared Sequencers & DA Layers

Rollup teams are discovering that outsourcing execution does not eliminate operational complexity, creating a market for shared infrastructure.

Rollups are not infrastructure-free. The modular thesis promised specialization, but teams still manage sequencer nodes, RPC endpoints, and cross-chain messaging. This operational overhead negates the core benefit of focusing solely on application logic.

Shared sequencers are inevitable. Dedicated sequencers are a single point of failure and create maximal extractable value (MEV) leakage. Networks like Espresso Systems and Astria provide neutral, decentralized sequencing that rollups like dYdX V4 are adopting for credible neutrality and MEV resistance.

Data Availability (DA) is the real bottleneck. Using Ethereum for DA is secure but expensive. Alternatives like Celestia, EigenDA, and Avail offer cost reductions of 10-100x, forcing a trade-off between economic security and scalability that each rollup must explicitly choose.

Evidence: The Arbitrum DA cost for a 100KB batch is ~0.003 ETH. The same batch on Celestia costs ~$0.01. This 100x+ cost differential is the primary driver for modular DA adoption, proving that execution is no longer the scaling constraint.

takeaways
THE INFRASTRUCTURE TRAP

TL;DR for Builders and Investors

The modular thesis promised specialization, but rollup teams are drowning in undifferentiated, high-risk infra work.

01

The Sequencer Monopoly Problem

Running your own sequencer means managing real-time consensus, transaction ordering, and MEV capture. The operational overhead is immense and centralizes risk.\n- ~$500k+ annual cost for a high-availability, geo-distributed setup\n- Single point of failure for your chain's liveness and censorship resistance\n- Lost revenue from inefficient MEV extraction vs. specialized networks like Espresso or Astria

99.9%
Uptime Required
500ms
Latency Target
02

Data Availability is a Full-Time Job

Integrating and maintaining a Data Availability (DA) layer like Celestia, EigenDA, or Avail is not plug-and-play. It requires deep protocol-specific engineering for fraud proofs, data sampling, and long-term archival.\n- Weeks of integration work per DA provider, locking you into their roadmap\n- Ongoing cost optimization battle between blob space, call data, and security budgets\n- Complex trust assumptions shift from Ethereum to a newer, less battle-tested system

~$100K
Initial Integration
-90%
Cost vs. Calldata
03

The Bridge & Prover Maintenance Burden

Every rollup must build and secure its own canonical bridge, a high-value attack vector historically responsible for $2B+ in exploits. Managing upgradeable contracts, multi-sigs, and fraud/zk proof verification is a constant security crisis.\n- Dedicated security team required to monitor and respond to bridge threats\n- Liquidity fragmentation as users get trapped by poorly designed bridge UX\n- Prover dependency on teams like RiscZero or Succinct adds another critical external failure point

$2B+
Bridge Exploits
24/7
Security Ops
04

The Shared Sequencer Opportunity

Shared sequencer networks like Espresso, Astria, and Radius are the logical endpoint. They turn a capital-intensive liability into a utility, offering decentralized sequencing, cross-rollup atomic composability, and optimized MEV revenue.\n- Instant liveness and censorship resistance from a distributed validator set\n- Atomic cross-rollup arbitrage unlocks new DeFi primitives\n- Revenue share model turns sequencing cost into a potential income stream

0
Sequencer DevOps
+Revenue
MEV Share
05

Rollup-as-a-Service (RaaS) is the New Baseline

Platforms like Conduit, Caldera, and Gelato RaaS abstract the entire stack. They provide a managed service for the rollup client, prover network, bridge, and explorer, letting teams focus on application logic.\n- Go-to-market in days, not months, with a production-ready chain\n- Automatic upgrades for core stack (OP Stack, Arbitrum Orbit, Polygon CDK)\n- Unified dashboard for monitoring, analytics, and managing key infra providers

<1 Week
Chain Launch
-80%
Dev Time
06

The Investor Lens: Infra Debt is a Valuation Killer

Investors are now discounting rollups that own their entire stack. The market rewards capital efficiency and developer focus. The winning teams will be those that outsource non-core infra to best-in-class specialists.\n- Due diligence must audit the infra roadmap and dependency risks\n- Valuation premium for teams using RaaS + Shared Sequencer + Ethereum for settlement\n- Long-term liability of a custom stack outweighs short-term control benefits

10x
Focus Multiplier
High
Infra Risk
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 direct pipeline
Rollup Infrastructure Burden: The Hidden Cost of L2 Scaling | ChainScore Blog