Security-Council threshold reduction (RT)
EigenLayer's assessment for RD-F-182 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Signal is directly applicable. EigenLayer's Pauser Multisig (0x5050389572f2d220ad927CcbeA0D406831012390) is already at 1-of-7 threshold (data cache) or 1-of-8 (Eigen Foundation docs — discrepancy to resolve). The Pauser Multisig's existing 1-of-N configuration means any single signer can pause the entire protocol — this is the structural pre-condition that makes any FURTHER threshold reduction on other multisigs highly consequential. The zero-delay timelock (0xC06Fd4F821eaC1fF1ae8067b36342899b57BAa2d) represents a potential bypass path for the timelock removal sub-pattern of F182. No threshold reduction events or new-signer additions observed in the 14-day lookback window as of 2026-04-28. The Drift Protocol precedent (3/5 to 2/5 SC threshold reduction, 6 days before $285M DPRK exploit) is directly analogous to what F182 would monitor on EigenLayer's multisigs. Score yellow because: (1) structural pre-conditions (1-of-N Pauser, zero-delay timelock) are elevated; (2) no event-trigger ob
Sources #
- Internal03-taxonomy.md v1.1 batch-24 — RD-F-182 definitionTaxonomy batch-24 RD-F-182 definition: Drift Protocol Apr 2026: 3/5 to 2/5 SC change + timelock removal, 6 days before $285M DPRK exploit — directly analogous precedentretrieved 2026-04-28
- Eigen Foundation Technical ArchitectureEigen Foundation docs: Pauser Multisig described as 1-of-8 multisig that can also pause EigenLayer functionality in emergency situations — threshold discrepancy with data cache (1-of-7 vs 1-of-8)retrieved 2026-04-28
- EigenLayer protocol profile §6Profile §6: zero-delay timelock 0xC06Fd4F821eaC1fF1ae8067b36342899b57BAa2d with minDelay 0 — potential F182 timelock removal sub-pattern monitoring targetretrieved 2026-04-28
- EigenLayer data cache — safe_multisigs pauser_multisigpauser_multisig: address 0x5050389572f2d220ad927CcbeA0D406831012390, threshold: 1, owner_count: 7 — any single signer can pause entire protocolretrieved 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 →