Analyzing the next generation L2 technology of Ethereum: Booster Rollups

Author: 2077Research Source: X, @2077Research Translator: Shan Ouba, Golden Finance

In the first article of our Rollups 2.0 series, we discussed Layer 1 (L1) based rollups - a highly decentralized and Ethereum-compatible method for managing rollups. By delegating the task of transaction ordering to Ethereum L1, L1-based rollups can leverage L1's decentralization, simplicity, and activity, while also bringing other advantages.

In today's article, we will explore the next evolution of rollups: Booster Rollups. Booster Rollups not only build upon L1-based rollups but also further expand Ethereum's composability. But how do we truly scale this composability?

Current Issues in L2 Space

To ensure that the L2 network operates as expected, additional checks are usually required. However, the main settlement and execution processes still occur directly on L1. This means that while L2 expands functionality (such as off-chain EVM execution), it also adds additional complexity. Although this extra logic is not ideal, the ultimate goal is to standardize operations and rely entirely on standard EVM.

Standardization is crucial for achieving smooth transaction exchanges between different L2s. To achieve this goal, a new type of transaction may be needed—transactions capable of operating across multiple chains.

In this system, a transaction can generate smaller sub-transactions. Each sub-transaction contains the following details:

1. Source Chain ID

2. Target chain ID

3. Input data (for example, caller, address, and call data)

4. Output generated by the target chain

The two main functions of this trading data:

1. As input on the source chain

It allows participants to directly view the output without directly involving the target chain.

2. Verify the consistency of inputs and outputs on the target chain

It is used to confirm whether a given input produces the expected output.

In this way, each chain can independently verify its own transactions while adhering to the shared standards for transaction formats and inputs.

This method keeps block validation simple, ensuring block validity with familiar L1 verification contracts. This shared standard and improved cross-chain transaction method lays a solid foundation for the future development of L2 networks and makes Booster Rollups a key driver of Ethereum ecosystem development.

How are Booster Rollups different?

Booster Rollups process transactions in a manner similar to execution on L1, allowing them to access the state of L1 while having independent storage, thus extending execution and storage to L2. Each L2 extends the block space of L1, distributing transaction processing and data storage over a wider area.

Imagine that by deploying a decentralized application (dapp) just once, it can automatically scale to all Layer 2 (L2) networks. If more block space is needed, simply add more Booster Rollups without additional configuration. This means developers do not increase workload, redeployment costs, or extra complexity.

In simple terms, Booster Rollups are like adding more CPU or SSD to your laptop: they enhance performance, make applications run more efficiently, and easily achieve scalability.

From a technical perspective, Booster Rollups can also be described as "distributing transaction execution and storage across multiple shards."

How Booster Rollups Work

Both Optimistic Rollup and ZK Rollup can utilize the Booster feature. However, not all Rollups require full boosting; some Rollups can benefit from L2-specific optimizations.

If the goal is to achieve native Ethereum scaling, the best improvement scenario is to implement it on an L1-based Rollup. By allowing L1 validators to propose blocks for the entire Boosted network, Ethereum can be expanded seamlessly.

Boosted Rollups also address the common fragmentation issue present in the current Rollup ecosystem. Through a Layer 1 based sequencing mechanism, they not only retain the advantages of Layer 1 ordering but also introduce atomic cross-Rollup transactions across all L2 Booster networks. This design realizes the scalability vision that Ethereum envisioned from the start—being both integrated and scalable, providing a unified solution to the growth challenges of Ethereum.

Because Booster Rollups inherently support synchronous composability, this rollup model eliminates the hassle of dealing with fragmentation or switching between multiple L2s. All prioritized decentralized applications (dapps) can be used on each L2, providing users with a seamless Ethereum experience.

By using Booster Rollups, developers can scale their dapps without the need for multiple redeployments on various L2s. By deploying once on L1, dapps will automatically scale to all existing and future Boosted L2s, greatly simplifying the development and deployment process.

Because Booster Rollups natively support synchronous composability, this rollup model eliminates the hassle of handling fragmentation or switching between multiple L2s. All preferred decentralized applications (dapps) can be used on each L2, providing users with a seamless Ethereum experience.

By using Booster Rollups, developers can scale their dapps without the need to redeploy multiple times across different L2s. Simply deploying once on L1 allows dapps to automatically scale to all existing and future Boosted L2s, greatly simplifying the development and deployment process.

Advantages of Booster Rollups

1. Transparent Scalability

Booster Rollups enhance scalability in a transparent manner, similar to adding more servers to a server cluster. Applications can seamlessly utilize additional resources, and developers can scale solutions without deploying complex L2 infrastructure.

2. Solve the fragmentation issue

Booster Rollups provide a unified user experience between L1 and L2. Since smart contracts share the same address across all networks, users can enjoy consistency and convenience in both L1 and L2 environments.

3. Solve the problem of low deployment efficiency

Developers only need to deploy once on L1, and dapps can default to support multiple Rollups, with updates managed centrally. Regardless of whether users use external accounts (EOA) or smart wallets, they can conduct seamless transactions across networks through a single address.

4. Addressing the Attractiveness of Rollup Operators

Developers do not need to specifically choose a deployment network; dapps will automatically support various Rollup networks. Booster Rollups can be used in conjunction with L1-based Rollups to achieve significant scalability. Moreover, not all L2s need to become Booster Rollups, which makes hybrid networks possible.

5. Enhancement of Sovereignty and Security

Booster Rollups eliminate the need for specific Wrapper Contracts, as smart contracts operate the same on both L1 and L2, with control remaining in the hands of developers. By applying security measures individually for each dapp instead of relying on bridges or specific implementations, security has been significantly enhanced, while also eliminating the risk of single points of failure.

Limitations of Booster Rollups

To ensure that L2 can remain consistent with L1, the deployment of smart contracts should be limited to L1. This restriction ensures unified access between L2s. This is not a significant limitation, as smart contracts can still exhibit different behaviors through data-driven methods, such as contract addresses stored on-chain varying between different chains.

Although L1 holds shared data, this does not directly improve scalability, which is an inherent challenge of any scalable system. Developers must optimize to minimize this impact. Similar to traditional software, not all decentralized applications (dapps) can fully take advantage of parallel processing. However, even if these dapps run on separate L2s, they can still benefit from interoperability, as they maintain universal accessibility for all users.

Booster Rollups are essentially a form of scaling for L1, but they have unique mechanisms for transaction execution and storage. To correctly interpret the transactions of Booster Rollup, L1 and L2 nodes must remain in sync. One possible solution is to run L1 and L2 on the same node simultaneously, switching between shared L1 storage and L2 specific storage when executing transactions.

Conclusion

Booster Rollups provide a transformative solution that enhances transaction throughput and storage efficiency by seamlessly integrating with L1, addressing the scalability challenges of Ethereum. They tackle issues such as fragmentation and inefficient deployment, enabling developers to easily scale dapps across multiple L2s while maintaining security and sovereignty.

By simplifying scalability and promoting interoperability, Booster Rollups pave the way for a more unified and user-friendly Ethereum ecosystem.