How Does Eclipse Work?

Eclipse canonical bridge moving ETH from Ethereum L1 to Eclipse L2 as native gas token via custom lock-and-mint mechanism connecting EVM deposit contracts to SVM credit issuance

Bridge connects EVM deposit on L1 to SVM credit on L2. Custom implementation without battle-tested codebase. Only a handful of audits exist as of mainnet launch.

Single centralized sequencer batching SVM transactions and posting data to Ethereum via EIP-4844 blobs; RISC Zero ZK proof system generating validity proofs for SVM execution

ZK proving for SVM execution is novel and unproven at scale. Sequencer remains centralized despite ZK validity proofs. RISC Zero prover latency and cost at scale are not fully characterized.

Eclipse uses Celestia for data availability instead of posting full calldata to Ethereum, reducing costs but adding an external dependency on Celestia's DA guarantees

Dual external dependencies (Ethereum settlement + Celestia DA) create a novel two-layer security model. Celestia DA failure can prevent ZK proof generation and block chain progress.

SVM execution on Ethereum L2 — programs written in Rust/Anchor run natively; bridged assets denominated in ETH as native gas token

First production SVM L2 on Ethereum. Developer tooling is SVM-native (Anchor, Solana CLI), creating an ecosystem unfamiliar to EVM developers. SVM-specific bugs may not be caught by EVM-trained auditors.

Ethereum L1 as settlement layer with state roots posted periodically by the sequencer; RISC Zero ZK proofs verify SVM state transitions on Ethereum

Settlement to Ethereum is established practice for L2s. The novel element is verifying SVM execution via ZK proofs, which adds latency and proving cost uncertainty.

A vulnerability in the canonical bridge smart contract on Ethereum L1 could allow an attacker to mint unbacked ETH on the Eclipse SVM side, draining bridged funds without any SVM-level exploit. The cross-VM nature means SVM security auditors may not audit the EVM bridge contracts.

If the sequencer goes offline or is compromised, no new ZK proofs can be submitted to Ethereum, halting the chain and potentially locking bridged funds indefinitely if no forced transaction mechanism exists for users to withdraw without sequencer cooperation.

If Celestia experiences a data withholding attack or extended outage, Eclipse transactions cannot be reconstructed from DA, undermining the ability to generate valid ZK proofs and challenging Ethereum finality. Users cannot exit safely without DA.

SVM-native oracle implementations on Eclipse may behave differently due to block timing and sequencer control, enabling price manipulation attacks that exploit sequencer front-running capabilities within the SVM execution model.