Summary
This proposal seeks LDO token holders approval to revoke the recognized canonical status of (w)stETH bridge endpoints on zkSync Era, Mode, Scroll, Mantle, Swell, Zircuit, Soneium, Polygon PoS, and Lisk, where the conditions that originally motivated recognition no longer hold, and to authorize the Network Expansion Committee (NEC) to perform such revocations in the future under existing guardrails. The proposal aims to keep the multichain strategy lean and efficient by focusing on networks where (w)stETH is demonstrating meaningful adoption and by maintaining canonical recognition status accurately and intentionally.
No immediate action is required from holders of (w)stETH on the affected networks. The de-recognition of bridging endpoints does not place currently bridged or future-bridged tokens at risk, nor does it affect users’ ability to hold or use (w)stETH on these networks. This proposal does not seek to disable bridge infrastructure, force user migration, or make a technical judgment on the safety of any specific bridge.
Revoke Recognized Canonical Status of Selected (w)stETH Bridge Endpoints
Over the past several years, LDO token holders voted to expand (w)stETH across multiple chains by formally recognizing selected bridge endpoints as canonical. The Lido Multichain hub was launched as a community hub for an up-to-date list of supported networks, statistics, guides, and available integrations. The most recent bridge endpoints were recognized by the Network Expansion Committee (NEC), acting on behalf of Lido DAO.
We believe multichain should remain a core part of Lido DAO’s long-term strategy. As the program matures, we also see increasing value in differentiating between networks where (w)stETH is demonstrating meaningful adoption, and those where it is not, and in keeping canonical recognition focused on the former.
Recognition is not a one-way ratchet: it carries ongoing costs for monitoring, security oversight, incident response, communications, integration support, and handling user and integrator inbounds. That cost and focus are best allocated where LDO token holders and users see meaningful benefits.
Across the currently recognized chains, conditions have evolved unevenly. On several networks, the original integration thesis no longer holds — whether because the chain itself is winding down, the network’s ecosystem direction has shifted away from wstETH-relevant use cases, the chain centers its strategy on a competing native LST, or organic adoption simply has not materialized. In these cases, continued canonical recognition no longer reflects the deployment state, and revoking it helps keep the public list of endorsements accurate, intentional, and informative for users and integrators. Therefore, it is proposed to formally revoke the recognized canonical status of the following (w)stETH bridge endpoints:
| Chain | Rationale |
|---|---|
| zkSync Era | Underlying system bridge contract is being deprecated (only new deposits affected, not withdrawals); the official wstETH bridging UI has been retired and no new wstETH venues are in development on the network |
| Mode | All-time bridged TVL has never exceeded a few wstETH; no major integrations |
| Scroll | wstETH adoption both from a TVL and an integration perspective has remained limited |
| Mantle | Mantle’s ecosystem strategy centers on its own native LST and LRT (mETH / cmETH); wstETH does not have a comparable role and adoption has remained marginal |
| Swell | Chain is being sunset |
| Zircuit | wstETH TVL has significantly declined on the chain; no major wstETH integrations/venues are planned |
| Soneium | Low TVL; No meaningful DeFi venues for wstETH have emerged on the network since launch |
| Polygon PoS | The network’s direction has shifted toward stablecoin payments and RWAs; wstETH-related activity has dwindled since the original integration |
| Lisk | Lisk’s focus on emerging markets and start-up incubation which offers limited compatibility with a DeFi ecosystem for wstETH; bridged TVL has remained low since launch |
Authorize NEC to Revoke Recognized Canonical Status of (w)stETH Bridge Endpoints
In 2024, LDO token holders, via Snapshot voting, voted to create the Network Expansion Committee (NEC), established to streamline the process for recognizing (w)stETH bridge endpoints across new networks while preserving transparency, security reviews, and DAO oversight. Since then, the NEC has helped shift network expansion from repeated DAO-level votes to a more operational committee process, with unanimous NEC decision-making and transparent public forum announcements.
As the multichain footprint evolves, this proposal aims to extend the same logic to revocations and authorize the NEC to revoke the recognized canonical status of (w)stETH bridge endpoints on behalf of the Lido DAO. If continued canonical recognition of bridging endpoints no longer reflects the deployment state, having a streamlined, transparent process to de-recognize the relevant bridge endpoints under DAO oversight will contribute to overall operational efficiency.
Future NEC revocation decisions should follow the existing NEC guardrails: unanimous committee support and a public forum announcement explaining the decision, including relevant context such as usage, ecosystem conditions, technical considerations, maintenance status, risk factors, or other rationale considered by the committee, and next steps, such as Lido Multichain hub, Lido Docs, and Lido Help updates.
If a network whose bridge endpoints have had their canonical status revoked later seeks renewed canonical recognition, its re-onboarding should follow the NEC’s endorsement principles and the guardrails in place at the time of re-endorsement. A detailed explanation covering the cause of the prior revocation, the current state of the deployment, and any implications for users, liquidity, integrations, and migration paths shall be provided.
Disclaimer
Revocation of canonical recognition means that the Lido DAO no longer endorses the relevant (w)stETH bridge endpoints and/or token denominations as canonical. It does not necessarily imply that the bridge, token contract, or any third-party integrations are technically disabled or deprecated at the smart-contract level.
Next Steps
Following publication of this proposal, the community is invited to engage in open discussion and review. The proposal is planned to proceed to a DAO-wide Snapshot vote in the June voting cycle, following consideration of feedback received during the review period.