Security-Council threshold reduction (RT)
Maple Finance'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 #
Maple does not operate a Security Council multisig governance model. Its governance is Snapshot → daoMultisig → GovernorTimelock. RD-F-182's SC threshold-reduction signal has no direct analog here.
Detail #
RD-F-182 fires when a Security Council multisig executes threshold reduction (e.g., 3/5 → 2/5) or timelock removal — the Drift Protocol Apr 2026 pattern. Maple's governance uses a Snapshot vote ratified by a DAO-level multisig feeding a GovernorTimelock with 1-day min delay. There is no separate Security Council with its own threshold management. The daoMultisig (Safe, 0xd6d4Bcde...) threshold is unknown (safe_api_gap flag), but it is the primary governance actor, not a supplementary Security Council layer. Signal not applicable per architecture.
Sources #
- Etherscanhttps://etherscan.io/address/0x2eFFf88747EB5a3FF00d4d8d0f0800E306C0426bretrieved 2026-04-27
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 →