Rollup Stages (0, 1, 2) Explained by L2BEAT

Definition

L2BEAT, a prominent analytics and research platform for Ethereum Layer 2 scaling solutions, introduced a framework known as Rollup Stages to assess the maturity and decentralization of various rollups. This framework categorizes rollups into three distinct stages – Stage 0, Stage 1, and Stage 2 – based on their reliance on centralized components and the extent to which they have minimized trust assumptions. The primary goal of the Stages framework, first introduced in June 2023, is to provide clear and simple indicators of a rollup's maturity, measured through its level of decentralization and trust minimization. It was inspired by Vitalik Buterin's proposed milestones for rollup development, aiming to guide the transition of rollups from early reliance on "training wheels" (operator control) to fully inheriting the security properties of the base layer, Ethereum. The rough intuition is that Stage 0 represents a project fully controlled by a few entities, Stage 2 represents a project fully controlled by code, and Stage 1 is something in between. It is crucial to understand that the Stages Framework primarily discusses the maturity of a rollup in terms of decentralization and trust minimization, not in terms of security against potential bugs or fundamental protocol flaws. If a project is assumed to be bug-free, then the Framework can be seen as a measure of security against permissioned actors.

Key Takeaway

The L2BEAT Rollup Stages framework provides a standardized and dynamic method to evaluate the maturity of Layer 2 rollups, primarily focusing on their level of decentralization and the reduction of reliance on trusted operators over time. By categorizing rollups into Stage 0, Stage 1, and Stage 2, the framework offers a clear progression path, where higher stages indicate greater trust minimization, enhanced censorship resistance, and a more complete inheritance of security properties from the underlying Layer 1 blockchain, Ethereum. This framework is an essential tool for understanding the evolving security and governance landscape of the Layer 2 ecosystem.

Mechanics

The L2BEAT Stages framework delineates a clear progression path for rollups, moving from a highly centralized, operator-controlled state to a fully decentralized, code-governed system. Each stage represents a significant step in reducing trust assumptions and enhancing the security inheritance from Ethereum.

Stage 0 — Full Training Wheels: At Stage 0, the rollup is effectively run by its operators, meaning a small group of entities or a multi-signature wallet has significant control over critical functions. This control often includes the ability to upgrade the rollup's smart contracts on Ethereum, potentially without a time delay or a robust escape hatch for users. While there is typically source-available software that allows for the reconstruction of the state from data posted on L1, this is primarily used to compare state roots with the proposed ones, rather than for permissionless fraud proving. Projects in this stage often rely on a security committee, managed by a multi-signature, which possesses the power to forcibly upgrade the rollup contract in emergencies or interfere with the L2 state hash recorded in the contract. This level of control means that users must place a high degree of trust in the operators to act honestly and competently. Examples include many optimistic rollups that have not yet launched a fully permissionless fraud proof system, or L2s that implement data availability (DA) under the ETH chain or lack mandatory withdrawal/transaction functions that can be invoked at any time, such as Immutable X or Starknet, as highlighted by L2BEAT's risk metrics.

Stage 1 — Limited Training Wheels: In Stage 1, the rollup transitions to being governed more by smart contracts, significantly reducing the reliance on operator control. A key characteristic of this stage is the implementation of a permissionless fraud proof system (for optimistic rollups) or a robust validity proof system (for ZK-rollups) that is fully operational and accessible to anyone. This means that any user can submit a proof to challenge an invalid state transition or verify a valid one, without needing permission from the rollup operators. Furthermore, users are given ample time to exit the rollup in the event of unwanted upgrades or malicious operator behavior, often through a forced withdrawal mechanism. While Stage 1 represents a substantial leap towards decentralization, some centralized components or upgrade mechanisms might still exist, albeit with reduced power compared to Stage 0. Defining the exact requirements for being "in between" Stage 0 and Stage 2 is a major challenge of the Stages Framework, but L2BEAT has made extensive efforts to provide a clear and objective set of criteria for this transition.

Stage 2 — No Training Wheels: Stage 2 represents the ultimate goal for rollups: a state where the project is fully controlled by code, with minimal to no reliance on trusted operators. At this stage, the rollup fully inherits the security properties of the base layer, Ethereum, without any significant trust assumptions on external entities. All critical functions, including upgrades, state transitions, and withdrawals, are permissionless, trust-minimized, and governed by the protocol's smart contracts. There are no centralized backdoors, multi-signatures with override capabilities, or emergency committees that can unilaterally alter the rollup's state or censor transactions. Achieving Stage 2 requires significant technological advancements, robust decentralized governance, and a proven track record of secure operation. As of the current landscape, no rollups have yet reached Stage 2, underscoring its aspirational nature and the complexity involved in achieving such a high degree of decentralization and trust minimization.

Trading Relevance

