# Lido on L2: first launches **URL:** \ **Category:** Proposals\ **Created:** [August 12, 2022, 2:37pm UTC](https://research.lido.fi/t/lido-on-l2-first-launches/2786 "2022-08-12T14:37:13Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\ **Post date:** [August 12, 2022, 2:37pm UTC](https://research.lido.fi/t/lido-on-l2-first-launches/2786/1 "2022-08-12T14:37:13Z")
### TL;DR Lido aims to have as widely usable liquid staking assets as possible. L2s are the obvious activity magnets, so it just makes sense to have Lido tokens available across rapidly developing L2 ecosystems. While the best case would be allowing ETH staking from L2s, the first step is to allow tokens bridging. The post adds tech details upon the recent [Lido on L2 announcement](https://blog.lido.fi/lidos-steth-comes-to-layer-2/). ### The game plan 1. Pick Arbitrum & Optimism as first L2s to bridge Lido tokens to. 2. Allow wstETH bridging, as bridges can’t work with stETH rebases out of the box. 3. Use upgradable setup to allow building L2-ETH staking in future. 4. Use Governance Decision Bridging smart contract to execute on L2 gov decisions made on L1 (and not lean on multisig for those). 5. Bridging contracts are [audited](https://github.com/lidofinance/audits/blob/main/Oxorio%20Lido%20L2%20Smart%20Contracts%20Security%20Audit%20Report%2007-2022.pdf) & [deployed](https://docs.lido.fi/deployed-contracts/#lido-on-l2) with L1 deposits paused. 6. To ease up operations, [dev team multisig](https://docs.lido.fi/deployed-contracts/#dev-team-multisigs) has the role necessary to enable L1 deposits. The proposed launch process is: 1. Running Snapshot vote on enabling the wstETH bridging. 2. Enabling the L1 deposits on L1 wstETH bridging contracts with dev team multisig. 3. Renouncing the “L1 deposits enabler” role from dev team multisig. 4. Run all the checks necessary. 5. On green mark from the checks — it’s launched. 7. After 6) all admin rights on both L1 & L2 bridging parts belong to [Aragon Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) contract. 8. Waiting for the audit on Governance Decision Bridging contracts to get published so the Snapshot vote on enabling wstETH bridging to L2s can be started. 9. [Emergency Brakes multisigs](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2b368b535b2024394daff218d222e260dbc4543b6d4e49aa4700cc0a9233e86a) on L1 & L2s have rights necessary for disabling deposits & withdrawals in case of the emergency. 10. Once staking design is available in the future, upgrade contract implementations on L1 & L2s; potentially ossify proxies. ### First launches Lido has picked two of the most popular L2 networks for the first launches – Arbitrum and Optimism. They have been picked based on many parameters, including DeFi activity, the TVL, technological difficulty of bridging assets, network security track records, and the presence of Lido’s longtime partners on the said networks. The first step of L2 expansion is simply bridging Ethereum staking tokens on Arbitrum and Optimism, while carefully preserving the main properties of Lido’s yield-bearing tokens. Due to rebasing nature of stETH, bridging it to other networks adds a whole level of difficulty to the process, so it has been decided to go with the wrapped version of stETH, namely wstETH. ### Technical details The custom bridging contracts for both Optimism and Arbitrum native bridges have been developed by Lido dev team. As usually, the code has been submitted for audit and considered safe after all the required fixes have been applied. You can find the audit report [here](https://github.com/lidofinance/audits/blob/main/Oxorio%20Lido%20L2%20Smart%20Contracts%20Security%20Audit%20Report%2007-2022.pdf). The smart contracts have been recently deployed, all the contract addressed are now [listed on Lido docs hub](https://docs.lido.fi/deployed-contracts/#lido-on-l2). Both bridges are owned by Lido DAO on L1 (by the [Aragon Agent app](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) to be precise). This means, no actions can be performed on bridges without explicit Lido DAO approval (beside pausing the bridges, [find details below](#Emergency-brakes)). Just like the L1 part of the setup, the L2 one is also designed to be upgradeable. Initially, we’ve [planned for having governance multi-sigs](https://research.lido.fi/t/wsteth-on-optimism-bridging-security-management/2427) to perform future upgrades, but in the end we found out our partners from the AAVE team have already solved this very issue with their [AAVE Governance Cross-Chain bridges](https://github.com/aave/governance-crosschain-bridges). This solution allows for trustless execution arbitrary actions on L2s after governance approval on Ethereum. Smart contracts developed by AAVE are currently under the audit by ChainSecurity. The code had been reviewed & deployed by our team with no changes: - on Arbitrum: [`0x1dcA41859Cd23b526CBe74dA8F48aC96e14B1A29`](https://arbiscan.io/address/0x1dca41859cd23b526cbe74da8f48ac96e14b1a29) - on Optimism [`0xefa0db536d2c8089685630fafe88cf7805966fc3`](https://optimistic.etherscan.io/address/0xefa0db536d2c8089685630fafe88cf7805966fc3) ### Emergency brakes For security, Emergency Brakes multi-sigs have been set up on Ethereum Mainnet, Optimism and Arbitrum, following [the proposal](https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608) and [the passed snapshot voting](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2b368b535b2024394daff218d222e260dbc4543b6d4e49aa4700cc0a9233e86a). The only lever available to these multi-sigs is pause deposits/withdrawals on the respective network. However, only the Aragon Agent is capable of resuming bridge operations. The [multi-sig addresses](https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs) on each network are: - Ethereum: [`0x73b047fe6337183A454c5217241D780a932777bD`](https://gnosis-safe.io/app/eth:0x73b047fe6337183A454c5217241D780a932777bD/home) - Optimism: [`0x4Cf8fE0A4c2539F7EFDD2047d8A5D46F14613088`](https://gnosis-safe.io/app/oeth:0x4Cf8fE0A4c2539F7EFDD2047d8A5D46F14613088/home) - Arbitrum: [`0xfDCf209A213a0b3C403d543F87E74FCbcA11de34`](https://gnosis-safe.io/app/arb1:0xfDCf209A213a0b3C403d543F87E74FCbcA11de34/home) On every network multi-sig composition is 3/5 of - @psirex with address `0x2a61d3ba5030Ef471C74f612962c7367ECa3a62d` - @vsh with address `0x2a96805188e583dd760785A0dE93128504DDd5c7` - @kadmil with address `0x6f5c9B92DC47C89155930E708fBc305b55A5519A` - @ujenjt with address `0xdd19274b614b5ecAcf493Bc43C380ef6B8dfB56c` - @folkyatina with address `0xCFfE0F3B089e46D8212408Ba061c425776E64322` ### Next steps Both Arbitrum and Optimism bridges have been deployed in the ‘paused’ state, which means deposits and withdrawals are disabled at the moment. We’re looking to enabling bridging, so we will be starting the snapshot vote on the matter once the public audit for the Governance Bridging contracts is available. Please note, that upon deployment [the Lido dev team multi-sig](https://docs.lido.fi/deployed-contracts#lido-dao-multisigs) has role to unpause deposits on L1 side. If the snapshot passes, the dev team multi-sig will enable bridging & renounce admin role on the bridge contracts. --- _[View the full topic](https://research.lido.fi/t/lido-on-l2-first-launches/2786)._