Search

Search for projects by name

L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our Discord to suggest improvements!

SummaryValue LockedRisk summaryTechnologyPermissionsSmart contracts

Eclipse logoEclipse

There are implementation changes and part of the information might be outdated.

About

Eclipse is a sidechain powered by the Solana Virtual Machine (SVM).

  • Total value locked
  • Destination
    Eclipse
  • Validated by
    Third Party
  • Type
    Token Bridge

    • About

    Eclipse is a sidechain powered by the Solana Virtual Machine (SVM).

    Value Locked
    Risk summary

    Users can be censored if

    1. the bridge operators decide not to mint tokens after observing a deposit.
    Technology

    Principle of Operation

    Eclipse implements a custom deposit-only bridge. There is no functionality to withdraw assets back to Ethereum.

    1. EtherBridge.sol - Etherscan source code, deposit() function, no withdraw function
    2. Mailbox.sol - Etherscan source code, receiveMessage() function calls EtherBridge

    Third party validation

    Deposits are processed by the bridge operators on the Eclipse side. There is no mechanism to send messages back to Ethereum.

    • Users can be censored if the bridge operators decide not to mint tokens after observing a deposit.

    • Funds can be stolen if the Treasury owner decides to transfer the funds locked on L1.

    1. Treasury.sol - Etherscan source code, emergencyWithdraw() function
    Permissions

    The system uses the following set of permissioned addresses:

    AuthorityMultisig 0x4720…64E0

    This is a Gnosis Safe with 3 / 5 threshold. Can pause and upgrade the EtherBridge and Mailbox contracts.

    AuthorityMultisig participants (5) 0xBb53…D5470xCD2f…e6A40x9508…B2a50x7572…BFc20xF48C…46FA

    Those are the participants of the AuthorityMultisig.

    TreasuryOwner 0x7B2c…0efC

    This is a Gnosis Safe with 3 / 5 threshold. Can upgrade and transfer funds from the Treasury.

    TreasuryOwner participants (5) 0xd061…cDb50x0706…8Fed0xDecF…96860xEe05…82D90x3392…C080

    Those are the participants of the TreasuryOwner.

    Smart contracts
    Note: Contracts presented in this section had their implementations updated since the last time our team looked at this project. The information presented may be inaccurate.
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    The system consists of the following smart contracts on the host chain (Ethereum):

    EtherBridge 0x83cB…0fd1Implementation (Upgradable)Admin

    Entry point to deposit ETH. It is registered as a module in the Mailbox contract.

    Mailbox 0xb23B…968dImplementation (Upgradable)Admin

    Contract receiving messages from registered modules to send to Eclipse. It doesn’t have any functionality to send messages back to Ethereum.

    There are implementation changes and part of the information might be outdated.
    Treasury 0xD7E4…E644Implementation (Upgradable)Admin

    Holds the funds locked on Ethereum. This contract stores the following tokens: ETH.

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).