Security-Council threshold reduction (RT)
Liquid Collective (LsETH)'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 #
Cat 6B batch-24 addition; T-09 v1.1 candidate signal. Drift-pattern: Security Council threshold reduction + timelock removal within 14 days of either event. For Liquid Collective: the functional equivalents are the Proxy Admin Safe (4-of-7, upgrade authority) and Executor Safe (2-of-3, execution authority). No timelock currently exists between the Safes and proxy contracts (governance.timelock_address = null). This means the timelock-removal sub-trigger of the Drift pattern is architecturally pre-satisfied -- any future Safe threshold reduction would complete the two-step precursor pattern alone. No threshold reduction event detected at assessment date: Proxy Admin Safe remains 4-of-7, Executor Safe remains 2-of-3, per data cache (fetched 2026-05-16). Score is yellow because the architecture creates structural elevated sensitivity for this signal: if any threshold reduction occurs, the Drift-pattern precursor would be complete without requiring a separate timelock-removal step. Galaxy
Sources #
- EtherscanProxy Admin Safe - EtherscanProxy Admin Safe 0x8EE3fC0Bcd7B57429203751C5bE5fdf1AB8409f3 on Ethereum mainnet; threshold and owner set verifiable via Safe Transaction Serviceretrieved 2026-05-17
- Galaxy Expands into Liquid Staking as Development Company for Liquid Collective - PR NewswireGalaxy Digital acquired Alluvial Finance (development company for Liquid Collective) on December 4, 2025 -- organizational change that may affect Safe signer compositionretrieved 2026-05-17
- Liquid Collective data cache - safe_multisigs and governance00-data-cache.json safe_multisigs[0] threshold=4 owner_count=7 role=proxy_admin; safe_multisigs[2] threshold=2 owner_count=3 role=executor; governance.timelock_address = nullretrieved 2026-05-17
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 →