Security-Council threshold reduction (RT)
Multipli'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 signal (batch-24, Cat 6B). T-09 v1.1 candidate signal. Trigger requires a Security Council multisig executing a threshold reduction (e.g. 3/5 → 2/5) or timelock removal within ≤14 days of prior signer addition. Multipli has no Security Council or Safe multisig published as of 2026-05-17. Data cache safe_multisigs=[]. Corporate / no-DAO pre-TGE admin via RolesAuthority EOA. The Drift-class trigger surface is absent. Post-TGE with potential Security Council introduction, this factor becomes applicable.
Sources #
- InternalMultipli data cache — no Safe multisig.research/protocols/multipli/00-data-cache.json §sources.safe_multisigs=[] — no Safe multisig foundretrieved 2026-05-17
- Multipli profile §6 — governance topology.research/protocols/multipli/00-profile.md §6 — Corporate / no-DAO, pre-TGE, no Security Council publishedretrieved 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 →