Security-Council threshold reduction (RT)
Midas's assessment for RD-F-182 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Security-Council threshold-reduction RT signal (batch-24, v1.1 candidate). Applicable in principle: Midas has an admin Safe controlling upgrade and admin operations. A threshold reduction on that Safe within 14 days of a timelock removal or new-signer addition would be the Drift-Protocol-class DPRK-precursor pattern. Architectural reason for gray: the admin Safe address is not publicly disclosed and not registered in the pipeline config (safe_addresses: [] in data cache). Without the Safe contract address, governance contract event subscription (ChangedThreshold, RemovedOwner, AddedOwner events) is impossible. No recent governance-weakening events identified in public data. Signal is applicable to this protocol class; the specific pipeline gap is that the admin Safe address must first be traced via MidasAccessControl RoleGranted events (governance-admin-analyst task) before this signal can be wired.
Sources #
- InternalData cache — undisclosed admin Safe (event subscription blocked)00-data-cache.json: safe_addresses=[], safe_multisigs=[], governance.type=unknown — admin Safe address not in pipeline config; event subscription impossible without contract addressretrieved 2026-05-16
- Profile §6 — undisclosed admin Safe gap00-profile.md §6: admin Safe not publicly disclosed; governance-admin-analyst instructed to trace via MidasAccessControl RoleGranted events on Etherscanretrieved 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 →