Security-Council threshold reduction (RT)
Lido's assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
GateSeal Committee threshold: 3-of-6 (confirmed from data-cache Safe API). EmergencyProtectedTimelock minimum delay: 259,200 seconds (3 days, per profile §6). No threshold reduction events or timelock removal events detected as of 2026-04-28. Dual Governance emergency committees (Tiebreaker Core, Reseal Committee) intact. The Drift Protocol reference case (3/5 → 2/5 SC change + timelock removal, 6 days before $285M DPRK exploit) makes this signal highest-priority to wire for Lido. Parameters to monitor: GateSeal Committee threshold change from 3-of-6 to lower; EmergencyProtectedTimelock MIN_EXECUTION_DELAY reduction below 3 days; new signer additions within ≤14 days of either.
Sources #
- URL0xCE0425301C85c5Ea2A0873A2dEe44d78E02D2316https://etherscan.io/address/0xCE0425301C85c5Ea2A0873A2dEe44d78E02D2316retrieved 2026-04-28
- 0x8772E3a2D86B9347A2688f9bc1808A6d8917760Chttps://etherscan.io/address/0x8772E3a2D86B9347A2688f9bc1808A6d8917760Cretrieved 2026-04-28
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →