Comment on page
Our validating bridge deployed directly to Ethereum is the primary way to bring assets to Eclipse Mainnet. You will be able to bridge ETH and eventually other assets via our bridge. The bridge is a hashed timelock contract (HTLC).
ETH is the native token for Eclipse Mainnet. We do not have any other native token for Eclipse Mainnet.
The Hyperlane bridge will provide fast finality bridging between Eclipse Mainnet and non-Ethereum chains. The Eclipse team worked with Hyperlane to deploy their mailbox contracts for the SVM.
Eclipse and Hyperlane partnered to bring Hyperlane's Permissionless Interoperability solution to Solana Virtual Machine (SVM) based blockchains. This integration enables Eclipse rollups to connect with other rollups and ecosystems without permission, communicate with non-IBC-enabled chains, provide fast-finality interoperability protocol for Eclipse rollups, and establish a mechanism for a token bridge.
Hyperlane's solution allows for unlimited instantiation of rollup chains, making it useful for high throughput SVM-based rollups. This collaboration is a significant step towards promoting interoperability, modularity, and customization within the SVM ecosystem and the industry as a whole.
IBC is the standard bridge between Cosmos chains.
To support trust-minimized IBC bridging to non-Eclipse chains, we impose a challenge period on IBC messages. We pass state roots as soon as they are generated by Eclipse Mainnet, but they cannot be used for IBC state proofs until after a specified number of blocks (the challenge period). If a correct fraud proof is passed to the light client on the receiving chain within the challenge period, then all IBC messages after that point are removed.
Our integration with IBC is still under development.