Question 1

What is Eclipse (ES)?

Accepted Answer

ES is the token ticker for Eclipse. Gate’s 2025 announcement lists ES as the Eclipse token and records it as ERC-20 at that time; ES is not company equity, and the token ticker alone cannot establish current governance rights, a Gas use case, or other on-chain functions. The announcement describes Eclipse as an L2 that settles on Ethereum, uses the Solana Virtual Machine (SVM) for execution, and uses Celestia for data availability. Token identity and network architecture are related but distinct questions: the former identifies ES, while the latter explains how Eclipse organizes transaction execution and settlement.

Question 2

What do Eclipse's SVM, Ethereum settlement, and Celestia data availability each do?

Accepted Answer

Eclipse’s architecture separates three key functions: the SVM handles transaction and program execution, Ethereum provides final settlement, and Celestia provides transaction-data availability. The core of this division is not to have one layer replace every function, but for different layers to respectively handle execution, settlement, and data access. For users, this means an activity on Eclipse involves at least three concepts: execution results, data available for verification, and final settlement. “Executing on Eclipse” should not be equated directly with “immediately completing final settlement on Ethereum,” nor should the data-availability layer be mistaken for the settlement layer for assets.

Question 3

What basic tools does Eclipse provide for users, and what does each solve?

Accepted Answer

Official user resources present Eclipse App as an entry point through which users can access the Eclipse Canonical Bridge, Gas Station, tETH Minter, EclipseScan, and ecosystem pages. These tools do not solve the same problem: the bridge is for cross-network asset paths, Gas Station relates to transaction-fee preparation, and the explorer is for viewing on-chain records. The official resources also list a status page. The status page displays the operating status of key infrastructure, active incidents, maintenance, and historical incidents; checking it before bridging or execution can help distinguish between “a transaction is still being processed” and “the relevant infrastructure has a known incident.”

Question 4

How should the process of bridging assets to Eclipse be understood, and how do official and third-party bridges differ?

Accepted Answer

For transferring assets to Eclipse, the official resources list Eclipse Canonical Bridge as the official bridge; the same page also lists third-party bridges including Hyperlane, Stride, Owlto, Orbiter, Gas.zip, and Mini Bridge. Choosing an “official bridge” or “third-party bridge” first means choosing different services and operational paths, not merely selecting a page name. A cross-chain process requires confirming the source network, asset to send, destination network, and receiving address in sequence, then initiating the transaction on the chosen bridge’s page and waiting for its completion conditions to be met. If a transaction shows as incomplete, a page transition or an unrefreshed balance should not substitute for an on-chain status determination; EclipseScan can be used to view on-chain records and the status page can be checked when needed.

Question 5

How does tETH Mint/Redeem differ from ES token mechanics?

Accepted Answer

Eclipse’s official resources list tETH Mint/Redeem alongside the official bridge, indicating that it is a separate minting/redemption tool rather than a universal step automatically applicable to every bridged asset. Before using it, confirm that the asset and path being operated are supported by that tool. “Minting” and “redemption” describe opposite asset-state changes within that tool; they are not ordinary transfers, nor do they establish ES’s own minting, redemption, or supply mechanism. ES token mechanics must be understood separately from the tETH tool’s asset flow.

Question 6

What are ES's historical supply, token standard, and contract address?

Accepted Answer

Gate’s 2025 announcement records a maximum ES supply of 1,000,000,000 tokens at that time and identifies it as ERC-20. This figure and standard are historical issuance information in that announcement and cannot alone establish current circulating supply or current balances at individual addresses. The announcement also lists the Ethereum contract address at that time: 0x6055dc6ff1077eebe5e6d2ba1a1f53d7ef8430de. When identifying the ES described in the announcement, the network and contract address should be checked along with the name and ticker; different networks or later versions cannot be identified as the same asset based only on the three characters “ES.”

Question 7

What were ES's allocation and unlock rules in the 2025 announcement?

Accepted Answer

