# wstETH Deployment on Mantle **URL:** \ **Category:** Lido Multichain\ **Created:** [November 22, 2023, 7:05am UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991 "2023-11-22T07:05:38Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Mantle](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/mantle/32/3681_2.png) [@Mantle](https://research.lido.fi/u/Mantle)\ **Post date:** [November 22, 2023, 7:05am UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/1 "2023-11-22T07:05:38Z")
## 1. Introduction The Mantle Core Contributor Team is submitting this proposal to the community for the deployment of wstETH on Mantle. [Mantle Network](https://mantle.xyz/) is an optimistic Ethereum layer-2 (L2) solution with an EVM-compatible execution environment. Mantle is DAO-governed and employs a modular approach to execution, consensus, settlement, and data availability. In addition to a burgeoning ecosystem with 110+ dApps and counting, Mantle counts among its partners Game7, HyperPlay, EduDAO, Sozu Haus, and EigenLayer. The DAO-led community-driven Mantle possesses one of the largest on-chain treasuries — and the largest when discounting native tokens — including nearly 270K ETH/wstETH/WETH, priming it to be a major player in ETH LST and LSDFi. ## 2. Mantle Ecosystem Growth Since its launch, Mantle has seen more than [22.5 million transactions and over 827,000 unique addresses](https://explorer.mantle.xyz/) transact on the network. At its peak, it reached [54,650](https://mantlescan.info/chart/activeaddresses?g=1) daily active addresses. To date, more than 3,900 developers have launched over [71,452](https://explorer.mantle.xyz/verified-contracts) contracts. As of now, Mantle has approximately [~$105 million](https://etherscan.io/address/0x95fc37a27a2f68e3a647cdc081f0a89bb47c3012) total value bridged (TVB) and around [~$156 million](https://l2beat.com/scaling/projects/mantle) in total value locked (TVL) across more than 40 different DeFi protocols, according to L2Beat. These metrics indicate a thriving ecosystem that Lido could benefit from by tapping into an existing, active user base. #### Mantle Treasury The Mantle Treasury is unmatched in terms of size. The treasury holds more than $740 million in assets excluding its own tokens (MNT) — [the largest of any other DAO](https://defillama.com/protocol/mantle-treasury#treasury) — which means ample runway to weather multiple cycles. It also has around $1.42 billion worth of MNT tokens, which provides a significant war chest to incentivize and bootstrap ecosystem growth. Two proposals, [MIP-24](https://snapshot.org/#/bitdao.eth/proposal/0x395e58727038c5a855977248a1dd6e07356674c11f0293eb4b0f68de4e73792f), and [MIP-25](https://snapshot.org/#/bitdao.eth/proposal/0xa34107e34b4dc4ff4cd16b77d66e62a51f4d35457a4f4b1f68ab8ac821f58561), have since been passed to establish two key authorities that will carry out ecosystem funding and bootstrapping activities. #### Mantle EcoFund The [Mantle EcoFund](https://snapshot.org/#/bitdao.eth/proposal/0x395e58727038c5a855977248a1dd6e07356674c11f0293eb4b0f68de4e73792f) is a strategic initiative designed to inject $200 million into the Mantle ecosystem over the next three years. Comprising $100 million from Mantle’s own Treasury and an additional $100 million matched by Strategic Venture Partners, the EcoFund serves multiple key objectives. These include supporting entrepreneurs and technologies within the Mantle ecosystem, accelerating adoption among developers and dApps, and incentivizing strategic partnerships. The fund will act as a seed investor in high-potential, early-stage projects and has the flexibility to provide additional liquidity or follow-on investments to successful ventures. #### Mantle Economics Committee The Mantle Economics Committee (EC) is a specialized sub-governance body operating under Mantle Governance. It will focus primarily on making informed, risk-averse decisions about the allocation of Mantle Treasury assets, without directly holding custody of these assets. The Committee is authorized to manage Mantle LSP and Lido ETH staking strategies, with allowances up to 200k ETH, and has the flexibility to enter and exit these strategies based on commercial negotiations and risk evaluations. The Committee adopts a highly conservative risk management approach and operates within governance rules that prioritize caution in strategy entries while allowing quicker exits. Its diverse membership will include representatives from Mantle Governance, the Mantle community, and Mantle Core Contributor teams. As of the time of writing, the EC has since tabled their [first proposal](https://forum.mantle.xyz/t/ec-proposal-treasury-assets-in-support-of-applications/7943) to allocate up to: - $160 million in liquidity support for applications - $60 million in seed liquidity for RWA-backed stablecoins - $18 million in liquidity support for third-party bridges ## 3. wstETH Demand Demand for Lido (w)stETH is significantly driven by its utility within major ecosystems, which are leveraging its composability in various DeFi protocols. Notably, wstETH’s overwhelming market share of staked ETH enhances its desirability. Additionally, wstETH’s versatility, being used for a range of DeFi applications including collateral, lending, farming, indexing, minting, vaults, and stables, amplifies its demand further. Mantle aims to leverage this demand for ETH liquid staking tokens and make wstETH one of the core building blocks of the Mantle ecosystem, as well as a core asset of its treasury to sustainably grow its protocol-owned liquidity (POL). ## 4. Implementation wstETH has already been deployed onto Mantle via the canonical bridge. This proposed new deployment will be replacing the existing wstETH with a one-way migration pool opened for users to migrate. - Solution smart contracts - [GitHub - mantlenetworkio/lido-l2](https://github.com/mantlenetworkio/lido-l2/) The Mantle team has taken the initiative to deploy wstETH to Mantle testnet that uses as a reference the wstETH on Optimism deployment ([lidofinance - lido-l2](https://github.com/lidofinance/lido-l2/tree/main/contracts/optimism)) with some UX enhancements like ERC-2612. - All management of the wstETH bridging components is designed to be performed by the Lido DAO via the previously developed cross-chain governance bridge ([GitHub - lidofinance/governance-crosschain-bridges: This repo contains the crosschain governance bridges used for the aave markets deployed across different networks](https://github.com/lidofinance/governance-crosschain-bridges)) - Ownership & Governance - Emergency brakes ## 5. Conclusion In conclusion, deploying wstETH on Mantle is a strategic move to form a mutually beneficial partnership with Lido. Mantle, with its established ecosystem and strong treasury, provides a viable platform for expanding wstETH’s utility and adoption. Conversely, integrating wstETH could enhance Mantle’s DeFi offerings and possibly attract more developers and users. The existing demand for wstETH, along with Mantle’s growth initiatives like the EcoFund and its governance structures, supports a promising integration. This proposal, therefore, encourages the community to support a collaboration that expands the utility of wstETH and aids Mantle in advancing its position in the Ethereum Layer 2 space and the broader blockchain sector. We propose that the Lido DAO formally accept ownership of the mainnet deployment of the wstETH bridging components referenced through a formal vote. ## 6. Audits - [Governance crosschain bridges (OptimismBridgeExecutor)](https://github.com/lidofinance/audits/blob/main/Oxorio%20Governance%20Crosschain%20Bridges%20Smart%20Contracts%20Security%20Audit%20Report%2008-2022.pdf) - [wstETH on Mantle (L1ERC20TokenBridge, L2ERC20TokenBridge, ERC20BridgedPermit)](https://drive.google.com/file/d/1wbmD-sg_LYu2tWVp2YWjydltDF4OlueG/view?usp=sharing) ## 7. Contracts - Testnet contracts: - Mainnet contracts: ## 8. Ownership, roles, and levers Mainnet setup - To be presented concurrently with the Mainnet deployment ---
**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:** [November 23, 2023, 10:59am UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/2 "2023-11-23T10:59:09Z")
Thank you for the well-crafted proposal! As a participant of the Network Expansion Group (NEW) I’d like to mention I’m going to participate in the setup review after the mainnet addresses are published. ---
**Author:** ![DZahar0v](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dzahar0v/32/3480_2.png) [@DZahar0v](https://research.lido.fi/u/DZahar0v)\ **Post date:** [November 29, 2023, 9:06am UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/3 "2023-11-29T09:06:14Z")
[MixBytes](https://mixbytes.io/) team was engaged and has verified wstETH deployment on Mantle. Three security researchers checked the presented information according to the internal checklist. The results are as follows: - Mantle network has slightly different features and behavior than Optimism, but these features do not affect wstETH and DAO decision bridging, so presented contracts and architecture can be used without any additional changes to consider. - Deployed contracts match the audited scope. All findings from the reports are addressed in the contracts. - All contracts were correctly deployed and initialized. - The ACL setup was implemented as the NEW contributors requested from the Mantle team without any additional roles and addresses. It is worth noting that the Mantle native explorer works differently than ethescan-like explorers in some cases. For example, to check a multi-sig structure, it is better to use [https://multisig.mantle.xyz/](https://multisig.mantle.xyz/) than native explorer. Also, these contracts [OssifiableProxy](https://explorer.mantle.xyz/address/0x9c46560D6209743968cC24150893631A39AfDe4d/contracts#address-tabs) and [OssifiableProxy](https://explorer.mantle.xyz/address/0x458ed78EB972a369799fb278c0243b25e5242A83/contracts#address-tabs) contain some unnecessary contracts in the deployment verification section. ---
**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:** [November 30, 2023, 4:38pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/4 "2023-11-30T16:38:44Z")
A working group of Lido on Ethereum protocol contributors and NEW participants (@arwer13 and @TheDZhon) has evaluated the current proposal in depth and presents the following findings and observations: - The [proposed contracts](https://docs.lido.fi/deployed-contracts/#mantle) are iterations of the wstETH solution on Optimism. Notable improvements include the addition of ERC-2612 support and resolution of issue [#53](https://github.com/lidofinance/lido-l2/issues/53). - The deployment preserves the integrity with the audits [`[1]`](https://drive.google.com/file/d/1wbmD-sg_LYu2tWVp2YWjydltDF4OlueG/view), [`[2]`](https://github.com/lidofinance/audits/blob/main/Oxorio%20Governance%20Crosschain%20Bridges%20Smart%20Contracts%20Security%20Audit%20Report%2008-2022.pdf) (source code, and bytecode wise, with no critical/high issues left unresolved) - All configurations and parameters look appropriate and meet expectations - The access control list (ACL) setup appears valid concerning the Lido DAO ownership and usage of the [Emergency Breaks](https://research.lido.fi/t/emergency-brakes-signer-rotation/5286) configuration for [both L1 and L2 counterparts](https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs). * * * Complete ACL and levers setup: - for the [Mantle Governance Bridge Executor](https://explorer.mantle.xyz/address/0x3a7B055BF88CdC59D20D0245809C6E6B3c5819dd) (`OptimismBridgeExecutor` contract is used) - `getEthereumGovernanceExecutor` is the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - A bridge admin and role holder on L1 is the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - Proxy admin for L1ERC20Bridge - DEFAULT\_ADMIN\_ROLE for L1ERC20Bridge - WITHDRAWALS\_DISABLER\_ROLE for L1ERC20Bridge - WITHDRAWALS\_ENABLER\_ROLE for L1ERC20Bridge - DEPOSITS\_DISABLER\_ROLE for L1ERC20Bridge - DEPOSITS\_ENABLER\_ROLE for L1ERC20Bridge - A bridge admin and role holder on L2 is the [Mantle Governance Bridge Executor](https://explorer.mantle.xyz/address/0x3a7B055BF88CdC59D20D0245809C6E6B3c5819dd) - Proxy admin for 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 - for the proposed wstETH token on L2 ([ERC20BridgedPermit](http://explorer.mantle.xyz/address/0x458ed78eb972a369799fb278c0243b25e5242a83)) - Proxy admin is the [Mantle Governance Bridge Executor](https://explorer.mantle.xyz/address/0x3a7B055BF88CdC59D20D0245809C6E6B3c5819dd) - Emergency breaks msig on L1 is [`0x73b047fe6337183A454c5217241D780a932777bD`](https://snapshot.org/#/lido-snapshot.eth/proposal/0xfe2a6a6506a642b616118363bc29aa83dd9ef2ec80447bb607a8f52c0a96aed0), 3/5 threshold: - WITHDRAWALS\_DISABLER\_ROLE for L1ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L1ERC20TokenBridge - Emergency breaks msig on L2 is a new one [`0xa8579D42E34398267dE16e6eeeCdb7ED0EFF953C`](https://multisig.mantle.xyz/home?safe=mantle:0xa8579D42E34398267dE16e6eeeCdb7ED0EFF953C) inheriting the same EOAs as for L1, 3/5 threshold: - WITHDRAWALS\_DISABLER\_ROLE for L2ERC20TokenBridge - DEPOSITS\_DISABLER\_ROLE for L2ERC20TokenBridge - An initial deployer has no remaining permissions and levers assigned * * * We would suggest the Lido DAO consider accepting the wstETH token deployment on Mantle. This step appears logical given [w]stETH’s representation of the broader ecosystem. ---
**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:** [December 7, 2023, 4:06pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/5 "2023-12-07T16:06:35Z")
## Snapshot vote started The [Should the Lido DAO recognize the wstETH Bridge Endpoints on Mantle as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x1d38c11b27590ab5c69ca21c5d2545d53b7f5150dada7e05f89d500ede5becad) Snapshot has started! Please cast your votes before Thu, 14 Dec 2023 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:** [December 14, 2023, 4:06pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/6 "2023-12-14T16:06:51Z")
## Snapshot vote ended Unfortunately, the [Should the Lido DAO recognize the wstETH Bridge Endpoints on Mantle as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x1d38c11b27590ab5c69ca21c5d2545d53b7f5150dada7e05f89d500ede5becad) Snapshot hadn’t reached a quorum. ⛔ The results are: **Recognize** : 47.3M LDO **Don’t recognize** : 34.7k LDO ---
**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:** [December 18, 2023, 1:16pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/7 "2023-12-18T13:16:14Z")
## Snapshot vote started The [[rerun] Should the Lido DAO recognize the wstETH Bridge Endpoints on Mantle as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x349fa7409a99683405e71ddebaf5068f3dee7d4e6c9e4375198c4dc10c899bb9) Snapshot has started! Please cast your votes before Mon, 25 Dec 2023 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:** [December 25, 2023, 4:06pm UTC](https://research.lido.fi/t/wsteth-deployment-on-mantle/5991/8 "2023-12-25T16:06:06Z")
## Snapshot vote ended The [[rerun] Should the Lido DAO recognize the wstETH Bridge Endpoints on Mantle as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x349fa7409a99683405e71ddebaf5068f3dee7d4e6c9e4375198c4dc10c899bb9) Snapshot vote concluded! The results are: **Recognize** : 51.4M LDO **Don’t recognize** : 118 LDO