Understanding L2BEAT's Rollup Stages framework is highly relevant for traders and investors navigating the Layer 2 ecosystem, as it provides critical insights into the underlying security and decentralization posture of various rollup projects. A rollup's stage directly correlates with its trust assumptions and potential counterparty risks. Projects in higher stages (Stage 1 or aspiring to Stage 2) are generally perceived as more robust, secure, and censorship-resistant, making them potentially more attractive for long-term capital deployment, significant liquidity provision, or holding native tokens. This perception can influence investor confidence, drive adoption, and ultimately impact the valuation and stability of a rollup's associated token or ecosystem. Traders performing due diligence can use the L2BEAT stages as a fundamental metric to assess the maturity of a project beyond mere market capitalization or transaction volume.

Furthermore, the stages framework helps traders evaluate the operational risks associated with using a particular L2 for their trading activities, such as swapping tokens, providing liquidity to DeFi protocols, or participating in NFT marketplaces. A Stage 0 rollup, while offering scalability, carries inherent risks due to the significant control held by its operators. This control could manifest as the ability to implement unexpected upgrades, censor transactions, or even potentially freeze user funds in extreme scenarios. For traders, this translates to a higher operational risk profile, which might necessitate smaller position sizes or a preference for more mature, higher-stage rollups for critical operations. Conversely, a rollup progressing from Stage 0 to Stage 1 signals a reduction in these centralized risks, potentially opening up new opportunities for traders seeking more secure and trust-minimized environments. This knowledge is crucial for informed risk management and strategic decision-making in the fast-evolving Layer 2 landscape.

Risks

While the L2BEAT Rollup Stages framework is invaluable for assessing decentralization, it also highlights several inherent risks, particularly for rollups in the earlier stages. Understanding these risks is crucial for users and developers alike.

Centralization and Operator Control Risks (Stage 0 & 1): The most significant risk in Stage 0, and to a lesser extent in Stage 1, stems from the high degree of control exercised by rollup operators. In Stage 0, operators often have the unilateral ability to upgrade smart contracts, potentially without sufficient time delays or user escape hatches. This power can be abused for malicious purposes, such as censoring transactions, freezing user funds, or even altering the rollup's state. Even if operators are benevolent, this centralization creates a single point of failure, making the rollup vulnerable to regulatory pressure, hacks targeting the operator's infrastructure, or internal collusion. The reliance on multi-signature wallets for critical operations, while better than a single key, still concentrates power in a small group, which may not always act in the best interest of all users.

Upgradeability and Exit Risks: The ability to upgrade rollup contracts, especially in Stage 0, poses a direct risk to user sovereignty and fund security. If a malicious or unwanted upgrade is implemented, users might not have adequate time or permissionless mechanisms to withdraw their assets to the Layer 1 blockchain. While Stage 1 introduces "ample time to exit," the definition of "ample" can be subjective, and users might still face challenges if an upgrade is contentious or if the underlying Layer 1 is congested. The absence of fully permissionless and trust-minimized exit mechanisms means that users are, to some extent, at the mercy of the operators' decisions and the protocol's design for emergency withdrawals.

Misinterpretation of Security: A critical risk lies in the potential misinterpretation of the Stages framework as a holistic measure of security. The framework explicitly states that it evaluates maturity in terms of decentralization and trust minimization, not in terms of security against smart contract bugs or fundamental protocol vulnerabilities. A rollup in Stage 2, while highly decentralized, could still harbor critical bugs in its codebase that could lead to exploits and loss of funds. Conversely, a well-audited Stage 0 rollup might be considered more secure against certain types of technical flaws than a less-audited Stage 1 rollup. Users and traders must therefore combine the L2BEAT Stages assessment with other security analyses, such as code audits, bug bounty programs, and formal verification efforts, to form a comprehensive understanding of a rollup's overall risk profile. Relying solely on the stage rating for security assessment can lead to a false sense of security.

History and Examples

The L2BEAT Rollup Stages framework was officially introduced in June 2023. Its development was a direct response to the growing complexity and diversity within the Layer 2 ecosystem, aiming to provide a standardized and objective method for evaluating the maturity of various rollup solutions. The framework draws inspiration from earlier discussions and proposed milestones by prominent figures in the Ethereum community, most notably Vitalik Buterin, who outlined a vision for rollups to gradually shed their "training wheels" and fully inherit Ethereum's security.

Stage 0 Examples: Many rollups, particularly in their early development phases, begin at Stage 0. This category includes projects where operators maintain significant control over the protocol's critical functions. For instance, many optimistic rollups initially fall into Stage 0 if they have not yet fully implemented or activated a permissionless fraud proof system. L2BEAT's risk analysis often points to projects like Immutable X or Starknet as examples that, due to specific design choices such as implementing data availability (DA) under the ETH chain or relying on multi-signature committees for contract management and emergency upgrades, exhibit characteristics of Stage 0. These rollups prioritize rapid development and functionality, often at the expense of immediate full decentralization, with a roadmap to progress to higher stages.