Under the allocation recorded in Gate’s 2025 announcement, ES was divided into four categories: ecosystem and development 35%, investors 31%, contributors 19%, and airdrop and liquidity 15%. These percentages total 100% and describe the maximum-supply allocation framework announced at that time. The unlock methods differ: airdrop and liquidity unlock at TGE; ecosystem and development, investors, and contributors are each locked for 12 months first, then released linearly over 48 months. Linear release means gradual release over time during the release period rather than all becoming available at once on the day the lock ends.

Question 8

How can the historical unlock arrangement affect the measure of ES's available supply?

Accepted Answer

If calculated under that historical arrangement, ecosystem and development, investors, and contributors together accounted for 85% and each underwent “12-month lock + 48-month linear release”; airdrop and liquidity accounted for 15% and unlocked at TGE. The former’s available quantity changes as the release period progresses, while the latter was unlocked at TGE according to the announcement. This explains why maximum supply cannot be treated directly as the tradable quantity at a specific point in time: even if maximum supply is fixed, locking, TGE unlocking, and subsequent linear release change the available status of different categories at different times. It also cannot predict price on its own, because price additionally depends on trading demand, order-book depth, and market conditions.

Question 9

What were the rules and boundaries of the 2025 Gate ES HODLer Airdrop?

Accepted Answer

Gate’s 2025 campaign announcement established an ES HODLer Airdrop with a total of 60,000 ES: participants had to complete identity verification, hold at least 1 GT at the snapshot, and a single user’s GT holdings counted toward the campaign were capped at 2,000 GT. Allocation was proportional to GT holdings at the snapshot. This was a Gate campaign rule at that time, not a general ES holding benefit of the Eclipse protocol. The announcement also states that the campaign’s ES was 100% unlocked; it cannot be extended to mean that participation remains available now, that all ES holders are eligible, or that ES itself has a fixed-yield mechanism.

Question 10

What roles do EclipseScan and the status page play in operational confirmation?

Accepted Answer

EclipseScan is listed in the official documentation as the official block explorer. It is suitable for viewing transactions, addresses, and other on-chain records, and is a tool for confirming whether an operation has left a record on-chain; it is not itself a bridging service and does not replace checking the network and asset in a wallet. When facing a bridging or network-use issue, first look up the transaction status in the explorer, then check whether the official status page reports active incidents or maintenance. They answer, respectively, “what is the status of this on-chain operation?” and “has the infrastructure announced an operational incident?” and should be used together rather than interchangeably.

Question 11

Can Eclipse's technology and historical unlock information directly determine ES's price?

Accepted Answer

ES’s price may be affected by trading demand for the Eclipse ecosystem, market participants’ expectations for the token, and the depth of executable orders, but Eclipse’s technical architecture or tool list does not automatically become buying demand for ES. Users or market participants must still actually form buy and sell demand for ES. Likewise, historical unlocks affect the time structure of available token quantities but do not guarantee a particular price outcome. If demand, market liquidity, or participants’ willingness to sell changes, price performance may differ from intuition based solely on technical upgrades, user resources, or the unlock schedule.

Question 12

Which information must be considered separately when understanding Eclipse and ES?

Accepted Answer

When understanding Eclipse and ES, first separate four categories of information: Eclipse’s modular network architecture, bridges and explorer tools available to users, ES’s asset identity, and the historical allocation and campaign rules in the 2025 announcement. Each category answers a different question. The architecture explains how execution, settlement, and data availability are divided; user resources explain which services can be accessed; the historical announcement explains ES parameters and campaigns at that time. Mixing them can lead to mistaking a bridging tool for an ES function or presenting old campaigns and allocations as token rights that remain currently effective.

Eclipse (ES) Price

Price of Eclipse (ES) Today in USD

Eclipse (ES) Price History

Fear & Greed Index

Why Did Eclipse (ES) Fall in the Last 24 Hours?

About Eclipse (ES)

Use Cases and Features

Supply and Issuance Mechanism

How to Buy and Use Eclipse (ES)

How to Buy

Related Markets

Simple Earn

Eclipse (ES) Basics & Market Insights

Fundamentals

Market Analysis

Frequently Asked Questions About Eclipse (ES)