One of the parts of Lido V2 is GateSeal: a one-time contract that could be triggered to pause one or more contracts for a predetermined amount of time. Lido on Ethereum protocol V2 upgrade plan contains using a single GateSeal for two contracts that affect withdrawals:
Withdrawal queue (users’ side of withdrawals).
Validator exit bus (Node Operators’ side of withdrawals).
GateSeal can be 1) triggered only once (no matter what contracts are getting paused); 2) can’t be triggered later than the “expiration date” — 1 May 2024; 3) sets pause only for 6 days, after which the contracts would be unpaused automatically if no further action by the Lido DAO is taken. To be able to trigger pause, GateSeal contract must be granted the necessary permissions first.
If Lido DAO would decide to continue using the GateSeal mechanics after 1 May 2024 — the new GateSeal deployment would be required, along with granting necessary permissions via on-chain DAO vote.
The proposal is the following GateSeal committee structure which is implemented by the 3/6 Gnosis Safe multisig contract at (0x8772E3a2D86B9347A2688f9bc1808A6d8917760C) having three Lido DAO contributors and three third-party participants as signers:
Hey there, with the consent of the Lido DAO, I’ll be honored to replace @skozin in the Lido DAO GateSeal Committee with the address 0x59f8d74fe49d5ebeac069e3baf07eb4b614bd5a7.