Security-Council threshold reduction (RT)
Ethena'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 #
Dev Multisig threshold confirmed at 5-of-11 via Safe API (data cache: threshold=5, owner_count=11, address 0x3B0AAf6e6fCd4a7cEEf8c92C32DFeA9E64dC1862). No threshold reduction event detected. The April 2026 DVN upgrade for the LayerZero bridge was a security *increase* (2 → 4 DVNs), not a threshold reduction. No on-chain Timelock contract is published (docs reference a 7-day conceptual time-lock but no contract address found), so timelock removal is not observable on-chain. Reserve Fund multisig is 4-of-10 (confirmed). Context: the Drift Protocol precedent (3/5 → 2/5 SC threshold + timelock removal 6 days before $285M DPRK exploit) anchors this signal — Ethena's 5-of-11 is a stronger quorum. No reduction detected.
Sources #
- URLEthena Dev Multisig 5-of-11 | EtherscanData cache safe_multisigs[0]: threshold=5, owner_count=11 for Dev Multisig 0x3B0AAf6e6fCd4a7cEEf8c92C32DFeA9E64dC1862retrieved 2026-04-28
- Ethena Bridge Restoration | WEEXEthena bridge DVN upgraded 2→4 (security increase, not threshold reduction)retrieved 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 →