Security-Council threshold reduction (RT)
Kinetiq's assessment for RD-F-182 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Batch-24 signal: Security-Council threshold reduction event (RT signal). Applicable context: the 4-of-7 Gnosis Safe is Kinetiq's admin (ProxyAdmin transferred 2026-04-21 per governance-admin-analyst). The F182 dual-trigger (threshold reduction AND timelock removal within ≤14 days) cannot fully fire for Kinetiq because there is NO timelock anywhere in the protocol — the timelock-removal component of the Drift pattern has nothing to remove. The threshold-reduction-only sub-condition is monitorable, but since there is already no timelock, the risk captured by F182's combined trigger (Drift pattern = threshold reduction PLUS timelock removal) is partially inapplicable. The Safe has executed 77 transactions with the most recent on 2026-05-14 — all routine execTransactions with near-zero HYPE value. No threshold reduction event observed. The absence of a timelock is already captured as a static red in Cat 2 (F032/F033). Scoring not_applicable because the defining dual-trigger condition of F1
Sources #
- EtherscanKinetiq Admin Safe 4-of-7 — HyperEVMScanAdmin Safe 0x18A82c968b992D28D4D812920eB7b4305306f8F1 — 77 transactions, most recent 2026-05-14, all routine execTransactions; created by deployer 307 days ago per HyperEVMScanretrieved 2026-05-17
- Orchestrator-verified admin topologyVerified admin fact from orchestrator: 4-of-7 Gnosis Safe 0x18A82c96 is current ProxyAdmin (transferred 2026-04-21); no timelock anywhere in protocolretrieved 2026-05-17
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 →