The blockchain scaling debate has evolved beyond simple L1 vs L2 comparisons. Understanding the difference between L3 architectures and aggregated L2s is critical for evaluating which chains will capture value and which will become commoditized infrastructure.
The Rollup Business Model
Before diving into L3s and aggregation, we need to understand how rollups actually make money. The rollup business model has four key components:
1. Sequencing
Function: Order transactions, build blocks
This is where rollups capture most of their value today. The sequencer:
- Receives user transactions
- Orders them (usually first-come-first-served, but can extract MEV)
- Builds blocks and publishes to the DA layer
Revenue: Transaction fees minus DA costs. Priority fees and MEV are bonus income.
2. Execution
Function: Run computations, update state
Execution involves:
- Processing transactions against the current state
- Computing state transitions
- Generating execution traces for proving
Revenue: Gas fees from computation (minimal compared to sequencing).
3. Proposing
Function: Publish state roots to L1
The proposer:
- Submits claims about the rollup's state to the settlement layer
- For optimistic rollups: anyone can challenge incorrect claims
- For ZK rollups: proofs verify correctness
4. Proving
Function: Generate validity/fraud proofs
Provers:
- Generate cryptographic proofs of correct execution (ZK)
- Or monitor for fraud and submit challenges (Optimistic)
Revenue = Sequencer fees + MEV
Costs = Data availability + Settlement + Proving
DA is the dominant cost (~95%). Cheap DA = higher margins for rollups.
What are Layer 3s?
Layer 3s (L3s) are rollups that settle on Layer 2s instead of directly on Ethereum L1. They add another layer to the stack:
| Layer | Example | Settles On |
|---|---|---|
| L1 | Ethereum | - |
| L2 | Arbitrum One, Base, Optimism | Ethereum L1 |
| L3 | Xai, Degen Chain, Proof of Play | L2 (e.g., Arbitrum) |
Why Build on L3?
- Cheaper DA: L2s have cheaper blockspace than L1, so L3s posting data to L2s pay less
- Customization: L3s can optimize for specific use cases (gaming, social, trading)
- Ecosystem alignment: Inherit security and liquidity from a specific L2
- Simpler settlement: Faster finality using L2 as the trust anchor
L3 Framework Comparison
Arbitrum Orbit
Arbitrum's L3 framework allows chains to settle on Arbitrum One or Nova.
- Technology: Same Nitro stack as Arbitrum One
- DA Options: AnyTrust (DAC), Ethereum calldata, or Celestia
- Customization: Custom gas tokens, privacy features, throughput optimization
- Settlement: Proofs posted to Arbitrum One
- Examples: Xai (gaming), Proof of Play (gaming), Degen Chain
OP Stack Superchain
Optimism's vision for a unified network of OP Stack chains.
- Technology: Standardized OP Stack with shared sequencing
- Interoperability: Native cross-chain messaging between Superchain members
- Revenue sharing: Chains contribute to Optimism Collective
- Members: Base, Zora, Mode, Worldchain
- Future: Shared sequencer for atomic cross-chain transactions
ZKSync ZK Chains (formerly Hyperchains)
ZK rollups that settle on ZKSync Era.
- Technology: ZK Stack with shared prover
- Settlement: Proofs verified on ZKSync Era (which settles to Ethereum)
- Benefit: Proof aggregation reduces costs
- Status: Earlier stage than Orbit/Superchain
Polygon CDK & Supernets
Polygon's framework for building ZK-powered chains.
- Technology: Choice of zkEVM (Polygon) or custom VM
- DA Options: Validium (DAC), Ethereum, Celestia
- Settlement: Proofs aggregated via AggLayer
- Focus: Enterprise and institutional adoption
L3 Economics: The Profitability Challenge
While L3s offer technical benefits, their economic viability is complex:
Revenue Sources
- Sequencer fees: Transaction fees from users
- MEV: Extractable value (if any)
- Native token value: If using custom gas token
Cost Structure
- DA costs: Posting data to L2 (or alt-DA)
- Settlement costs: Proving to L2
- Infrastructure: Sequencer, RPC nodes, indexers
- Security: Bug bounties, audits
The Margin Squeeze
L3s face pressure from multiple directions:
- L2s getting cheaper (EIP-4844 reduced L2 costs 10-100x)
- Competition drives fees down
- Alt-DA makes "cheap DA" less of a differentiator
- Users expect near-zero fees
L3s make sense when you need application-specific optimization that justifies the infrastructure costs. Gaming chains with millions of players, high-frequency trading venues, or social apps with unique requirements may find L3 economics work. Generic "cheap chain" L3s will struggle.
Aggregated L2s: The Alternative Architecture
Instead of building vertically (L3 on L2 on L1), aggregated L2s connect horizontally at the L2 level with shared infrastructure.
Key Differences
| Property | L3 Architecture | Aggregated L2 Architecture |
|---|---|---|
| Settlement | Settles on L2 | Settles directly on L1 |
| Security | Inherits from L2 (which inherits from L1) | Direct L1 security |
| Interoperability | Through L2 bridge | Native via aggregation layer |
| Latency | L3 + L2 + L1 finality | L2 + L1 finality |
| Proof Cost | Pays L2 for verification | Aggregated proofs to L1 |
Polygon AggLayer Deep Dive
AggLayer is Polygon's answer to the fragmentation problem. Instead of isolated chains, AggLayer creates a unified network of ZK-connected chains.
Core Components
1. Unified Bridge
A single bridge contract on Ethereum that:
- Holds all assets for connected chains
- Enables cross-chain transfers without withdrawing to L1
- Maintains a global exit tree for all chains
2. Pessimistic Proofs
The security innovation at the heart of AggLayer:
- Problem: A malicious chain could steal funds by forging cross-chain messages
- Solution: Pessimistic proofs verify that chains only withdraw what they deposited
- Mechanism: Tracks accounting balance per chain; rejects withdrawals exceeding deposits
3. Proof Aggregation
Multiple chain proofs combined into single L1 submission:
- Reduces per-chain settlement costs
- Enables shared security across chains
- More chains = lower per-chain costs
AggLayer Architecture
The aggregation flow:
- Local execution: Each chain processes transactions locally
- Proof generation: Chain generates ZK proof of state transition
- Aggregation: AggLayer combines proofs from multiple chains
- Settlement: Single aggregated proof submitted to Ethereum
- Bridge updates: Unified Bridge state updated atomically
Security Properties
- Isolation: Bad chain can't harm other chains' funds
- Soundness: Invalid state transitions rejected by ZK proofs
- Liveness: Chains can exit independently if aggregator fails
- Censorship resistance: L1 escape hatch always available
L3s vs Aggregated L2s: When to Use Each
Choose L3 When:
- You need tight integration with a specific L2 ecosystem
- Your app benefits from L2's existing liquidity/users
- Custom execution environment is required
- You want simpler deployment (inherit L2 security)
Choose Aggregated L2 When:
- Direct L1 security is important
- You need interoperability with many chains
- Settlement latency matters (fewer hops)
- You're building infrastructure others will use
The Scaling Roadmap
Current State (2026)
- L2s: Dominant scaling solution, maturing rapidly
- L3s: Emerging for app-specific chains
- Aggregation: Early deployment (AggLayer, Superchain)
Near-Term Evolution
- Shared sequencing: Multiple chains sharing block production
- Proof aggregation: Combining proofs across ecosystems
- Native interop: Cross-chain transactions without bridges
Long-Term Vision
- Unified liquidity: Assets move freely across chains
- Chain abstraction: Users don't see individual chains
- Specialized execution: Different VMs optimized for use cases
The value will accrue to layers that solve the interoperability problem while maintaining security. Watch for:
- Aggregation layers that gain network effects
- L3 frameworks with strong developer traction
- Cross-chain protocols enabling seamless UX
Key Takeaways
- Rollup economics: Sequencing captures value; DA is the main cost
- L3s: Rollups on rollups, optimized for specific use cases
- Aggregation: Horizontal scaling connecting L2s directly
- Security models differ: L3 inherits from L2; aggregated L2s get direct L1 security
- The future is multi-chain: Both approaches will coexist, serving different needs