Security-Council threshold reduction (RT)
Frax Finance's assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Batch-24 Cat 6B signal (T-09 v1.1 candidate). Applicable: FraxGovernorOmega (0x953791D) controls Frax Comptroller multisig (0xB1748C79, 3/5) via FraxGuard (0xed53eb15); FraxGovernorAlpha (0xe8Ab863) controls governance parameters. Architectural protection: FraxGuard design means Omega cannot change Safe configurations or its own governance parameters — only Alpha (high-quorum, long-delay governor) can do this. Comptroller current configuration: threshold 3, owner_count 5 (per data-cache safe_multisigs[0]). No ChangedThreshold, AddedOwner, or RemovedOwner events on the Comptroller Safe found in recent Etherscan data. No timelock removal or new-signer addition within 14 days of any threshold change detected. Drift Protocol-class SC threshold reduction pattern (3/5 to 2/5 + timelock removal) not observed. Signal would not fire today.
Sources #
- EtherscanFrax Comptroller multisig — EtherscanComptroller 0xB1748C79 — 3/5 Safe, regular operational activity, no threshold-change events visible; ProxyAdmin consistentretrieved 2026-05-17
- Frax governance advanced concepts — FraxGuard designFraxGuard architecture: Omega cannot change Safe configs or own params — only Alpha can do thisretrieved 2026-05-17
- Frax Finance data cache — Comptroller Safe threshold confirmation00-data-cache.json safe_multisigs[0]: threshold=3, owner_count=5, address=0xB1748C79709f4Ba2Dd82834B8c82D4a505003f27retrieved 2026-05-16
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 →