Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 103 of 189

App-Chains and Rollup-as-a-Service

How Cosmos-style app-chains and modern Rollup-as-a-Service (RaaS) providers (Caldera, Conduit, AltLayer, Gelato) let applications deploy dedicated chains, and the trade-offs vs shared chains.

Beginner
8 min readUpdated November 2026Block Clarity Hub Editorial Team

The basics

The App-Chain Thesis

The app-chain thesis argues high-value applications should run on their own chain rather than sharing block space with other apps. Benefits: customised consensus parameters, sovereign tokenomics, no congestion from unrelated apps, full control over upgrades. This is Cosmos's approach — many sovereign chains interoperating via IBC. Modern rollup-as-a-service (RaaS) has brought a similar model to Ethereum — anyone can deploy a dedicated rollup for their application, benefiting from Ethereum security while having full control over their chain's parameters.

Why RaaS Emerged

Deploying and operating a rollup from scratch is expensive and complex — requires deep infrastructure knowledge, ongoing security work, monitoring systems. RaaS providers (Caldera, Conduit, AltLayer, Gelato, others) offer 'rollup as a service' — spin up a dedicated rollup with a few clicks. They handle sequencer operation, upgrades, monitoring, and infrastructure. Applications pay recurring fees for the service. This dramatically lowers the barrier to launching a dedicated chain — many applications now can deploy app-chains that couldn't before.

Major RaaS Providers

Caldera: chains as a service on more than one stack (ETHBEAT lists both OP Stack chains and Arbitrum Orbit chains, such as ApeChain, as deployed via Caldera); multiple production deployments. Conduit: chain infrastructure for rollups and L1s, now also aimed at institutions, payments and DeFi use cases. AltLayer: Multi-stack support with restaking security via EigenLayer. Gelato: Multi-chain deployment across various stacks. Alchemy Rollups: Alchemy's rollup service. Each has different specialisations and technical approaches. The competition is real; multiple major applications have deployed rollups through various providers.

  • App-chain thesis: high-value apps run own chains
  • RaaS providers make this practical for Ethereum
  • Major providers: Caldera, Conduit, AltLayer, Gelato
  • Applications get customised chain economics without full infrastructure burden

Key Takeaways

  • App-chains give applications customised chain parameters
  • RaaS providers dramatically lower deployment barriers
  • Multiple competing providers with different specialisations
  • Many production app-chains now exist across various providers

Going deeper

OP Stack, ZK Stack, Arbitrum Orbit

RaaS providers work with different underlying frameworks. OP Stack (Optimism): most-adopted framework; base for Zora, World and Mode. Base also launched on it but announced in February 2026 that it is moving to its own stack. ZK Stack (zkSync): ZK rollup framework; its chains form the interoperable ZKsync Elastic Network. Arbitrum Orbit: Arbitrum's L3-and-L2 deployment framework. Polygon CDK: Polygon's chain development kit, now offered as a bespoke product for institutions with built-in Agglayer connectivity rather than a self-serve kit. Each has different technical characteristics and ecosystem alignments. Applications choose based on ecosystem fit, technical requirements, and RaaS provider preferences.

Case Studies of App-Chains

Several notable app-chains illustrate the pattern. dYdX V4: perpetuals moved from StarkEx to a dedicated chain built with the Cosmos SDK and run by its own proof-of-stake validators. Aevo: perpetuals on a dedicated OP Stack rollup. Derive (formerly Lyra): options exchange that ran on a dedicated OP Stack rollup (Derive Chain), which is being wound down after the protocol migrated to Derive V3, a separate system settling on Ethereum. Xai: gaming L3 on Arbitrum Orbit. ApeChain: APE-token community chain on the Arbitrum Orbit stack, deployed via Caldera. Each app-chain claims specific benefits: custom token economics, no congestion from unrelated apps, better user experience for the specific application.

The Fragmentation Cost

App-chains fragment liquidity and users. A user with USDC on Ethereum mainnet who wants to use dYdX V4 must bridge to dYdX chain, use USDC there, potentially bridge back. Each app-chain has its own token, its own liquidity, its own user experience. Cross-chain composability is limited. Aggregation layers (LayerZero, Wormhole, various bridge protocols) partially address this but add cost and risk. Whether app-chain benefits outweigh fragmentation costs depends on the specific application.

Superchain and Elastic Network Coordination

Optimism's Superchain and zkSync's Elastic Network attempt to reduce fragmentation among chains sharing their stacks. Chains in the Superchain will eventually have shared sequencing, native interop, unified user experience. This preserves app-chain benefits while reducing fragmentation costs — a middle-ground design. Whether these coordination layers achieve their promise remains an open question.

