• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
LidoLidoby0xDbBC6A93ae517D3ea568C04219cbBBd025f01CB6zuzu_eeka

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

Voting ended over 1 year agoSucceeded

The proposal is to recognize the wstETH token bridging endpoints for BNB by the Lido DAO as canonical. If Snapshot passes, the Lido DAO will control the endpoints of wstETH token contract 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 underlying bridge infrastructure itself, but having the ability to append/remove additional bridge verifiers via an on-chain DAO vote.

The expected technical capabilities of the DAO-representing contracts, contingent on the DAO recognition:

  1. Proxy admin capability by Lido DAO Aragon Agent contract on Ethereum
    1. Contract Address: 0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c
  2. Proxy admin capability by Lido a.DI CrossChain Executor on BNB
    1. Contract Address: 0x8E5175D17f74d1D512de59b2f5d5A5d8177A123d
  3. Pausability by Emergency Brakes multisig
    1. Ethereum: 0x73b047fe6337183A454c5217241D780a932777bD
    2. BNB: 0xC2b778fCc3FF311Cf1abBF4E53880277bfD14C8f

This initiative has been undertaken by Wormhole and Axelar contributors who deployed the wstETH canonical bridge to BNB being the first multi-verifier bridge proposed to be recognized by Lido DAO for wstETH after the corresponding temp check vote passed.

Motivation

stETH is a key token in the Ethereum ecosystem powering much of defi and new innovation in recent years. Today, it has a market cap of over $30B and well over 450,000 holders, and its importance has only continued to grow over the years. BNB chain remains one of crypto’s most important ecosystems with over $4.5B in tvl and consistently boasts a massive number of daily active users. Introducing a canonical, community approved wstETH to BNB chain will reduce friction in adoption and ultimately enhance growth for the token as well as for the Lido DAO.

Audits

  • WstEthL2Token Cyfrin Audit Report
  • Wormhole Native Token Transfers (NTT), including Wormhole Transceiver
    • Cyfrin Audit Report
    • Cantina Audit Report
    • Cyfrin Audit on the diff between their previous audit and NTT v1.1.0+evm, which was used for this deployment
  • Axelar Transceiver Cyfrin Audit Report

Mainnet Contracts

Newly Deployed Contracts

  • Ethereum:
    • NTT Manager: 0xb948a93827d68a82F6513Ad178964Da487fe2BD9
    • Wormhole Transceiver: 0xA1ACC1e6edaB281Febd91E3515093F1DE81F25c0
    • Axelar Transceiver: 0x723AEAD29acee7E9281C32D11eA4ed0070c41B13
    • Transceiver Structs: 0xf0396a8077eda579f657B5E6F3c3F5e8EE81972b
  • BNB:
    • WstEthL2Token: 0x26c5e01524d2E6280A48F2c50fF6De7e52E9611C
    • NTT Manager: 0x6981F5621691CBfE3DdD524dE71076b79F0A0278
    • Wormhole Transceiver: 0xbe3F7e06872E0dF6CD7FF35B7aa4Bb1446DC9986
    • Axelar Transceiver: 0x723AEAD29acee7E9281C32D11eA4ed0070c41B13
    • Transceiver Structs: 0xf0396a8077eda579f657B5E6F3c3F5e8EE81972b

Deployment Artifacts and Levers Setup

  • Ethereum
    • NTT Manager
      • Outbound Rate Limit: 30,000 wstETH
      • Inbound Rate Limit from BNB: 30,000 wstETH
      • Owner / Pauser: Interim Multisig
    • Wormhole Transceiver
      • Wormhole Core Contract Address: 0x98f3c9e6E3fAce36bAAd05FE09d375Ef1464288B
      • Wormhole Standard Relaying Contract Address: 0x27428DD2d3DD32A4D7f7C497eAaa23130d894911
      • Wormhole Special Relaying Contract Address: 0x63BE47835c7D66c4aA5B2C688Dc6ed9771c94C74
    • Axelar Transceiver
      • Axelar Gateway Contract Address: 0x4F4495243837681061C4743b74B3eEdf548D56A5
      • Axelar Gas Service Contract Address: 0x2d5d7d31F671F86C782533cc367F14109a082712
  • BNB
    • WstEthL2Token
      • Owner: Interim Multisig
      • Minter: NTT Manager contract on BNB
    • NTT Manager
      • Outbound Rate Limit: 30,000 wstETH / per day
      • Inbound Rate Limit from BNB: 30,000 wstETH / per day
      • Owner / Pauser: Interim Multisig
    • Wormhole Transceiver
      • Wormhole Core Contract Address: 0x98f3c9e6E3fAce36bAAd05FE09d375Ef1464288B
      • Wormhole Standard Relaying Contract Address: 0x27428DD2d3DD32A4D7f7C497eAaa23130d894911
      • Wormhole Special Relaying Contract Address: 0x63BE47835c7D66c4aA5B2C688Dc6ed9771c94C74
    • Axelar Transceiver
      • Axelar Gateway Contract Address: 0x304acf330bbE08d1e512eefaa92F6a57871fD895
      • Axelar Gas Service Contract Address: 0x2d5d7d31F671F86C782533cc367F14109a082712

Off-Chain Vote

Recognize
50.28M LDO100%
Don’t recognize
88.68 LDO0%
Download mobile app to vote

Discussion

LidoShould the Lido DAO recognize the wstETH Bridge Endpoints on BNB as canonical?

Timeline

Aug 02, 2024Proposal created
Aug 02, 2024Proposal vote started
Aug 09, 2024Proposal vote ended
Oct 31, 2025Proposal updated