Renew GateSeal for the Withdrawal Queue and Validator Exit Bus Oracle

Proposals
21

Vote #184 has concluded and was enacted!

294 participants cast their votes (either directly or via delegation).
Huge thanks to everyone who voted! :heart:

Here are the results:
“Yes” — 50107878.2 (5.01%)
“No” — 36.3 (0.01%)

3 Likes
22

Recent GateSeal Updates

Following recent releases, the previously approved GateSeal configuration has been updated and extended.

Triggerable Withdrawals (Vote #192)

The original GateSeal covering the Withdrawal Queue and Validator Exit Bus Oracle was replaced with two separate GateSeals:

Validator Exit Bus (VEB) and Triggerable Withdrawals Gateway (TWG) GateSeal 0xA6BC802fAa064414AA62117B4a53D27fFfF741F1

Withdrawal Queue GateSeal 0x8A854C4E750CDf24f138f34A9061b2f556066912

Community Staking Module V2 (Vote #192)

The original CSM GateSeal was replaced with the new instance:

CSM GateSeal 0xE1686C2E90eb41a48356c1cC7FaA17629af3ADB3

Lido V3 (Vote #194)

With the Lido V3 release, a new dedicated GateSeal was deployed for pausing VaultHub and PredepositGuarantee:

VaultHub and PredepositGuarantee (PDG) GateSeal 0x881dAd714679A6FeaA636446A0499101375A365c

Next Steps

All currently active GateSeals remain in effect until their respective expiration dates, with the first expirations starting in September 2026. Ahead of expiration, Lido DAO will either be proposed to prolong the current GateSeal configuration or migrate to GateSeal V2, depending on its readiness.

A complete and up-to-date list of active GateSeals and expiration dates is available in the Lido Docs.

1 Like