Key Takeaways

  • OP Stack dominates by deployment count; ZK Stack, Orbit, CDK compete
  • Notable app-chains: dYdX V4, Aevo, Xai, ApeChain
  • Fragmentation cost is real: split liquidity, users, composability
  • Superchain and Elastic Network coordination attempts to reduce fragmentation

Under the hood

Sequencer Revenue Economics

App-chain economics depend heavily on sequencer revenue. On shared chains (Base, Arbitrum), the chain operator captures sequencer revenue. On app-chains, the application captures it. For high-fee applications (perpetuals, DEX aggregators), sequencer revenue can be substantial for successful chains. dYdX V4's move to its own Cosmos-SDK chain is an example of an application running its own chain instead of sharing block space. The economic case for app-chains rests substantially on this revenue capture.

Restaking-Secured Rollups

AltLayer and others offer restaking-secured rollups via EigenLayer. The rollup's sequencer/prover operations are secured by restaked ETH — if they misbehave, the restaked ETH is slashed. This provides an additional security layer beyond just Ethereum's underlying security. It also creates new economic relationships — rollup operators pay AVSs (Actively Validated Services) for security. Whether restaking-secured rollups achieve substantial adoption remains an open question.

The App-Chain Governance Question

App-chains give applications control over their chain — but also responsibility. Who decides on upgrades? Who controls sequencer operation? What happens if the application team departs? These governance questions have real implications for user protection. Many app-chains are effectively single-team governed with minimal decentralisation. This concentrates power but also concentrates operational responsibility. The trade-offs are real and case-specific.

When App-Chains Make Sense

The heuristic: an app-chain makes sense when the application has (a) substantial revenue that would benefit from capturing sequencer economics, (b) specific technical requirements poorly served by shared chains (custom gas token, block time, throughput needs), and (c) enough capital or usage to sustain the operational burden. High-frequency trading applications, gaming with massive throughput needs, and applications with unique economic models are strong candidates. Simple DeFi applications usually don't benefit enough to justify the overhead.

Evaluating App-Chain Investments

App-chain tokens often accrue value from sequencer revenue capture and application usage. When evaluating: what fraction of application revenue flows to token holders? What is the underlying application's revenue trajectory? How is chain governance structured? What's the competitive position vs shared chains? These fundamental questions drive long-term token value more than headline TVL or user counts.

Key Takeaways

  • Sequencer revenue capture is the primary economic driver for app-chains
  • Restaking-secured rollups add new security layer via EigenLayer
  • Governance is concentrated in application teams; user protection varies
  • App-chains make sense for high-revenue, specific-requirement, sustainable-operation applications
  • Token evaluation should focus on revenue capture mechanics, not just usage metrics

Related Content

Aztec and Railway — Ethereum Privacy Layers

How Aztec's zkRollup and the RAILGUN shielded pool (used through the Railway wallet) approach privacy on Ethereum from different architectural angles, and what shipping ZK-based Ethereum privacy actually looks like.

Lightning Network — Deep Dive

How Lightning's payment channels enable instant Bitcoin transactions, the routing challenges that shape the network's topology, and why LN adoption has grown more slowly than early forecasts suggested.

Liquid Network

How Liquid is a Bitcoin sidechain with faster settlement, confidential transactions, and asset issuance — and where it fits in the Bitcoin scaling ecosystem alongside Lightning.

Validium, Plasma, and State Channels

The scaling designs that lost to rollups — Validium (off-chain data), Plasma (mass exit games), and state channels (bilateral off-chain) — and why understanding them helps make sense of current rollup design.

Cosmos IBC and Interchain Security

How Cosmos IBC enables cross-chain messaging without wrapped assets, how Interchain Security (ICS) let chains rent security from the Cosmos Hub before the Hub removed it in 2026, and what these primitives mean for Cosmos's app-chain thesis.

Polkadot Parachains

How Polkadot's parachain model works — shared security via the Relay Chain, XCM cross-chain messaging, agile coretime — and how the network has evolved from parachain auctions to coretime markets.

RPC Providers Compared

How RPC providers like Alchemy, Infura, QuickNode, and Ankr sit between wallets and blockchains — their business models, reliability differences, censorship risks, and how to think about decentralised alternatives.

Indexers and The Graph

How blockchain indexers turn raw chain data into fast, queryable APIs — The Graph's subgraphs, competing indexers, why every dApp uses one, and how the indexing layer shapes what applications can build.

References & further reading