Stage 1 Examples: Rollups that have successfully transitioned to Stage 1 have made significant strides in decentralizing their operations and minimizing trust assumptions. A key requirement for Stage 1 is the presence of a fully operational and permissionless fraud proof system (for optimistic rollups) or a robust validity proof system (for ZK-rollups), coupled with mechanisms that allow users ample time to exit in case of unwanted upgrades. While L2BEAT continuously updates its classifications, projects like Arbitrum have been actively working towards and are often cited as examples of rollups that are either in Stage 1 or are making substantial progress towards it, by implementing decentralized governance and enhancing their fraud proof mechanisms. The journey to Stage 1 involves a complex interplay of technical implementation, community engagement, and governance evolution.

Stage 2 Examples: As of the current state of the Layer 2 ecosystem, no rollup has yet achieved Stage 2. This highlights the ambitious nature of Stage 2, which represents the pinnacle of decentralization and trust minimization. To reach Stage 2, a rollup must be entirely controlled by its code, with no centralized entities capable of overriding its operations, censoring transactions, or unilaterally upgrading its contracts. All critical functions must be permissionless and fully secured by the underlying Layer 1. The path to Stage 2 involves overcoming significant technical and governance challenges, including fully decentralizing sequencers, provers, and upgrade mechanisms, ensuring robust censorship resistance, and establishing a truly community-driven governance model. Stage 2 remains an aspirational goal, driving innovation and development across the entire Layer 2 landscape.

Common Misunderstandings

Despite its clarity and utility, the L2BEAT Rollup Stages framework is sometimes subject to common misunderstandings that can lead to incorrect conclusions about a rollup's overall status.

Stages Equate to Overall Security: One of the most prevalent misconceptions is that a higher stage automatically implies a rollup is "more secure" in every conceivable aspect. While the framework is a measure of security against permissioned actors and centralization risks, it does not directly assess security against smart contract bugs, protocol design flaws, or economic vulnerabilities. A Stage 0 rollup with a meticulously audited and battle-tested codebase might, in certain contexts, be considered more resilient to technical exploits than a Stage 1 rollup with a newly deployed, less-audited fraud proof system. Users must understand that the Stages framework is a specific lens through which to view security, focusing on trust minimization, and should be complemented by other security assessments like code audits, formal verification, and bug bounty programs.

Static Classification: Another misunderstanding is that a rollup's stage classification is static and permanent. In reality, the stages are dynamic. Rollup projects are continuously evolving, implementing new features, decentralizing components, and refining their governance models. A rollup classified as Stage 0 today might actively work towards and achieve Stage 1 in the future by deploying a permissionless fraud proof system or decentralizing its upgrade mechanism. Conversely, a rollup could theoretically revert to a lower stage if critical decentralized components are temporarily disabled, centralized, or if governance decisions introduce new points of control. L2BEAT regularly updates its classifications to reflect these ongoing developments, emphasizing that the stages represent a snapshot in time of a project's maturity.

Exclusivity to Optimistic Rollups: While the concept of fraud proofs is central to optimistic rollups and often discussed in the context of stages, the framework is not exclusive to them. ZK-rollups also have stages of maturity, even though their security model relies on cryptographic validity proofs rather than fraud proofs. For ZK-rollups, the stages assess aspects like the decentralization of their provers, the permissionlessness of their upgrade mechanisms, the robustness of their data availability solutions, and the extent to which their validity proofs are generated and verified in a trust-minimized manner. The specific criteria might differ slightly, but the underlying principle of evaluating decentralization and trust minimization remains consistent across both optimistic and ZK-rollup architectures.

Summary

The L2BEAT Rollup Stages framework stands as a pivotal tool for evaluating the maturity, decentralization, and trust minimization of Layer 2 scaling solutions within the Ethereum ecosystem. By categorizing rollups into Stage 0 (full operator control), Stage 1 (limited operator control with permissionless fraud proofs), and Stage 2 (full code control), the framework provides a clear and objective pathway for understanding a project's progression towards fully inheriting the robust security properties of the Layer 1 blockchain. It highlights the critical journey from reliance on trusted operators to a state of complete trust minimization and censorship resistance.

Understanding these stages is paramount for all participants in the blockchain space, from developers building on L2s to users transacting on them, and especially for traders and investors making informed decisions. While the framework is an excellent indicator of security against permissioned actors, it is essential to remember that it does not encompass all aspects of security, such as protection against smart contract bugs. Therefore, the L2BEAT Stages should be utilized in conjunction with other due diligence practices. As the Layer 2 landscape continues to evolve, this framework remains an indispensable guide, fostering transparency and enabling a more secure and decentralized future for Ethereum scaling.