Novel SVM-on-Ethereum architecture with real upside but centralized sequencer and untested bridge create meaningful tail risk for early adopters
Risk Breakdown
Top Risks
1
Cross-VM bridge between SVM and EVM introduces novel attack surface with no established security track record
2
Sequencer centralization: single sequencer controls transaction ordering and can censor or delay transactions
3
Immature ecosystem with limited audited DeFi protocols and nascent tooling compared to EVM counterparts
4
Dual external dependencies (Ethereum settlement + Celestia DA) create a novel two-layer security model with untested failure modes
Frequently Asked Questions
Is Eclipse safe to use?
Eclipse receives a C+ risk grade (42/100) from Hindenrank, where lower scores indicate lower risk. Novel SVM-on-Ethereum architecture with real upside but centralized sequencer and untested bridge create meaningful tail risk for early adopters Eclipse is the first Solana Virtual Machine Layer 2 built on Ethereum, combining SVM's high-performance execution with Ethereum's security and settlement. It uses Celestia for data availability and ZK proofs for validity. The chain is VC-backed with $65M raised but remains centralized at the sequencer level and has no native token yet. Suitable for developers wanting SVM speed with Ethereum liquidity, but carries meaningful bridge and sequencer risk.
What are the main risks of using Eclipse?
The key risks identified for Eclipse are: (1) Bridge vulnerability: a bug in the Ethereum L1 bridge contract could result in total loss of all bridged ETH (2) Sequencer centralization: Eclipse relies on a single sequencer — if it goes down, the chain halts and funds may be temporarily inaccessible
What is Eclipse's risk score breakdown?
Eclipse scores 42/100 across eight risk dimensions: Mechanism Novelty: 11/15, Interaction Severity: 10/20, Oracle Surface: 4/10, Documentation Gaps: 4/10, Track Record: 4/15, Scale Exposure: 0/10, Regulatory Risk: 3/10, Vitality Risk: 6/10. The highest risk area is Mechanism Novelty at 11/15.
How does Eclipse compare to other L2 protocols?
Among 41 rated L2 protocols on Hindenrank, Eclipse ranks #35 by safety (lowest risk score = safest). Its 42/100 risk score and C+ grade place it among the riskier L2 protocols.
Has Eclipse ever been hacked or exploited?
Eclipse scores 4/15 on the Track Record risk dimension, indicating some history of security incidents or exploits. Higher scores reflect more severe or frequent incidents. Review the full risk report for details.
Last scanned 2026-06-13
Get risk alerts before it's too late
Weekly grade changes, downgrade alerts, and new protocol risk findings. Free.