Security-Council threshold reduction (RT)
Concrete'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 #
Security-Council threshold reduction event (batch-24, Cat 6B): not applicable. Concrete has no Security Council multisig structure. Data cache confirms safe_multisigs=[], governance fields all null. No Gnosis Safe or equivalent SC multisig has been identified. The signal fires on bridge/protocol Security Council threshold reductions (e.g., 3/5 → 2/5 per Drift Protocol pattern). This governance structure does not exist for Concrete — governance is EOA-admin-only. If governance-admin-analyst discovers a previously-unidentified Safe multisig (U18 resolution), this factor should be re-evaluated.
Sources #
- InternalRD-F-182 batch-24 definition — SC structure required03-taxonomy.md §v1.1 batch-24 additions RD-F-182 — Drift Protocol SC threshold reduction pattern; requires SC multisig structureretrieved 2026-05-17
- Concrete data cache — no Safe multisig identifieddata cache §sources.safe_multisigs=[] — no Gnosis Safe found by pipeline; no Security Council structureretrieved 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 →