Eclipse Explained

Table of contents

Eclipse is an evolved rollup solution – a modular architecture that provides scalability and flexibility for decentralized applications (dApps). As the blockchain industry continues to evolve, solutions like Eclipse will unlock the full potential of this groundbreaking technology by helping Web3 projects overcome the biggest hurdles to mainstream adoption. This article describes the limitations of the traditional blockchain space, and outlines how Eclipse represents a valuable new solution for issues facing dApp developers and businesses.

For a full glossary of technical terms, including those used in this article click here

Introduction: What vendor lock-in looks like in Web3

One of the main promises of blockchain technology is that it will revolutionize the Internet as we know it, by transforming the Big Tech-dominated Web2 into a decentralized, more user-controlled and owned "Web3". Over the last several years, dozens of layer-1 (L1) blockchain networks have been built with the vision of supporting this next generation of decentralized applications (dApps), each with their own unique solutions for achieving consensus, scalability, and speed. While many dApps have been successfully built on L1s, they are subject to the constraints of those networks, particularly data throughput, which is typically expressed in terms of transactions per second, or TPS. 

In addition, these L1 networks offer different functionalities and are typically independent of one another, making it difficult for applications to adapt to changing needs, or access value (I.e. liquidity) across relatively isolated networks. These issues are matters of scalability (the ratio of TPS to cost of running the network), and interoperability (the ability to move assets between chains). Both limitations can be addressed by layer-2 (L2) solutions, including Eclipse.

Traditional L2 solutions and how Eclipse compares

Multiple solutions exist to address issues of L1 scalability and interoperability. These include rollups and sidechains. Here’s a little background if you’re not familiar with L2 solutions:

Rollups work by serving as an additional layer on top of the L1 blockchain, which handles most of the transaction processing, while still utilizing the security and decentralization of the underlying blockchain. By bundling transactions for execution off-chain, rollups are able to assist in reducing L1 network congestion. 

There are two basic types of rollups: "optimistic" and "zero-knowledge" (zk). Eclipse is deploying as an optimistic rollup, with plans for a zk-rollup in parallel.

To use a simplistic analogy, rollups are like buses on a busy highway during rush hour. If every one of the bus passengers were traveling in their own personal cars, the highway would become congested with vehicles, and traffic would slow. But by "rolling up" many passengers onto buses, traffic can flow more freely, and everyone gets to their destinations faster. 

A sidechain is a separate blockchain that operates alongside the main blockchain and is connected to it via a two-way peg. Sidechains touch on the concept of "interoperability" in the blockchain space, allowing assets to be moved from the main blockchain to the sidechain and back again, with the two chains linked in a secure and trustless process. 

While technically not an L2 solution, some chains may also use bridges to transfer assets to another independent L1 blockchain that simply has a higher throughput capacity, or less network congestion, compared to the original chain. For example, faced with congestion on Ethereum, a user might use a bridge to transfer an asset from Ethereum to Solana, or to NEAR, despite the fact that Solana and NEAR are entirely independent networks. 

Here’s where Eclipse shines compared to these current solutions: Eclipse is a modular rollup that solves the same problems as traditional rollups and sidechains, but in a more customizable and flexible manner, in a single product. This unlocks enhanced scalability, improved throughput and advanced interoperability for any dApp. 

Why Eclipse is a smart choice for dApp developers and businesses


Typical blockchains are built one-size-fits-all. Compared to traditional L2 solutions, Eclipse offers a highly modular approach, allowing developers the freedom to select their preferred virtual machine, L1, and additional customizations. DApps built with Eclipse allow developers to choose their preferred execution layer, customizations in the settlement layer, and data availability layer - offering complete flexibility for operating on different blockchain networks. This flexibility negates the need to rely on a singular, monolithic software stack and enables developers to cherry-pick the tools that best align with their project requirements. 


Improving scalability is a crucial objective for dApps, because it directly impacts the volume of transactions – and therefore users – the application can handle. As the number of users and transactions on a blockchain grows, the network’s capacity can become strained, leading to longer transaction times, higher fees, and a worse user experience. Since blockchain networks tend to be inherently slower than centralized systems, it is very important to prepare your application for network congestion. Eclipse solves this problem by providing every individual dApp that utilizes Eclipse with maximum dedicated TPS, giving dApps the ability to handle a massive amount of users; compared to traditional L1’s where you have to share that TPS with others. A whole highway for yourself - this is necessary for mainstream adoption.


With Eclipse, dApps can take advantage of the security and decentralization offered by blockchain networks, without being constrained by the limitations imposed by a single L1 chain. DApps using Eclipse can seamlessly transition from network to network, according to the needs of the developers and the dApp community. If an L1 blockchain network goes down, or becomes compromised, a dApp using Eclipse can simply switch to another chain. DApp developers can also jump on opportunities to grow, shifting to wherever demand for their dApp may be greatest. With a fully flexible dApp, value and community will follow where the dApp goes. 

The outcome is a fully adaptable, customized blockchain that developers can deploy as an "out-of-the-box" solution, quickly and easily. With Eclipse, developers are no longer constrained by the limits of a single L1 blockchain – their dApps can utilize the best features of several chains in one project. Eclipse supports communication between different blockchain networks, acting as an interface, and reducing the need for standardized intra-chain protocols.

In short, Eclipse enables a more adaptable development experience than traditional L2s, with less work required on the part of dApp developers, and without the worry of being "locked-in" to a particular L1 blockchain.

Ready to get started with Eclipse? Connect with our team: