Sidechain · settles to Ethereum
Eclipse ticker ES
Summary
Operator-run chain built from a fork of Solana's validator software. A permissioned sequencer run by Eclipse orders and executes transactions in slots. A publisher compresses the blocks and posts them to Celestia for data availability. Eclipse's security page says only a whitelisted proposer publishes state roots to Ethereum and that no fraud or validity proofs are live, so invalid state roots cannot be challenged; the fraud proofs it plans to build on RISC Zero are not deployed. ETH enters through a canonical bridge on Ethereum; a trusted relayer authorizes each withdrawal, which can be claimed after a 7-day window, though Eclipse's developer bridge page says withdrawals are currently disabled. No open stake or work competition decides who produces blocks. 1246891224
Design
- System
- SidechainEclipse describes itself as an Ethereum-settled optimistic layer 2 that runs a fork of Solana's software and posts its data to Celestia. It is filed here as a sidechain because nothing on Ethereum currently checks its state: Eclipse's own security page says no fraud or validity proofs are live, the canonical bridge releases ETH only after permissioned parties authorize each withdrawal, and L2BEAT now describes Eclipse as a sidechain in its Others category. ETH, with 9 decimals, is the gas asset; ES is a separate token that does not pay fees.
- Settles to
- EthereumETH arrives from Ethereum through Eclipse's canonical bridge, which holds deposits in a treasury contract on Ethereum. Deposits take a few minutes. Eclipse's bridge docs describe withdrawals that a trusted relayer authorizes, that can be cancelled during a 7-day fraud window and that are then claimed on Ethereum, but its developer bridge page says withdrawals are currently disabled. Ethereum does not verify Eclipse blocks or state, and L2BEAT notes the treasury owner can move the locked funds and the contracts can be upgraded instantly.
- Settlement family
- Solana / SVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One permissioned sequencer run by Eclipse; Eclipse's security page says there is no fallback if it stops or censors. Eclipse's node guide says the network is kept permissioned so unauthorized validators cannot join, and asks would-be validators to contact the admin. A read-only query of the public RPC endpoint on 2026-09-27 showed a single voting validator account holding all stake.
- Fork choice
- The node software keeps Solana's vote-based fork rules, but with one voting validator the canonical chain is whatever the operator produces. Ethereum does not choose between Eclipse forks. The designed Ethereum gateway lets an authorized role start a new fork of its recorded commitment chain; whether that gateway is live on mainnet was not verified.
Qualifications
- System class · Contested. Eclipse's docs and website call it an Ethereum layer 2 settled on Ethereum. L2BEAT describes it as a sidechain powered by the Solana Virtual Machine and lists it under Others because the proof system is not working and there is no data-availability bridge. This profile uses sidechain; it would move to layer 2 if proofs and Ethereum-checked data commitments go live.
- Scarce resource · Not applicable. Block production is assigned by the operator. The chain keeps the stake accounts of its forked Solana software, but one operator-run validator holds all stake, so stake does not decide who produces blocks.
- Finality · Partial. The confirmation levels of its forked Solana software exist, but with one voting validator a finalized block reflects only the operator's own votes. No stage of an Eclipse transaction becomes final by Ethereum's rules; bridge withdrawals wait out a 7-day window after a relayer authorizes them.
- Data availability · Partial. Block data is posted to Celestia, and Celenium showed a new Eclipse blob minutes before this review. L2BEAT says transaction roots are not checked against Celestia's attestations on Ethereum and there is no fallback if Celestia data becomes unavailable.
- Withdrawals · Contested. Eclipse's user guide describes 7-day ETH withdrawals to Ethereum, while its developer bridge page says withdrawals are currently disabled. L2BEAT records a new bridge contract from November 2025 that can settle pending withdrawals, and that contract differs from the address in Eclipse's docs.
- Ecosystem continuity · Unknown. The chain was producing blocks and posting data on review day. The Foundation's June 2026 post says its focus has been an app called Human API, Orca shut its Eclipse trading interface in March 2026, Eclipse's tETH and tUSD products are redeem-only, and several listed ecosystem sites did not load.
Tradeoffs
- Emphasizes
- Scalability Contested
- Gives up
- Decentralized operation and trust-minimized security. One operator sequences every transaction with no fallback, no proof checks its state, withdrawals need a permissioned party to authorize them, the bridge and treasury contracts can be upgraded with no delay, and transaction data lives on Celestia with no data-availability check on Ethereum. Running even a non-voting node needs server-class hardware.Eclipse's docs say it inherits Ethereum's integrity and censorship-resistance guarantees. Its own security page and L2BEAT's review say those guarantees are not in place today, so the security corner is not listed and the reading is marked contested. Scalability here means the parallel execution of its forked Solana software, run by one operator, not a measured throughput.
- Full node at home
- Data-center class 3111223Eclipse's docs list RPC node requirements of 12 cores and 24 threads at 2.8 GHz or faster, 256 GB of RAM, a 2 TB ledger disk and a 500 GB accounts disk. Its node guide, last edited in May 2026, asks for 16 cores and 32 threads and 512 GB of RAM. The guide builds the node from a solar-eclipse repository at version 2.2.20.1, matching what mainnet reports, but that repository returned not found on GitHub during review, and Eclipse's public fork of Solana's software was last updated in February 2025. Validator nodes are permissioned.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Built into the protocolLimited scope | Limited to exchanges on Eclipse itself. Eclipse runs Solana's execution environment, where a transaction can carry several signers and all its instructions succeed or fail together, so two parties can exchange Eclipse assets in one transaction. This was inferred from Solana's documented behaviour and Eclipse's statement that its execution is a direct fork of Solana, not tested on Eclipse. No cross-chain hash-locked swap mechanism was found. 11039 |
| Authenticated data publication | Unknown | Not yet assessed under the current definitions; no way for Eclipse users to publish data against a commitment the chain records was found, and absence was not exhaustively verified. Eclipse posts its own block data to Celestia for data availability; under the current definition that posting is Celestia's feature, not Eclipse's. 8 |
| Light clients | Not present | None: no light client can check Eclipse's execution, because no proofs are posted and Eclipse's security page says execution correctness is not verifiable on Ethereum. The nearest feature, a Celestia light node sampling the data Eclipse posts, confirms only that the data is available, not that the resulting state is correct. 424 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Eclipse was found or reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Programs are compiled programs for the Solana Virtual Machine that Eclipse's software forks, and accounts can be controlled by program logic rather than a single key. Eclipse says building and deploying programs is the same process as on Solana. 1038 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under this row's current definition. |
| Rollups | Unknown | No rollups anchored to Eclipse were found or reviewed. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | ThinInvariant, Orca (withdrawals only since March 2026) | Orca, the first DEX listed on Eclipse's ecosystem page, disabled trading and new liquidity on Eclipse on 6 March 2026 and now offers only a withdrawal tool. Invariant's Eclipse interface loads, and GeckoTerminal still lists Orca and Invariant pools. DefiLlama's Eclipse DEX tracker reports nothing for the 30 days before review, but its only reporting venue, Invariant, showed the same daily figure from late April 2026 until the series stopped on 6 August 2026, so it cannot show current trading. Lifinity's Eclipse site had an expired certificate. 2228293033 |
| Issuer-native stablecoins | None found | Neither Circle's USDC address list nor Tether's supported-protocols page names Eclipse. USDC on Eclipse is a Hyperlane-minted token backed by USDC locked on other chains. Eclipse's own yield-bearing dollar token, tUSD, is being sunset and can only be redeemed. 19263435 |
| Algorithmic stablecoins | Unknown | Eclipse's ecosystem page lists Neptune Protocol's USDN as a decentralized stablecoin, but Neptune's site did not resolve during review, so its design and usage were not verified. 22 |
| Bridges | Native to the protocolEclipse Canonical Bridge (ETH to and from Ethereum), Hyperlane warp routes via Nexus, Relay | The canonical bridge moves ETH between Ethereum and Eclipse. Hyperlane routes named in Eclipse's docs carry USDC from Ethereum and Solana and SOL and WIF from Solana, and Eclipse's bridge list adds Stride's Hyperlane bridge for TIA. Relay's chain list shows Eclipse enabled for ETH. Eclipse's docs also list Stride, Gas.zip, Orbiter, Owlto and others, which were not reviewed. Risk: Canonical withdrawals depend on a trusted relayer and multisig with no proof system, the treasury owner can move locked ETH, and the contracts can be upgraded without delay, per L2BEAT and Eclipse's security page. Eclipse's docs disagree on whether withdrawals are enabled. Hyperlane tokens on Eclipse depend on Hyperlane's own validator security, which was not reviewed. 45141516172431 |
| Block explorers | ThinEclipseScan | Eclipse's docs name EclipseScan as the official explorer, which loaded during review. The Eclipse Dev Explorer is marked deprecated and the Eclipse XRAY domain did not resolve. Celestia explorers such as Celenium show Eclipse's posted data, not Eclipse transactions. Explorer indexes are not canonical consensus. 112032 |
| Hardware wallets | Unknown | See custody rows: Ledger's supported-assets page does not name Eclipse, Trezor lists the ES token only on Ethereum and Solana, and no wallet path for signing Eclipse transactions with either device was verified. 3637 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Ledger's supported-assets page does not name Eclipse and its Eclipse coin page returned 404. Eclipse accounts use the key format of its forked Solana software, but no wallet was verified that signs Eclipse transactions with a Ledger device. 36 |
| Trezor | UnknownSame as native: Unknown | Trezor's Eclipse (ES) page lists the ES token only on Ethereum and Solana, with Trezor Suite, MetaMask, Backpack, Rabby or NuFi; the Eclipse network itself is not listed, and holding the token on another network is not custody on Eclipse. No third-party wallet path for signing Eclipse transactions with a Trezor device was verified. 37 |
Public data
iKnow Blockchain has no public-data lookups for Eclipse yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Eclipse Foundation reset ES's role around the Human API app
The Foundation said it had sold part of its treasury to fund operations, that its focus had been Human API, a mobile app it says has passed 100,000 users new to crypto, and that ES is Human API's only token. It dropped the utility-token framing for ES in favour of user incentives it is exploring, kept supply fixed at 1 billion, and published a new allocation: 24% float, 29% ecosystem and development, 16% contributors and 31% early supporters and investors, with a third of the last two groups unlocking on 16 July 2026 and the rest monthly over 24 months.
- Implementation:treasury sale reported as completed; token mechanisms described as being explored
- Release:announced in a Foundation blog post
- Activation:not a protocol change
Source: Eclipse Collective — Updated $ES Tokenomics (external site)
-
Orca disabled trading on Eclipse and moved to withdrawals only
Orca wound down its services on Eclipse: trading and adding liquidity were disabled, its main Eclipse interface shut down, and a permanent withdrawal-only tool was made available for closing positions. Orca says assets remain on-chain and there is no withdrawal deadline.
- Implementation:trading and new liquidity disabled
- Release:withdrawal-only tool published
- Activation:in effect on review day
Sources: Orca — Eclipse Sunset (external site) · Orca — Whirlpool Position Closer (external site)
Topics your AI can explain
Your AI can explain these topics for Eclipse through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Whether Eclipse currently posts state commitments to an Ethereum gateway contract was not verified; its security page says a whitelisted proposer publishes state roots, but the docs give no mainnet gateway address and L2BEAT lists no such contract.
- The fraud-proof system Eclipse plans with RISC Zero is not live; Eclipse's public repositories for that work were last updated in August 2025, and no delivery date was found.
- Eclipse's docs disagree on whether canonical bridge withdrawals are enabled, and the bridge contract address in the docs differs from the one L2BEAT tracks since November 2025.
- The legal entity that runs the sequencer, the relayer and the multisigs, and the identities of the multisig signers, were not sourced.
- Eclipse's node guide builds the mainnet client from a solar-eclipse repository that returned not found on GitHub during review, so whether outsiders can build and inspect the exact client was not confirmed.
- DefiLlama's Eclipse DEX series stopped updating on 6 August 2026 after months of an unchanged figure, so current trading activity on Eclipse was not measured.
- Whether Human API, the Foundation's current product focus, uses the Eclipse chain was not stated in the reviewed post.
- Ledger and Trezor paths for Eclipse were not found on vendor pages, and no third-party wallet signing path was verified.
- Neptune Protocol's USDN and Lifinity's Eclipse venue could not be reached, so their status is unknown.
- Hyperlane's validator and security settings for the Eclipse warp routes were not reviewed.
- Atomic-swap support was inferred from Solana's transaction model rather than tested on Eclipse; reversible-transfer or recovery, channel and rollup surfaces were not found.
- No throughput claims were recorded; Eclipse's website calls it the fastest Ethereum layer 2 without a sourced figure.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- What is Eclipse? (external site)
- Architectural Overview (external site)
- Stage 0 & Stage 1 (external site)
- Security Architecture: From Assumptions to Guarantees (external site)
- Eclipse Canonical Bridge (core infrastructure) (external site)
- Withdrawal Flow (external site)
- System Composition (external site)
- Eclipse's Celestia Publisher (external site)
- Eclipse L1 Gateway (external site)
- Differences Between Eclipse and Solana (external site)
- RPC & Block Explorers (external site)
- How to run mainnetbeta RPC node (external site)
- Frequently Asked Questions (external site)
- Bridges (external site)
- Eclipse Canonical Bridge (developers) (external site)
- 2. Bridge Assets for Gas and Transactions (external site)
- Hyperlane (external site)
- $ES (external site)
- tUSD (external site)
- User Resources (external site)
- Updated $ES Tokenomics (external site)
- Ecosystem (external site)
- Eclipse-Laboratories-Inc/agave (external site)
- Eclipse (external site)
- eclipsemainnet chain metadata (external site)
- USDC warp route configuration including Eclipse (external site)
- Eclipse namespace on Celestia (external site)
- Eclipse Sunset (external site)
- DEX overview: Eclipse (external site)
- Top eclipse Pools (external site)
- Relay chains API (external site)
- EclipseScan (external site)
- Invariant DEX on Eclipse (external site)
- USDC Contract Addresses (external site)
- Supported Protocols (external site)
- Supported crypto assets (external site)
- Eclipse (ES) wallet (external site)
- Accounts (external site)
- Transactions (external site)
- Solana Commitment Status (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding