Security-Council threshold reduction (RT)
GMX v2 (GMX Synthetics)'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 #
F182 batch-24 RT signal: Security-Council threshold reduction event. GMX admin Safe confirmed stable at 5-of-8 threshold (Safe API data cache, fetched 2026-05-05T09:51:39Z at 0x8D1d2e24eC641eDC6a1ebe0F3aE7af0EBC573e0D). All five timelocks confirmed at 86400s minDelay (1-day) with no reduction documented. Security Committee Season 4 (May 1 — Oct 31, 2026) was constituted via governance vote, not via unilateral threshold reduction. No signer addition within <=14 days of a threshold change. Drift Protocol analog: Drift Apr 2026 had 3/5 -> 2/5 + timelock removal 6 days before $285M DPRK exploit. GMX Safe is 5/8 with no recent change — does not match precursor pattern. Signal would not fire.
Sources #
- GitHubhttps://raw.githubusercontent.com/gmx-io/gmx-synthetics/main/deployments/arbitrum/Timelock.jsonretrieved 2026-05-05
- https://gov.gmx.io/t/gmx-security-committee-season-4/5051retrieved 2026-05-05
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 →