# Empowering Lido Ecosystem Foundation to Lead Bridge-Related Partnerships

**URL:** <https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794>\
**Category:** Proposals\
**Created:** [October 8, 2025, 11:56am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794 "2025-10-08T11:56:30Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![skelneko](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/skelneko/32/5508_2.png) [@skelneko](https://research.lido.fi/u/skelneko)\
**Post date:** [October 8, 2025, 11:56am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/1 "2025-10-08T11:56:31Z")

</div>

## TL;DR

This proposal seeks DAO authorization for the Lido Ecosystem Foundation (“Lido Ecosystem”) to lead all bridge-related strategic partnerships and negotiations involving stETH and wstETH, in order to unlock opportunities to improve competitiveness and resilience of the Lido protocol in an evolving market landscape.

### Key Highlights

- Lido Ecosystem will be empowered to negotiate and execute strategic agreements with bridge counterparties on behalf of the DAO.

- Being a part of the Lido Ecosystem, the [Network Expansion Committee (NEC)](https://snapshot.org/#/lido-snapshot.eth/proposal/0x7cdf1af7cfeb472ae202c45fb6d7e952bb34bfcbc82113549986b2bc2d5f54c5) will serve as a subject matter expert, providing expertise and best practices for bridge counterparties and the DAO.

- NEC membership composition will be rotated to ensure better alignment with its objectives.

- A Bridging Security Committee (”BSC”) will be established under Lido Labs Foundation (“Lido Labs”) and nominated to pause and block partnerships if they pose serious unresolved risks and escalate such cases to the DAO for review.

- With BSC safeguarding the process, the previously approved flow for canonical bridge recognition changes: a 5-day DAO objection period will no longer be provided upon publication of the decision by NEC.

- Lido DAO retains the ultimate authority to cancel, amend, or override any strategic agreement executed by Lido Ecosystem.

## Background

[Following the Lido Ecosystem establishment](https://research.lido.fi/t/establishment-of-lido-ecosystem-borg-foundation-as-a-lido-dao-adjacent-foundation/9345), NEC activities have been placed under its oversight, with NEC continuing support the timely execution of network expansion efforts and prevent missed market opportunities. Since November 2024, the NEC has successfully guided the expansion of wstETH to 4 new networks and induced 10k wstETH bridged across [Soneium](https://research.lido.fi/t/nec-2-recognition-of-steth-and-wsteth-bridge-endpoints-on-soneium-as-canonical/9427), [Unichain](https://research.lido.fi/t/nec-3-recognition-of-steth-and-wsteth-bridge-endpoints-on-unichain-as-canonical/9584), [Lisk](https://research.lido.fi/t/nec-4-recognition-of-wsteth-bridge-endpoints-on-lisk-as-canonical/9637), and [Swellchain](https://research.lido.fi/t/nec-5-recognition-of-wsteth-bridge-endpoints-on-swellchain-as-canonical/10026) within one year (with an all-time high of 38k ETH bridged on April 25, 2025; [Dune](https://dune.com/queries/5873915/9497755/)). These results highlight the ability to capture opportunities through NEC under the current Lido Ecosystem oversight.

However, bridges have become more than technical infrastructure. Conversations with partners over the past year show that bridge setups carry consequences beyond execution: they define how tokens enter ecosystems, influence partner confidence, and concentrate both opportunities and risks, and thus for the accelerated adoption and success if wstETH, a more nimble setup should be considered. Opportunities have been identified to create better conditions for wstETH users and increase the competitiveness of the Lido protocol through tighter integration of bridging infrastructure with (w)stETH. This can be enabled by extending the scope of authority of Lido Ecosystem to negotiate and support the execution of bridge-related agreements.

Lido Ecosystem was founded to [develop and manage relationships with institutions, projects and DAOs, and to promote the expansion and use of (w)stETH across blockchains and other projects](https://research.lido.fi/t/establishment-of-lido-ecosystem-borg-foundation-as-a-lido-dao-adjacent-foundation/9345). Expanding its scope to cover bridge partnerships would ensure these goals are fully realized, while NEC continues to focus on operational excellence.

## Proposal

This initiative proposes that the DAO empowers Lido Ecosystem to lead all bridge-related strategic partnerships and negotiations involving (w)stETH, while maintaining institutional grade confidence in wstETH bridging:

### Roles & Responsibilities

- Lido Ecosystem

- NEC

- Bridging Security Committee (within the Lido Labs Foundation)

### Bridging Security Committee

With the Lido Ecosystem’s extended role in decision-making, a Bridging Security Committee (BSC) is proposed to be established to act as a counterbalance and a safeguard on behalf of the DAO, ensuring that bridge-related agreements protect the long-term integrity of the protocol. The committee is proposed to be established within the Lido Labs Foundation and operate independently from the Lido Ecosystem.

With the trust and expertise established, the following contributors are nominated to be the first members of the BSC:

- [@TheDZhon](https://research.lido.fi/u/thedzhon/summary), [@tamtamchik](https://research.lido.fi/u/tamtamchik/summary), [@psirex](https://research.lido.fi/u/psirex/summary) (Tech)

- [@zuzu\_eeka](https://research.lido.fi/u/zuzu_eeka/summary) (DAO Ops)

### Network Expansion Process Adjustment

- Lido Ecosystem will lead the negotiation, agreement, and execution, with NEC providing technical, operational, and advisory.

- BSC is required to provide explicit approval before any agreement to proceed. Lido Ecosystem is advised to keep BSC updated on any risk assessment info throughout the development, including but not limited to the full extent of the negotiation process and communications with the relevant counterparty(ies), including any risk assessments or analysis conducted on the partnership. Following the decision to proceed with execution, the signing of any agreement will be deferred for a period of five business days to allow BSC to review and evaluate the agreement.

- BSC may exercise its rights to pause or stop the negotiation if a critical risk is identified. When pausing an ongoing negotiation:

- If critical risks remain unresolved while the agreement is being advanced, BSC may escalate the matter to the DAO to safeguard Lido DAO and the protocol. In this case, the DAO should vote on whether to stop the agreement. If the DAO supports a stop, the agreement is terminated, and any related technical deployment will be rolled back.

- Once the BSC grants approval, the NEC will publish an announcement on the Research Forum on canonical bridge recognition. The original 5-day DAO objection period will no longer apply. However, should the DAO disagree with the NEC’s decision, it has the authority to initiate a Snapshot vote to dispute it.

These safeguards are emergency powers: while necessary to protect Lido DAO, their use carries trade-offs — including reputational impact, disclosure of confidential information, and strained counterpart relationships.

### NEC Committee Rotation

NEC membership composition will be rotated to ensure better alignment with its objectives:

- [@kovalgek](https://research.lido.fi/u/kovalgek) → [@arwer13](https://research.lido.fi/u/arwer13/summary) (Tech)

- [@EvgeniyEmelyanov](https://research.lido.fi/u/evgeniyemelyanov) → [@Mariya\_Muzyko](https://research.lido.fi/u/mariya_muzyko/summary) (Product)

- [@DeFiYaco](https://research.lido.fi/u/defiyaco) → [@vtrush](https://research.lido.fi/u/vtrush/summary) (ProRel → QA)

- [@nikita.p](https://research.lido.fi/u/nikita.p) will remain without a change (DAO Ops)

### Next Steps

- DAO discussion period to gather feedback.

- Have a Snapshot vote to formally empower Lido Ecosystem for bridge-related partnerships.

- Upon approval:

---

<div class="post-metadata">

**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\
**Post date:** [October 9, 2025, 7:08am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/2 "2025-10-09T07:08:04Z")

</div>

In general, makes sense to me. Are there any added risks due to this change you foresee and can share? How are they mitigated?

---

<div class="post-metadata">

**Author:** ![skelneko](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/skelneko/32/5508_2.png) [@skelneko](https://research.lido.fi/u/skelneko)\
**Post date:** [October 10, 2025, 12:06pm UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/3 "2025-10-10T12:06:51Z")

</div>

Sure, let me elaborate.

The following key risks have been identified for this proposal, along with the safeguards currently in place to mitigate them:

- Security & Technical Risks

- Governance Centralization Risks

- Legal & Counterparty Risks

- Operational Risks

If readers identify additional risks not covered here, you are encouraged to share your thoughts and/or concerns here.

---

<div class="post-metadata">

**Author:** ![EvgeniyEmelyanov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/evgeniyemelyanov/32/3756_2.png) [@EvgeniyEmelyanov](https://research.lido.fi/u/EvgeniyEmelyanov)\
**Post date:** [October 13, 2025, 7:03am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/4 "2025-10-13T07:03:02Z")

</div>

As an NEC Committee member, I support this proposal and my rotation, as I’m fully focused on the stVaults launch

---

<div class="post-metadata">

**Author:** ![kovalgek](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kovalgek/32/4197_2.png) [@kovalgek](https://research.lido.fi/u/kovalgek)\
**Post date:** [October 13, 2025, 7:31am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/5 "2025-10-13T07:31:47Z")

</div>

As an NEC Committee member, I’m also in favor of this proposal and my rotation.

---

<div class="post-metadata">

**Author:** ![DeFiYaco](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/defiyaco/32/2084_2.png) [@DeFiYaco](https://research.lido.fi/u/DeFiYaco)\
**Post date:** [October 13, 2025, 9:13am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/6 "2025-10-13T09:13:55Z")

</div>

Supportive of this proposal as a whole and happy to get rotated out from the NEC.

---

<div class="post-metadata">

**Author:** ![Mariya\_Muzyko](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/mariya_muzyko/32/2110_2.png) [@Mariya\_Muzyko](https://research.lido.fi/u/Mariya_Muzyko)\
**Post date:** [October 13, 2025, 9:20am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/7 "2025-10-13T09:20:37Z")

</div>

Supportive this proposal and I’d be happy to be included as the NEC member from Product side.

---

<div class="post-metadata">

**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:** [October 13, 2025, 9:39am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/8 "2025-10-13T09:39:26Z")

</div>

Will be honored to join the Bridging Security Committee contingent the course of action approval by the Lido DAO.

---

<div class="post-metadata">

**Author:** ![psirex](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/psirex/32/6344_2.png) [@psirex](https://research.lido.fi/u/psirex)\
**Post date:** [October 13, 2025, 9:57am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/9 "2025-10-13T09:57:30Z")

</div>

I’m in favor of this proposal and would be honored to take part in the Bridging Security Committee once it’s approved by the Lido DAO.

---

<div class="post-metadata">

**Author:** ![vtrush](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/vtrush/32/6257_2.png) [@vtrush](https://research.lido.fi/u/vtrush)\
**Post date:** [October 13, 2025, 10:01am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/10 "2025-10-13T10:01:07Z")

</div>

Guys, thank you for your work on this proposal! I support it and am ready to be included in the NEC from the QA department.

---

<div class="post-metadata">

**Author:** ![tamtamchik](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/tamtamchik/32/4064_2.png) [@tamtamchik](https://research.lido.fi/u/tamtamchik)\
**Post date:** [October 13, 2025, 10:08am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/11 "2025-10-13T10:08:06Z")

</div>

I support this proposal and would be honored to serve on the Bridging Security Committee pending approval from Lido DAO.

---

<div class="post-metadata">

**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:** [October 13, 2025, 12:03pm UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/12 "2025-10-13T12:03:56Z")

</div>

Hi! I support the proposal and ready to accept the tech part participation!

---

<div class="post-metadata">

**Author:** ![zuzu\_eeka](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/zuzu_eeka/32/1157_2.png) [@zuzu\_eeka](https://research.lido.fi/u/zuzu_eeka)\
**Post date:** [October 13, 2025, 1:49pm UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/13 "2025-10-13T13:49:27Z")

</div>

I’m fully supportive of this proposal and ready to take on the role within the Bridging Security Committee, helping uphold the DAO’s security standards

---

<div class="post-metadata">

**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:** [October 15, 2025, 4:21pm UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/14 "2025-10-15T16:21:42Z")

</div>

## Snapshot vote started

Please get your wallets ready to cast a vote ✅, the [Empowering Lido Ecosystem Foundation to Lead Bridge-Related Partnerships](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf842517c2ffba082efac87ec43365e86548adb38e24d1446d850c7d7b979c423) Snapshot has started! The Snapshots ends on Wed, 22 Oct 2025 16:00:00 GMT.

---

<div class="post-metadata">

**Author:** ![PGov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/pgov/32/4894_2.png) [@PGov](https://research.lido.fi/u/PGov)\
**Post date:** [October 16, 2025, 6:10am UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/15 "2025-10-16T06:10:09Z")

</div>

We are strongly in support of empowering the Lido Ecosystem Foundation to lead bridge-related partnerships, as it streamlines decision-making while preserving DAO sovereignty. The current NEC model has demonstrated its capacity (e.g. expanding wstETH to multiple networks and bridging tens of thousands of ETH in the past year), but to compete in evolving cross-chain markets, Lido needs a more agile negotiation posture. The proposed structure, is a pretty good balance between speed and oversight.

The concerns re governance centralization, legal exposure, and removal of the 5-day objection window are valid; here’s our thoughts. The proposal preserves ultimate DAO authority (override, cancel, amend), embedding reversibility clauses in agreements, and requiring legal and risk review before execution. Our take is that these safeguards go a long way to protect against abuses. Moreover, NEC members themselves have signaled support for rotation and lighter roles.

Given the speed demands and competition in bridging infrastructure, we are very much in support. Granting this mandate helps reduce friction in executing partnerships, enables more responsive opportunity capture, and concentrates institutional negotiation strength in the team with the deepest relational footing.

---

<div class="post-metadata">

**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:** [October 22, 2025, 4:02pm UTC](https://research.lido.fi/t/empowering-lido-ecosystem-foundation-to-lead-bridge-related-partnerships/10794/16 "2025-10-22T16:02:48Z")

</div>

## Snapshot vote ended

The [Empowering Lido Ecosystem Foundation to Lead Bridge-Related Partnerships](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf842517c2ffba082efac87ec43365e86548adb38e24d1446d850c7d7b979c423) Snapshot has reached a quorum and completed successfully!  
The results are:  
**For** : 55.5M LDO  
**Against** : 86 LDO

✅ **Winning option: For**
