Security-Council threshold reduction (RT)
mETH Protocol'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 #
Security-Council threshold reduction event (batch-24, Cat 6B, T-09 v1.1 candidate). Applicable: yes — Security Council (MSecCouncilL1 at 0x4e59e778a0fb77fBb305637435C62FaeD9aED40f) is a 6-of-14 Safe multisig; Protocol Admin (MLSPEngL1 at 0x432ABcCb04DdD86Db9aA91FA3E03Fb566270c9ff) is a 3-of-8 Safe multisig. Signal fires on threshold reduction, timelock removal, or new-signer addition within 14 days. CRITICAL CALIBRATION NOTE: TimelockController minDelay=0 means the Drift comparator (6-day window between SC threshold reduction and exploit) does not apply — for mETH, any threshold reduction could be followed immediately by malicious operation. Current posture: Security Council threshold 6-of-14 (confirmed via Safe API data cache, retrieved 2026-05-16); Protocol Admin threshold 3-of-8 (confirmed). No threshold reduction events reported. Score green: no threshold change at assessment time. Monitoring this signal is especially high-priority given zero-delay timelock architecture.
Sources #
- EtherscanMSecCouncilL1 Security Council Safe — EtherscanSecurity Council Safe 0x4e59e778a0fb77fBb305637435C62FaeD9aED40f — Safe 1.3.0, deployed 2023-05-08, 75 total transactions, no threshold change events detectedretrieved 2026-05-16
- mETH Protocol data cache — Safe multisig configurations00-data-cache.json §safe_multisigs — MSecCouncilL1 0x4e59e778a0fb77fBb305637435C62FaeD9aED40f: threshold=6, owner_count=14, api_status=found; MLSPEngL1 0x432ABcCb04DdD86Db9aA91FA3E03Fb566270c9ff: threshold=3, owner_count=8, api_status=foundretrieved 2026-05-16
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 →