Security-Council threshold reduction (RT)
Babylon Protocol'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 #
Babylon has no Gnosis Safe / Security Council multisig (data cache safe_multisigs: []). No EVM ChangedThreshold/RemovedOwner/AddedOwner events applicable. The closest analog (Covenant Committee 6-of-9) is an off-chain signing quorum, not an EVM Safe contract — threshold reduction events cannot be detected via EVM event subscriptions. Cosmos SDK x/gov upgrades do not have a Security Council pattern. Structurally inapplicable.
Sources #
- Curator note00-data-cache.json — safe_multisigs: []Data cache safe_multisigs: []. No EVM Security Council multisig contract registered.retrieved 2026-05-04
- Babylon Governance Documentation — No EVM Admin ControlsBabylon profile §6: 'No Ethereum-style admin controls. There is no proxy admin address, no Gnosis Safe, no OpenZeppelin TimelockController.'retrieved 2026-05-04
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 →