GateSeal Renewal for 2025-2026
Hey everyone! I’m happy to share that Lido DAO has recently approved the Snapshot vote, which proposes to extend the on-chain voting duration from 3 days to 5 days in order to increase participation and improve security:
Tané and Lido DAO Ops contributors are proposing to extend on-chain voting duration for better participation and security:
Main phase: 48h → 72h;
Objection phase: 24h → 48h.
The GateSeal duration extension was also included in this snapshot vote: to maintain the security and efficiency of the GateSeal mechanics, the seal duration was proposed to be twice the governance reaction time plus one day. As a result, the new GateSeal duration was proposed to be 11 days.
There are currently two separate GateSeal contracts involved in the Lido protocol, serving as one-time panic buttons for critical contracts in case of an emergency:
- GateSeal can pause protocol contracts: Withdrawal Queue and Validators Exit Bus Oracle
- CSM GateSeal can pause CSM contracts: Core CS Module, CS Accounting and CS Fee Oracle
It is proposed to renew both GateSeals in the upcoming on-chain vote, along with an extension of the voting duration. The deployments of new instances for the GateSeal and CSM GateSeal contracts will use the same GateSeal Blueprint and GateSeal Factory referenced in the initial post, using the same set of parameters, except for the seal duration:
GateSeal
- The same list of
sealables- Withdrawal Queue (proxy): 0x889edC2eDab5f40e902b864aD4d7AdE8E412F9B1
- Validator Exit Bus Oracle (proxy): 0x0De4Ea0184c2ad0BacA7183356Aea5B8d5Bf5c6e
- The same 3/6 multisig 0x8772E3a2D86B9347A2688f9bc1808A6d8917760C
- The same activity duration of 1 year
- Seal duration of 11 days (950400 seconds) instead of the 6-day seal duration set for the previous GateSeal
CSM GateSeal
- The same list of
sealables- CSModule (proxy): 0xdA7dE2ECdDfccC6c3AF10108Db212ACBBf9EA83F
- CSAccounting (proxy): 0x4d72BFF1BeaC69925F8Bd12526a39BAAb069e5Da
- CSFeeOracle (proxy): 0x4D4074628678Bd302921c20573EEa1ed38DdF7FB
- The same 4/6 multisig 0xC52fC3081123073078698F1EAc2f1Dc7Bd71880f
- The same activity duration of 1 year
- Seal duration of 11 days (950400 seconds) instead of the 6-day seal duration set for the previous CSM GateSeal
Deployment and Verification
The new instances of the GateSeal and CSM GateSeal contracts will be deployed and announced under the post. The deployment verification by a third-party audit team will be posted before the on-chain voting as well.
GateSeal Multisigs
There is a Lido DAO Ops Multisigs Policy (revised) proposal that aims to optimize multisig governance for scalability, enhance security measures, and ensure a clear framework that aligns with the fast-moving nature of Web3 governance. Be sure to check it out!
Next steps
- New GateSeal and CSM GateSeal contracts will be deployed
- Deployment verification will be performed for both GateSeal contracts
- On-chain vote will follow