# Triggerable Withdrawals Framework in the Lido Protocol **URL:** \ **Category:** Proposals\ **Created:** [July 4, 2025, 11:40am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299 "2025-07-04T11:40:13Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Raman\_Siamionau](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/raman_siamionau/32/7018_2.png) [@Raman\_Siamionau](https://research.lido.fi/u/Raman_Siamionau)\ **Post date:** [July 4, 2025, 11:40am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/1 "2025-07-04T11:40:13Z")
### **TL;DR** This proposal outlines implementing the Triggerable Withdrawal framework within the Lido protocol to enable permissionless, secure, and verifiable validator exits via the Execution Layer - enhancing the protocol’s fault tolerance, reducing trust assumptions, and paving the way for truly permissionless staking in Lido. ### **Abstract** The Triggerable Withdrawals (TW) mechanism is a critical extension of Lido’s architecture, enabling the initiation of validator exits without requiring the involvement of a Node Operator. TW is based on [EIP-7002](https://eips.ethereum.org/EIPS/eip-7002), which addresses a key issue in delegated staking. Previously, stakers had to rely on the goodwill of Node Operators - either to pre-sign an exit message or to agree to process it in the future. This limitation is now removed: any party with access to a validator’s withdrawal credentials can initiate its exit directly via the Execution Layer. ### **Motivation** For the **Lido protocol** , TW support means a substantial reduction in trust assumptions toward Node Operators and Oracles. It unlocks the following capabilities: - **Permissionless Staking Modules** , such as CSM, where ETH cannot be “held hostage” even if the operator misbehaves or significantly underperforms; - A mechanism for **emergency validator exits** , in case of key loss or a potential compromise event; - **Direct DAO interaction** , enabling the Lido DAO to request validator exits independently of Oracles. - Enables permissionless exits for validators that have been requested to exit, preventing NOs from delaying withdrawal requests fulfillment. ### **References** [The Lido improvement proposal (LIP-30)](https://github.com/lidofinance/lido-improvement-proposals/blob/develop/LIPS/lip-30.md) [Technical details](https://hackmd.io/Bebrx9iHTQuz71IqYmbICg) * * * We kindly ask everyone to share their opinions and suggestions for improvement in this thread. If no objections are raised, the next step will be the Snapshot vote (presumably, on July 14). Thanks! ---
**Author:** ![dgusakov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dgusakov/32/1238_2.png) [@dgusakov](https://research.lido.fi/u/dgusakov)\ **Post date:** [July 7, 2025, 7:36am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/2 "2025-07-07T07:36:49Z")
Thanks for the proposal @Raman_Siamionau! I find it useful and well thought out. The only suggestion from my side is to have a detailed breakdown of the use cases. While they are listed with high-level descriptions, more detailed explanations might be useful for Lido Node Operators. CSM Node Operators can refer to the corresponding parts of the CSM v2 spec: [📝 Community Staking Module v2. Spec - HackMD](https://hackmd.io/@lido/csm-v2-spec#Validator-ejection-due-to-strikes). Still, having it all collected in one place seems useful to me. ---
**Author:** ![cp0x](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/cp0x/32/4886_2.png) [@cp0x](https://research.lido.fi/u/cp0x)\ **Post date:** [July 8, 2025, 5:39pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/3 "2025-07-08T17:39:41Z")
I have a couple of questions just to clarify some moments: - Will this be a mandatory transition for all Node Operators? - Will everyone be required to upgrade in order to remain part of Lido? ---
**Author:** ![dgusakov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dgusakov/32/1238_2.png) [@dgusakov](https://research.lido.fi/u/dgusakov)\ **Post date:** [July 9, 2025, 9:09am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/4 "2025-07-09T09:09:40Z")
TW mechanism is proposed to be implemented on the Lido Protocol side. No actions are required from the Node Operators side. ---
**Author:** ![Raman\_Siamionau](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/raman_siamionau/32/7018_2.png) [@Raman\_Siamionau](https://research.lido.fi/u/Raman_Siamionau)\ **Post date:** [July 9, 2025, 11:49am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/5 "2025-07-09T11:49:20Z")
Thanks for feedback! Will prepare such document! ---
**Author:** ![Raman\_Siamionau](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/raman_siamionau/32/7018_2.png) [@Raman\_Siamionau](https://research.lido.fi/u/Raman_Siamionau)\ **Post date:** [July 9, 2025, 1:22pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/6 "2025-07-09T13:22:28Z")
Also, what to highlight that we’re introducing new Easy Track Factories for the sDVT committee and Node Operators in the Curated Module. These ET factories enable authorized entities to request validator exits via the Validator Exit Bus for specific validators. After initiating such exits, anyone can exit those validators using the TW framework on the EL. It provides a crucial recovery path in catastrophic scenarios - such as when a Node Operator loses access to a validator key. 📘 More details can be found in the LIP-30: [Easy Track Factories for VEB](https://github.com/lidofinance/lido-improvement-proposals/blob/develop/LIPS/lip-30.md#appendix-b---easy-track-factories-for-veb) ---
**Author:** ![Aleksandr\_V](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/aleksandr_v/32/4105_2.png) [@Aleksandr\_V](https://research.lido.fi/u/Aleksandr_V)\ **Post date:** [July 15, 2025, 1:01pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/7 "2025-07-15T13:01:57Z")
Thanks for the proposal @Raman_Siamionau! **Recommended TW limits for Lido** To make triggerable withdrawals safe and reliable, we suggest: - maxExitRequestsLimit: 11 200 validators (applies to both TW gateway and VEB modules) - exitsPerFrame: 1 validator - frameDuration: 48 seconds (resulting in (~1 800 validators/day)) This setup keeps TW permissionless and efficient, providing a sufficient capacity for **emergency validator exits** , while still limiting risks for any malicious attacks utilizing EIP-7002 if there is a protocol exploit For full analysis (threat models, APR effects, benchmarks, etc.), check the detailed research here: [TW module limits](https://hackmd.io/5wN10bGaSbyPwpzcVkdVVw?both) ---
**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:** [July 21, 2025, 11:26am UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/8 "2025-07-21T11:26:26Z")
## Snapshot vote started We’re starting the [Triggerable Withdrawals Framework in the Lido Protocol](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7d7f0e1a6d181310f8752af37e20515a9be258f30b211872f9acca99bc478851) Snapshot, active till Mon, 28 Jul 2025 16:00:00 GMT . Please don’t forget to cast your vote! ---
**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:** [July 28, 2025, 4:00pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/9 "2025-07-28T16:00:41Z")
## Snapshot vote ended Thank you all who participated in the [Triggerable Withdrawals Framework in the Lido Protocol](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7d7f0e1a6d181310f8752af37e20515a9be258f30b211872f9acca99bc478851) Snapshot, the proposal passed! 🙏 The results are: **For** : 52.3M LDO **Against** : 12 LDO ---
**Author:** ![Raman\_Siamionau](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/raman_siamionau/32/7018_2.png) [@Raman\_Siamionau](https://research.lido.fi/u/Raman_Siamionau)\ **Post date:** [September 23, 2025, 3:16pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/10 "2025-09-23T15:16:31Z")
Great news! We are going to start the vote for upgrading Lido protocol with Triggerable Withdrawals Framework. All proposed contract addresses can be found here: [Mainnet | Lido Docs](https://docs.lido.fi/deployed-contracts/) And, of course, we prepared step-by-step guide on how to verify the full vote: [TW + CSM vote steps with details - HackMD](https://hackmd.io/J1zMCasFQ0yc42YShwrDgQ) ---
**Author:** ![nikita.p](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/nikita.p/32/5751_2.png) [@nikita.p](https://research.lido.fi/u/nikita.p)\ **Post date:** [September 23, 2025, 3:59pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/11 "2025-09-23T15:59:34Z")
**The [Vote #192](https://vote.lido.fi/vote/192) has started!** Besides other voting items, it contains a Dual Governance proposal with a **Triggerable Withdrawals on-chain activation**. The vote will be open for your “For” or “Against” input until the end of the main phase: **Sep 26, 15:32 UTC.** For instructions on how to verify the vote items, please follow [this guide](https://enchanted-direction-844.notion.site/How-to-check-the-Lido-DAO-on-chain-vote-192-275bf633d0c98057a5a1cf1a50bd9ad2?source=copy_link). ---
**Author:** ![nikita.p](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/nikita.p/32/5751_2.png) [@nikita.p](https://research.lido.fi/u/nikita.p)\ **Post date:** [October 2, 2025, 4:48pm UTC](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299/12 "2025-10-02T16:48:41Z")
**The [Vote #192](https://vote.lido.fi/vote/192) was passed, and [Dual Governance Proposal #5](https://dg.lido.fi/proposals/5) was executed!** Triggerable Withdrawals Framework is finally live! Voting stats: **“No” — 1 (0.01%)** **“Yes” — 55,433,862 (5.54%)**