# wstETH Deployment on Mode **URL:** \ **Category:** Proposals\ **Created:** [April 30, 2024, 11:25am UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365 "2024-04-30T11:25:51Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![AdamTheWhale](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@AdamTheWhale](https://research.lido.fi/u/AdamTheWhale)\ **Post date:** [April 30, 2024, 11:25am UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/1 "2024-04-30T11:25:52Z")
## Introduction: The Mode core team proposes the deployment of wstETH (Wrapped staked ETH) to Mode, with the ultimate goal of acceptance of ownership of the wstETH bridging components by the Lido DAO. #### 1. Mode’s Rapid Growth and Ecosystem: Mode is positioned to be the DeFi hub of the Superchain and has received support from Optimism in the form of an OP grant worth 2 million OP. Mode launched just 12 weeks ago and has already grown to 700m in overall TVL and an impressive 550m in dApp TVL in a short timeline since mainnet release. We see these numbers continue to grow as we bring in new assets like wstETH and useful DeFi products to the ecosystem. wstETH has already been deployed to Optimism and Base, two of the biggest L2s that are also in the Superchain. The Mode core team feels it is strategically beneficial for the Lido DAO to also consider Mode as the next ecosystem to deploy their asset. Reference: [DeFiLlama Ranking](https://defillama.com/chain/Mode) | [L2Beat Ranking](https://l2beat.com/scaling/projects/mode) #### 2. High Demand for wstETH: Lido is a very important and trusted asset within the overall crypto ecosystem. It is the [top reward bearing asset by marketcap](https://www.coingecko.com/en/all-cryptocurrencies) and its deployment on Mode would unlock new opportunities for our users and the dApps that are deployed within Mode. All of the top dApps inside of the Mode ecosystem would love to integrate wstETH from the moment the asset is live on the chain. Our user base would enjoy having access to the reward bearing asset within the Mode ecosystem so they can increase their efficiency for their onchain strategies. Mode also has an accelerator program is centred around products that optimize rewards for onchain users. We would love to include wstETH as an asset developers can build off of if the Lido DAO decides to accept ownership of the bridging components outlined in this proposal. #### 3. Canonical Bridge for wstETH: Like OP and Base the best approach for deploying wstETH on Mode is through the canonical bridge. The Mode core team sees the importance of Lido to our long term success and took action to deploy wstETH to Mode testnet using the same open-source solution used for Optimism deployment ([GitHub - lidofinance/lido-l2 14](https://github.com/lidofinance/lido-l2)). The management of wstETH bridging components are designed to be controlled by the Lido DAO (GitHub - [lidofinance/governance-crosschain-bridges](https://github.com/lidofinance/governance-crosschain-bridges): This repo contains the crosschain governance bridges used for the Aave markets deployed across different networks. All of the pieces are in place for wstETH to come to Mode and we would propose Lido DAO formally accept ownership of the wstETH bridging components mentioned through signalling a snapshot vote. ## Conclusion If Lido chooses to accept the deployment of wstETH within the Mode blockchain and take over ownership of the bridging components associated with its deployment this would be a positive and significant step towards diversifying the reward bearing assets within Mode’s ecosystem and open up a new userbase for Lido. Mode users would love to use wstETH for their strategies on dApps within Mode and the recent growth of staking assets in the ecosystem highlights that assets like wstETH will have a bright future within Mode. ## Audits - [Governance crosschain bridges (OptimismBridgeExecutor):](https://github.com/lidofinance/audits/blob/main/L2/Governance-Crosschain-Bridges-2022-08-Oxorio-Audit%20Report.pdf) - [wstETH token bridge (L1ERC20TokenBridge, ERC20Bridged, L2ERC20TokenBridge):](https://github.com/lidofinance/audits/blob/main/L2/Lido-L2-2022-07-Oxorio-Smart-Contracts-Security-Audit-Report.pdf) ## Deployment artifacts and levers setup #### Deployments on Mainnet (L1) and Mode (L2): - OptimismBridgeExecutor on L2: [0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C](https://explorer.mode.network/address/0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C?tab=contract) (Ethereum to Mode decisions forwarder for the Lido DAO Agent) - L1ERC20TokenBridge on L1: [0xD0DeA0a3bd8E4D55170943129c025d3fe0493F2A](https://etherscan.io/address/0xD0DeA0a3bd8E4D55170943129c025d3fe0493F2A#readContract)( Ethereum token bridge part for wstETH) (implementation: [Address: 0xe6a4ed59...e18a6bf76 | Etherscan](https://etherscan.io/address/0xe6a4ed59ec73ed78ae3a10294c99f0ee18a6bf76#code)) - ERC20Bridged on L2: [0x98f96A4B34D03a2E6f225B28b8f8Cb1279562d81](https://explorer.mode.network/address/0x98f96A4B34D03a2E6f225B28b8f8Cb1279562d81) (Mode representation for wstETH proposed as the canonical one) (implementation: [Mode Mainnet address details for 0xF27b1B121e55A13047d66dC4AAA8c17BA72c762A | Blockscout](https://explorer.mode.network/address/0xF27b1B121e55A13047d66dC4AAA8c17BA72c762A)) - L2ERC20TokenBridge on L2: [0xb8161F28a5a38cE58f155D9A96bDAc0104985FAc](https://explorer.mode.network/address/0xb8161F28a5a38cE58f155D9A96bDAc0104985FAc) (Mode token bridge part for wstETH) (implementation: [Mode Mainnet address details for 0x488cDB57E9a1006ab77730fC8b19e1BB76e1cB97 | Blockscout](https://explorer.mode.network/address/0x488cDB57E9a1006ab77730fC8b19e1BB76e1cB97)) #### Levers setup: - OptimismBridgeExecutor - [getEthereumBridgeExecutor 4](https://explorer.mode.network:443/address/0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C?tab=read_contract#c3a76886) is the [Lido DAO Agent (admin)](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c#code) (implementation for lido dao agent - admin: [Lido: Agent Impl | Address: 0x3a93c17f...5cc89dd37 | Etherscan](https://etherscan.io/address/0x3a93c17fc82cc33420d1809dda9fb715cc89dd37#code)) - Ultimate admin and role holder on L1 is the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c#code) (implementation for lido dao agent: [Lido: Agent Impl | Address: 0x3a93c17f...5cc89dd37 | Etherscan](https://etherscan.io/address/0x3a93c17fc82cc33420d1809dda9fb715cc89dd37#code)) - Proxy admin for L1ERC20TokenBridge - DEFAULT\_ADMIN\_ROLE for L1ERC20TokenBridge - WITHDRAWALS\_DISABLER\_ROLE for L1ERC20TokenBridge - WITHDRAWALS\_ENABLER\_ROLE for L1ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L1ERC20TokenBridge - DEPOSITS\_ENABLER\_ROLE for L1ERC20TokenBridge - Ultimate admin and role holder on L2 is the [OptimismBridgeExecutor](https://explorer.mode.network/address/0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C?tab=read_contract) - Proxies admin for ERC20Bridged, L2ERC20TokenBridge - DEFAULT\_ADMIN\_ROLE for L2ERC20TokenBridge - WITHDRAWALS\_DISABLER\_ROLE for L2ERC20TokenBridge - WITHDRAWALS\_ENABLER\_ROLE for L2ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L2ERC20TokenBridge - DEPOSITS\_ENABLER\_ROLE for L2ERC20TokenBridge - Emergency breaks on L1 uses this EOA account [0x73b047fe6337183A454c5217241D780a932777bD](https://docs.lido.fi/token-guides/wsteth-bridging-guide/#mainnet): - WITHDRAWALS\_DISABLER\_ROLE for L1ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L1ERC20TokenBridge - Emergency breaks msig on L2 is a newly created one [0x244912352A639001ceCFa208cDaa7CB474c9eadE](https://safe.optimism.io/home?safe=mode:0x244912352A639001ceCFa208cDaa7CB474c9eadE): - WITHDRAWALS\_DISABLER\_ROLE for L2ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L2ERC20TokenBridge ---
**Author:** ![AdamTheWhale](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@AdamTheWhale](https://research.lido.fi/u/AdamTheWhale)\ **Post date:** [June 5, 2024, 6:24pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/2 "2024-06-05T18:24:24Z")
After speaking with the staff at Mode and at Lido the following update has been made to the proposal. #### Deployments on Sepolia testnet (L1) and Mode (L2): - OptimismBridgeExecutor on L2: [0x442a6Bea15718588391C5d1dE261AB2c617eA703](https://sepolia.explorer.mode.network/address/0x442a6Bea15718588391C5d1dE261AB2c617eA703) (Sepolia to Mode decisions forwarder for the Lido DAO Agent) - L1ERC20TokenBridge on L1: [0x16B929D35B200EA0ae0B93EABc3Bf9Ad611BF18F](https://sepolia.etherscan.io/address/0x16B929D35B200EA0ae0B93EABc3Bf9Ad611BF18F#readContract) (Sepolia token bridge part for wstETH) (implementation: [Address: 0x8c1e68a7...7aec4d599 | Etherscan Sepolia](https://sepolia.etherscan.io/address/0x8c1e68a74e71594925c7d7a78ef43657aec4d599#code)) - ERC20Bridged on L2: [0x2C937931B5d544E3dff1d9D78c80d9772B55837A](https://sepolia.explorer.mode.network/address/0x2C937931B5d544E3dff1d9D78c80d9772B55837A) (Mode representation for wstETH proposed as the canonical one) (implementation: [Mode Sepolia address details for 0xC9C796E4CefdD38Eb462E84246bE41d500149162 | Blockscout](https://sepolia.explorer.mode.network/address/0xC9C796E4CefdD38Eb462E84246bE41d500149162)) - L2ERC20TokenBridge on L2: [0xd41a90e55bcfC1CbF96D78aE80BbCB56A6BA0008](https://sepolia.explorer.mode.network/address/0xd41a90e55bcfC1CbF96D78aE80BbCB56A6BA0008) (Mode token bridge part for wstETH) (implementation: [Mode Sepolia address details for 0x8Cc0183D53c8fB160BFB01fe49ff3E8A9Aa0B1F6 | Blockscout](https://sepolia.explorer.mode.network/address/0x8Cc0183D53c8fB160BFB01fe49ff3E8A9Aa0B1F6)) ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [June 13, 2024, 9:29pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/3 "2024-06-13T21:29:37Z")
Hey, thank you for posting the proposal! It would be great to see wstETH available on Superchain 🔴 Could you spot the expected integrations or projects that will be unlocked with wstETH on Mode? ---
**Author:** ![AdamTheWhale](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@AdamTheWhale](https://research.lido.fi/u/AdamTheWhale)\ **Post date:** [July 17, 2024, 2:08pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/4 "2024-07-17T14:08:52Z")
Hi TheDZhon here are a few that come to mind to start with: - [Balancer](https://balancer.fi/) (AMM) - [Ironclad](https://www.ironclad.finance/) (Lending and borrowing) - [Ionic](https://app.ionic.money/) (Lending and borrowing) - [BMX](https://www.bmx.trade/) (perp dex) If you have more product experiences you like to see with wstETH let us know and we can explore the ecosystem to see what is possible. ---
**Author:** ![AdamTheWhale](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@AdamTheWhale](https://research.lido.fi/u/AdamTheWhale)\ **Post date:** [July 17, 2024, 2:16pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/5 "2024-07-17T14:16:39Z")
Here is the Cantina mainnet verification report to bring wstETH to Mode. ![report-review-mode-wsteth-mainnet-verification-final copy](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/0/0c6f6c64589b92e3427557cac4dbe9ddbde6be2d.jpeg) ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [July 20, 2024, 10:06am UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/6 "2024-07-20T10:06:02Z")
GM, the verification report has been re-uploaded to GH for the sake of accessibility: > **[Mode-2024-07-18-Cantina-wstETH-deployment-verification.pdf](https://github.com/lidofinance/audits/blob/main/L2/Mode-2024-07-18-Cantina-wstETH-deployment-verification.pdf)** ---
**Author:** ![zuzu\_eeka](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/zuzu_eeka/32/1157_2.png) [@zuzu\_eeka](https://research.lido.fi/u/zuzu_eeka)\ **Post date:** [August 1, 2024, 1:32pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/7 "2024-08-01T13:32:49Z")
Hi @AdamTheWhale! Could you please also share the implementations’ addresses here ---
**Author:** ![AdamTheWhale](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@AdamTheWhale](https://research.lido.fi/u/AdamTheWhale)\ **Post date:** [August 1, 2024, 2:28pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/8 "2024-08-01T14:28:40Z")
Hello @zuzu_eeka - I updated the main post and Sepolia addresses to include the implementation addresses as requested. ---
**Author:** ![arwer13](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/arwer13/32/798_2.png) [@arwer13](https://research.lido.fi/u/arwer13)\ **Post date:** [August 1, 2024, 4:11pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/9 "2024-08-01T16:11:39Z")
A working group of the Lido on Ethereum protocol contributors (@TheDZhon, @arwer13) has evaluated the current proposal and ended up with the following: - the [proposed contracts](https://docs.lido.fi/deployed-contracts/#mode) adhere to the established design of the wstETH token on Layer 2 solutions described in depth in the [wstETH rollup bridging guide](https://docs.lido.fi/token-guides/wsteth-bridging-guide); - the deployments are in full correspondence with the presented [audit](https://github.com/lidofinance/audits/blob/main/L2/Mode-2024-07-18-Cantina-wstETH-deployment-verification.pdf), source code, and bytecode wise, with no significant issues found; - all configurations and parameters are relevant and meet expectations, according to [this state configuration file](https://github.com/lidofinance/state-mate/blob/92e6d38b4be9adce6cf4f0b6376bf59fd7c67d5e/configs/mode/mainnet.yml); - the access control list (ACL) configuration appears reasonable regarding the Lido DAO ownership and usage of the [Emergency Breaks](https://research.lido.fi/t/emergency-brakes-signer-rotation/5286) setup for [both L1 and L2 counterparts](https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs). Namely, the ACL and levers setup is: - For [OptimismBridgeExecutor](https://explorer.mode.network/address/0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C) - `getEthereumGovernanceExecutor` is [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) (admin) - On L1ERC20TokenBridge contract [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) is holder of roles: - `DEFAULT_ADMIN_ROLE` - `WITHDRAWALS_DISABLER_ROLE` - `WITHDRAWALS_ENABLER_ROLE` - `DEPOSITS_DISABLER_ROLE` - `DEPOSITS_ENABLER_ROLE` - On L2ERC20TokenBridge contract [ScrollBridgeExecutor](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) is holder of roles: - `DEFAULT_ADMIN_ROLE` for L2ERC20TokenBridge - `WITHDRAWALS_DISABLER_ROLE` for L2ERC20TokenBridge - `WITHDRAWALS_ENABLER_ROLE` for L2ERC20TokenBridge - `DEPOSITS_DISABLER_ROLE` for L2ERC20TokenBridge - `DEPOSITS_ENABLER_ROLE` for L2ERC20TokenBridge - Emergency breaks msig on L1 is [0x73b047fe6337183A454c5217241D780a932777bD](https://snapshot.org/#/lido-snapshot.eth/proposal/0xfe2a6a6506a642b616118363bc29aa83dd9ef2ec80447bb607a8f52c0a96aed0), 3/5 threshold, holds roles: - `WITHDRAWALS_DISABLER_ROLE` of L1ERC20TokenBridge - `DEPOSITS_DISABLER_ROLE` of L1ERC20TokenBridge - Emergency breaks msig on L2 is a new one [`0x244912352A639001ceCFa208cDaa7CB474c9eadE`](https://safe.optimism.io/home?safe=mode:0x244912352A639001ceCFa208cDaa7CB474c9eadE) inheriting the same EOAs as for L1, 3/5 threshold, holds roles: - `WITHDRAWALS_DISABLER_ROLE` of L2ERC20TokenBridge - `DEPOSITS_DISABLER_ROLE` of L2ERC20TokenBridge ---
**Author:** ![governance-data-bot](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/governance-data-bot/32/2204_2.png) [@governance-data-bot](https://research.lido.fi/u/governance-data-bot)\ **Post date:** [August 2, 2024, 6:17pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/10 "2024-08-02T18:17:35Z")
## Snapshot vote started The [Should the Lido DAO recognize the wstETH Bridge Endpoints on Mode as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x6bc51c2b07a9345a03a0bc0acb72ccc9f63879c981f3a6954164d110c5d330b2) Snapshot has started! Please cast your votes before Fri, 09 Aug 2024 16:00:00 GMT 🙏 ---
**Author:** ![governance-data-bot](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/governance-data-bot/32/2204_2.png) [@governance-data-bot](https://research.lido.fi/u/governance-data-bot)\ **Post date:** [August 9, 2024, 4:07pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mode/7365/11 "2024-08-09T16:07:12Z")
## Snapshot vote ended Thank you all who participated in [Should the Lido DAO recognize the wstETH Bridge Endpoints on Mode as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x6bc51c2b07a9345a03a0bc0acb72ccc9f63879c981f3a6954164d110c5d330b2) Snapshot, we reached a quorum! 🙏 The results are: **Recognize** : 50.3M LDO **Don’t recognize** : 1 LDO