L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our discord to suggest improvements!
Socket
...
Choose token
USD Coin (USDC)
Wrapped eETH (weETH)
Wrapped liquid staked Ether 2.0 (wstETH)
rswETH (rswETH)
Staked USDe (sUSDe)
Savings Dai (sDAI)
Wrapped Ether (WETH)
Wrapped BTC (WBTC)
ENA (ENA)
Synthetix Network Token (SNX)
Dai Stablecoin (DAI)
ether.fi governance token (ETHFI)This page gathers Socket vaults built on top of Socket Data Layer cross chain messaging protocol.
Socket is highly flexible and configurable and risks vary depending on the current configuration of the specific route. It allows to define custom Token Vaults that communicate using different messaging protocols. Token Vaults are connected via Plugs and Switchboards to their remote counterparts. The central contract on each chain, Socket, stores the configuration of all Plugs and Switchboards. Some Switchboards may be as secure as “native” (canonical) bridge, some may use simple Relayers/Watchers to move messages across chains.
Funds can be stolen if
Users can be censored if
Principle of operation
Socket is a bridge framework connecting different chains via a set of “switchboards”. Every chain using Socket for some of its tokens can mix & match many switchboards with varying trust assumptions, for example mixing a “fast” route via “Fast Switchboard” with a “Standard Route” using a native rollup AMB.
Various switchboards
Vaults can use any registered switchboards. The validation model is chosen by the switchboard and their security can vary from using a canonical bridge to a third-party validation model.
Users can be censored if watchers fail to facilitate the transfer (CRITICAL).
Funds can be stolen if watchers submit fraudulent block hash and relay fraudulent transfer (CRITICAL).
Funds can be stolen if the Socket Vault owners change the Vault configuration (CRITICAL).
The system uses the following set of permissioned addresses:
Account privileged to set up different roles in the main Socket contract.
Multisig that owns the Socket Vaults associated with Lyra. This is a Gnosis Safe with 2 / 3 threshold.
Those are the participants of the LyraMultisig.
Multisig that owns the Socket Vaults associated with Kinto. This is a Gnosis Safe with 3 / 6 threshold.
Those are the participants of the KintoMultisig.
EOA that owns the Socket Vaults associated with hook.xyz.
The system consists of the following smart contracts:
Central contract in Socket SuperBridge holding configuration of all Plugs and associated Switchboards.
Fast Switchboard having a set of Watchers authorizing transfers. If the transfer is not explicitly authorized within certain period of time, it is optimistically considered to be valid. Watchers can also stop (trip) an invalid transfer.
Switchboard using native Polygon message passing.
Switchboard using native Optimism message passing.
Switchboard using native Arbitrum message passing.
Value Locked is calculated based on these smart contracts and tokens:
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Lyra and owned by LyraMultisig.
Socket Vault associated with Hook and owned by HookOwnerEOA.
Socket Vault associated with Hook and owned by HookOwnerEOA.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Kinto and owned by KintoMultisig.
Socket Vault associated with Reya and owned by socketadmin.eth EOA.
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).