Should the Lido DAO recognize the wstETH Bridge Endpoints on Mode as canonical?

The proposal is to recognize the wstETH token bridging endpoints for Mode by the Lido DAO as canonical. If Snapshot passes, the Lido DAO will control the endpoints of wstETH token contract (including the token contract on Mode itself) as a proxy admin. Lido DAO will only have the upgrade authority of the wstETH proxy contract, and will not be able to manage the native bridge itself.

The Mode Team is submitting this proposal to the community for the deployment of wstETH on Mode.

Motivation

wstETH has already been deployed to Optimism and Base, two of the biggest L2s that are also in the Superchain. The Mode core team suggests that it is strategically beneficial for the Lido DAO to also consider Mode as the next ecosystem to deploy their token. Mode has received support from Optimism in the form of an OP grant worth 2 million OP. As a key token, wstETH plays a vital role in DeFi activities across network segments.

The proposal aims to enhance wstETH adoption on Mode by signaling the Lido DAO’s recognition of the bridge endpoints.

Audits

To better form an opinion you may consider reading through the audit reports for:

• Governance crosschain bridges (OptimismBridgeExecutor)
• wstETH token bridge (L1ERC20TokenBridge, ERC20Bridged, L2ERC20TokenBridge)
• Mainnet verification report

Deployment artifacts and levers setup

The deployment is done using the exact codebase previously used for wstETH on Optimism and wstETH on Base bridge endpoints as the Mode network is OP-stack compatible.

Deployments on Mainnet (L1) and Mode (L2):

• OptimismBridgeExecutor on L2: 0x2aCeC6D8ABA90685927b61968D84CfFf6192B32C (Ethereum to Mode decisions forwarder for the Lido DAO Agent)
• L1ERC20TokenBridge on L1 (proxy): 0xD0DeA0a3bd8E4D55170943129c025d3fe0493F2A (Ethereum token bridge part for wstETH)
  • L1ERC20TokenBridge on L1 (implementation): 0xE6A4ED59Ec73eD78aE3A10294c99F0EE18A6bF76
• ERC20Bridged on L2 (proxy): 0x98f96A4B34D03a2E6f225B28b8f8Cb1279562d81 (Mode representation for wstETH proposed as the canonical one)
  • ERC20Bridged on L2 (implementation): 0xF27b1B121e55A13047d66dC4AAA8c17BA72c762A
• L2ERC20TokenBridge on L2 (proxy): 0xb8161F28a5a38cE58f155D9A96bDAc0104985FAc (Mode token bridge part for wstETH)
  • L2ERC20TokenBridge on L2 (implementation): 0x488cDB57E9a1006ab77730fC8b19e1BB76e1cB97

Levers setup:

• OptimismBridgeExecutor
  • getEthereumBridgeExecutor is the Lido DAO Agent (admin)
• Ultimate admin and role holder on L1 is the Lido DAO Agent
  • 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
  • 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
  • WITHDRAWALS_DISABLER_ROLE for L1ERC20TokenBridge
  • DEPOSITS_DISABLER_ROLE for L1ERC20TokenBridge
• Emergency breaks msig on L2 is a newly created one 0x244912352A639001ceCFa208cDaa7CB474c9eadE
  • WITHDRAWALS_DISABLER_ROLE for L2ERC20TokenBridge
  • DEPOSITS_DISABLER_ROLE for L2ERC20TokenBridge