Security-Council threshold reduction (RT)
Fluid'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 #
Not applicable. Fluid does not have a formalized Security Council structure with a documented M-of-N threshold (as in Drift Protocol's 3/5 Security Council). Fluid's admin is a team-controlled Avocado smart wallet — not a Security Council with a public threshold that could undergo a 3/5 → 2/5 reduction. The F182 signal (Security Council threshold reduction + timelock removal within 14 days) does not map to Fluid's governance topology. The team-wallet-as-sole-admin structure is a Cat 2/9 static finding, not a Cat 6B real-time threshold-change signal.
Sources #
- EtherscanFluid Liquidity Layer — proxy admin structure0x52Aa899454998Be5b000Ad077a46Bbe360F4e497 — admin is single Avocado wallet, no Security Councilretrieved 2026-04-29
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 →