As a part of the implementation of withdrawls and unstaking for users of stETH, it seems that the Lido DAO will need to come up with a policy on what the expectations and responsibilities of Node Operators who participate in the protocol by operating validators are.
Together with some other Lido contributors, we have put together a draft attempt at such a policy, to be used as a driver for discussion by the community.
I suggest that we take the next two weeks to discuss and iterate on the above and attempt to have a vote-ready document within the first week of March. It would also make sense to have a deep-dive session to go over how the policy would interact with the proposed updates to the oracle design and the withdrawals flow, so we will try to put something together. Aiming for first week of March should also provide Lido contributors and Node Operators enough time to test the implementation of relevant process/mechanisms when withdrawals are enabled on the Goerli testnet.
Other topics / resources relevant to this discussion:
There will be an open community session to discuss the draft on Wed Feb 22, 5PM UTC. Since posting a public zoom link isn’t ideal, if anyone is interested in joining please respond here, or ping someone from the NOM contributors in the Lido discord and the link will be shared.
Just a reminder that there’s an open deep dive session today at 5PM UTC to go over the proposed policy and go in-depth on the tooling modules that were presented yesterday by the tooling team during the community call (relevant segment is here: Node Operator Community Call #4 - YouTube)
If you wish to join please contact a lido contributor and the zoom link will be provided!
Some minor edits for flow and grammar have been made to the proposed policy and two sections have been added. I propose that if by next week there’s no more discussion on the topic, we move to a snapshot vote.
The newly added sections:
B.3.V Out of Order Exits and NO Business Continuity
Out of Order Exits
Out of Order exits refers to exits that are made by a Node Operator when a validator exit request has not been made for a (set of) validator(s) by the Lido protocol. In the case of processing such an exit, the Node Operator must notify the DAO via the Lido forums (https://research.lido.fi) that such an exit has been processed, how many and which validators have been exited, and the reason for the exit.
Business Continuity and Other Considerations
If at any time a Node Operator is unable to continue to participate in the Lido on Ethereum protocol (e.g. has become insolvent), it must notify the DAO via the Lido forums (https://research.lido.fi) of the circumstances and signal its intent to exit all of the validators that it operates as a part of the protocol. If the DAO does not otherwise instruct the Node Operator via a ratified vote within 8 days, it must proceed with triggering the exit of all of the validators.
There will be two open sessions to go over the current draft before it’s sent to snapshot if the community wants to join. The sessions will be over video conferencing, but the link will be shared privately to any interested DAO community member to avoid scammers/phishers joining. If you wish to join, just DM any NOM workstream member.
The Policy has had minor updates made in order to bring terminology related to the v2 oracles in line with the actual wording (“Ejector Oracle” → “Exit Bus Oracle”) and from a grammar and clarity perspective. The detailed changes can be seen in hackmd by clicking the “settings” menu of the note (dots on the top right) and navigating to “Versions and GitHub sync”.
The draft for the proposal has also been published to github to facilitate version comparison for future changes.