Eclipse: Solana VM Layer 2 on Ethereum

Updated April 2026 · 15 min read

What Is Eclipse?

Eclipse is the first Layer 2 powered by the Solana Virtual Machine (SVM) running on Ethereum. Rather than building a custom execution environment, Eclipse leverages Solana's battle-tested parallel processing engine—capable of executing thousands of transactions simultaneously—and marries it with Ethereum's security, Celestia's data availability layer, and RISC Zero's zero-knowledge fraud proofs.

Founded by Tess Rinearson and Nate Welch (formerly of Solana Foundation), Eclipse was created with a singular thesis: parallel execution should not be limited to one blockchain. If Solana's SVM can scale to 65,000 theoretical TPS on its own chain, what happens when you combine it with Ethereum's finality guarantees?

The answer is Eclipse—a modular layer 2 that takes the "best of breed" approach: execution speed from Solana, settlement security from Ethereum, data availability from Celestia, and validity proofs from RISC Zero.

How Eclipse Works

Eclipse's architecture is elegantly modular. Unlike monolithic rollups, each component can be understood independently:

1. Execution: Solana Virtual Machine

The SVM processes transactions in parallel using Sealevel's scheduler. Rather than executing transactions sequentially (as Ethereum and most L2s do), the SVM identifies non-conflicting accounts and processes them in parallel. A transaction touching Account A, B, and C can run alongside another touching D, E, and F.

2. Settlement: Ethereum Mainnet

After transactions execute, state proofs settle on Ethereum L1. Users' assets are ultimately protected by Ethereum\'s validator set and finality. This is the security anchor: if you trust Ethereum, you can trust Eclipse.

3. Data Availability: Celestia

Transaction data is posted to Celestia, not Ethereum, reducing costs further. Celestia\'s specialized DA layer is optimized for storing and validating data availability, not execution. This separation lets Eclipse save on L1 calldata costs while maintaining cryptographic proof that data was published.

4. Fraud Proofs: RISC Zero ZK

Eclipse uses RISC Zero\'s zero-knowledge proof system to generate validity proofs. If a state transition is disputed, a zk proof can be generated and verified on Ethereum, proving the transaction was executed correctly without re-executing it on-chain. This is significantly more efficient than traditional optimistic fraud proofs.

Eclipse vs Traditional L2s

How does Eclipse compare to the major layer 2s? Here\'s a breakdown:

The Eclipse advantage: Parallel execution and external DA (Celestia) yield faster speeds and lower fees. The tradeoff: Developers must adapt to SVM tooling rather than EVM tooling, though SVM is Rust-based and has grown more accessible.

The ES Token

Eclipse\'s native governance and utility token, ES, launched mid-2025 as the network activated. Here\'s the tokenomics snapshot:

Supply & Allocation

• Total Supply: 1 billion ES tokens
• Airdrop (2025): 100 million tokens (10%) distributed July-Aug 2025 to early users
• Ecosystem Growth: 35% (350M) for incentive programs and developer grants
• Early Backers: 31% (310M) for investors and team
• Contributors: 19% (190M) for core developers and researchers
• Reserve: 5% (50M) for future initiatives

Use Cases

Eclipse Ecosystem & DeFi

Though Eclipse experienced significant headwinds in 2025-2026, several foundational DeFi applications continue building:

Key Infrastructure

Hyperlane Bridge: The primary cross-chain bridge connecting Eclipse to Ethereum and Solana. Users can bridge ETH, USDC, and other assets seamlessly. Hyperlane\'s modular design allows Eclipse to integrate quickly with other SVM-powered rollups as they launch.

DeFi Applications

Several teams are building lending protocols, AMMs, and derivatives platforms leveraging Eclipse\'s speed and cost. The SVM execution model is particularly beneficial for:

• Flash loans: Parallel execution allows atomic flash loans within a single block.
• Liquidations: Liquidation bots can operate profitably at Eclipse\'s sub-cent fee levels.
• High-frequency trading: Algorithms benefit from 1000+ TPS and low latency.

Learn more about cross-chain bridges in our cross-chain interoperability guide, and explore the broader Solana DeFi ecosystem.

The 2025-2026 Pivot

Eclipse\'s journey has not been without turbulence. After a strong 2024 and early 2025, the project faced significant market headwinds:

TVL Collapse

Total Value Locked on Eclipse declined ~95% from its 2025 peak (roughly $200M) to under $10M by early 2026. This was driven by broader market conditions, reduced institutional interest, and competition from established L2s.

Organizational Restructuring

In late 2025, Eclipse laid off approximately 65% of its engineering and operations staff. Rather than a death knell, the team reframed this as a pivot to a "studio model"—focusing on building in-house applications on top of Eclipse infrastructure rather than purely serving external developers.

What This Means

For context on broader L2 challenges, see our Ethereum L2 ecosystem guide.

Risks & Considerations

1. TVL & Liquidity Risk

With 95% TVL decline, Eclipse\'s liquidity is fragile. Users may encounter slippage on smaller trades. A recovery depends on killer apps and market sentiment shifts.

2. Competition

New SVM Layer 2s are launching. SOON (Solana\'s official optimistic network) and Atlas represent alternatives. Eclipse must differentiate through execution or ecosystem.

3. Team Uncertainty

The 65% layoff raises questions about execution velocity. Can a smaller team deliver on the technical roadmap? Key departures could further weaken commitment.

4. Developer Adoption

Building on SVM requires learning Rust and SVM-specific tooling. This is a higher barrier than EVM. Established L2s have larger developer communities.

5. Regulatory Unknowns

Like all L2s, Eclipse faces evolving regulatory scrutiny. Changes to staking, tokens, or cross-chain bridging rules could impact operations.

For deeper reading on rollups and validity proofs, explore our ZK rollups guide and data availability guide.

FAQ

Q: Is Eclipse decentralized?

A: Eclipse is moving toward decentralization. Currently, a small validator set operates the network. The roadmap includes community-run validators and governance via ES token voting, though full decentralization is a multi-year effort.

Q: What programming languages does Eclipse support?

A: Rust is the primary language (like Solana). Projects can deploy Solana programs (written in Rust) to Eclipse. Some SDKs and tooling exist in TypeScript, but core development is Rust-focused.

Q: How are transaction fees calculated on Eclipse?

A: Fees depend on computation units (CUs) and the current network congestion. A typical transaction might use 5,000 CUs. At ~0.00004 SOL per CU, fees are typically $0.0001–0.001 per transaction.

Q: Can I use MetaMask or other Ethereum wallets on Eclipse?

A: Not directly. Eclipse uses Solana-style accounts, not Ethereum addresses. You\'ll need Solana-compatible wallets like Phantom or Magic Eden. Some bridges may support Ethereum wallet UX, but the underlying account model differs.

Q: What\'s the withdrawal time from Eclipse back to Ethereum?

A: Using the Hyperlane bridge, withdrawals typically finalize in 1-2 minutes, depending on Ethereum confirmation time. This is faster than optimistic rollups, which require a 7-day challenge window.

Q: Could Eclipse eventually merge with Solana?

A: Unlikely. Eclipse and Solana serve different purposes. Solana is a monolithic L1; Eclipse is an Ethereum L2. However, cross-chain composability via bridges allows both ecosystems to interoperate without a technical merger.

Disclaimer: This guide is educational and does not constitute financial advice. Always conduct your own research and assess your risk tolerance before participating in any blockchain network or token.