Security-Council threshold reduction (RT)
Balancer (v2 + v3)'s assessment for RD-F-182 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Security-Council threshold reduction event (RT signal) [batch-24, T-09 v1.1 candidate] | Applicable: Yes — directly applicable to Balancer's multisig governance structure | Threshold: Multisig executes threshold reduction (e.g., 6-of-11 → 4-of-11) OR timelock removal OR new-signer addition within ≤14 days of either of the above. Current DAO Multisig threshold: 6-of-11. BIP-907 (Jan 2026) replaced 4 signers but maintained 6-of-11 threshold — signer rotation, not threshold reduction; governance-sanctioned. Historical threshold-reduction event: the TimelockAuthorizer (0x9E3cD0606Db55ac68845bB60121847823712ae05) was deprecated and removed from the active Authorizer chain in a prior governance cycle — this represents a timelock removal event that would have fired this signal. The signal's precondition (no active timelock in the Vault's Authorizer path) is now permanently in a fired state — the current design is structurally equivalent to having executed a timelock removal. Drift Protocol an
Sources #
- GitHubhttps://github.com/balancer/balancer-deployments/blob/master/addresses/mainnet.jsonretrieved 2026-05-05
- https://etherscan.io/address/0x9E3cD0606Db55ac68845bB60121847823712ae05retrieved 2026-05-05
- https://forum.balancer.fi/t/bip-907-update-dao-multisig-signer-set-and-adjust-annual-stipend/6956retrieved 2026-05-05
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 →