Security-Council threshold reduction (RT)
BENQI'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 (v1.1 batch-24, Cat 6B): BENQI has no formal Security Council structure in the Arbitrum/Drift sense, but the team-multisig serves an analogous function. Any multisig threshold reduction (e.g., from N-of-M to lower threshold) would be the relevant trigger. Admin multisig threshold is not confirmed from public data — governance-admin-analyst tracing Snowtrace. No public report of BENQI multisig threshold reduction. No timelock confirmed on Comptroller (pendingAdmin() check pending). veQI is not a Security Council. Signal is v1.1 candidate (not yet in production shortlist). Pipeline not implemented; threshold data not yet confirmed.
Sources #
- URLBENQI Comptroller — Snowtrace (admin() address to be traced by governance-admin-analyst)https://snowtrace.io/address/0x486Af39519B4Dc9a7fCcd318217352830E8AD9b4retrieved 2026-05-16
- Taxonomy F182 definition — batch-24risk-dashboard/research/outputs/03-taxonomy.md §v1.1 batch-24 additions — RD-F-182 definition: SC threshold reduction, timelock removal, new signer within ≤14 daysretrieved 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 →