Lido proposes a two-of-three quorum for BNB Chain governance forwarding

What happened

A primary governance proposal specifies removing Wormhole from Lido's Ethereum-to-BNB governance route and reducing destination confirmations from three of four adapters to two of three.

What changed

The proposed configuration trades a three-bridge forgery threshold for a two-bridge threshold while restoring tolerance to one remaining bridge outage.

What did not change

The record does not establish an approved vote or executed configuration change. It proposes no change to core Ethereum stETH withdrawal mechanics.

Confirmed

• The proposal identifies CCIP, Hyperlane and LayerZero as the remaining adapters.
• It specifies destination-controller calls to reject Wormhole deliveries and require two confirmations, followed by disabling Ethereum forwarding through Wormhole.
• The governance record identifies the BNB CrossChainExecutor as owner of wstETH and associated bridge contracts.
• The stated next step is an upcoming on-chain vote through Dual Governance.

Still open

• Approval, vote identifier and execution transactions are not established.
• The proposal's account of lost Wormhole automatic delivery and current route availability has not been independently reproduced.
• The proposal describes immediate destination execution without a guardian veto window; current deployed authority and delay settings require verification.
• The approximately $4 million bridged exposure is the author's dated estimate.

What it means for an advisor

• Review the Lido diligence file's BNB wstETH owner-authority and messaging assumptions, including the proposed two-bridge compromise threshold.
• Verify current route availability, destination controls and eventual execution before updating the authority map.