# Withdrawals: Automating Lido Validator Exits **URL:** \ **Category:** Proposals\ **Created:** [November 21, 2022, 1:11pm UTC](https://research.lido.fi/t/withdrawals-automating-lido-validator-exits/3272 "2022-11-21T13:11:10Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![kolyasapphire](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kolyasapphire/32/323_2.png) [@kolyasapphire](https://research.lido.fi/u/kolyasapphire)\ **Post date:** [November 24, 2022, 4:57pm UTC](https://research.lido.fi/t/withdrawals-automating-lido-validator-exits/3272/3 "2022-11-24T16:57:32Z")
> If this happens, I’d guess the LIDO protocol could (and likely should) initiate exits directly, rather than relying on node operators? On one hand, this would make Node Operator operations easier as there would be less services to run and less manual tasks, but on the other, Lido operational costs could be a problem as a contract function needs to be called for every exit on the execution layer (by the [0x03 WC spec](https://ethresear.ch/t/0x03-withdrawal-credentials-simple-eth1-triggerable-withdrawals/10021) or the [GMB spec](https://ethresear.ch/t/withdrawal-credentials-exits-based-on-a-generalized-message-bus/12516)). So, we’ll have re-evaluate our options if/when they are implemented. > Does anyone have insights with regards to an implementation timeline? My basic understanding (from before the Merge) was that this feature would be developed/released together with withdrawals, but I might be mistaken. Very unlikely, probably at least the fork after withdrawals. --- _[View the full topic](https://research.lido.fi/t/withdrawals-automating-lido-validator-exits/3272)._