What’s possible with Eclipse?

Build applications that can coordinate masses of people, scale with your needs, and stay running even during L1 downtime. Take the best parts of crypto and build with no limits.
Eclipse offers rollups-as-as-service, so that developers can deploy customized app chains for their projects without worrying about infrastructure, security, or reliability.
But how?
Blockchains have historically been "monolithic."
All of the duties of a blockchain are done by the same set of nodes (computers running the network).
Ethereum
zkSync (L2)
Execution
Consensus + Data Availability
Ethereum
settlement
Consensus + Data Availability
Ethereum
zkSync (L2)
Execution
Consensus + Data Availability
Traditional rollups have helped scale blockchains.
Rollups move execution off of Layer 1s like Ethereum. But this still isn't specialized enough to support many apps.
Ethereum
zkSync (L2)
Execution
Consensus + Data Availability
Ethereum (L1)
settlement
Consensus + Data Availability
We are building "customizable" rollups.
Your App (L3)
Execution
Your App (L3)
Execution
Your App (L3)
Execution
Eclipse (L2)
settlement
Your L1 of Choice
Consensus +

Data Availability
Your L1 of Choice
Consensus +

Data Availability
Your L1 of Choice
Consensus +

Data Availability
Apps get the freedom to pick their virtual machine and different chains for data availability.

What does this mean?

Superior speed, security, and customization for powerful apps.
Maximum customizability

Adjust block times, subsidize gas, or restrict who can use your blockchain.

Shared security

Don't worry about managing infrastructure or bootstrapping validators, because you borrow your security from the underlying Layer 1.

Scale horizontally

This means that we can always spin up another execution layer, giving developers the power of their virtual machine all to themselves.

Cheaper running costs

The data availability layer doesn’t need to support execution, and therefore the cost of running a node is cheaper promoting decentralization.