Security-Council threshold reduction (RT)
Symbiotic'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 #
Security-Council threshold reduction RT signal (batch-24, Cat 6B). Signal fires when a bridge or protocol Security Council multisig executes a threshold reduction or timelock removal. Symbiotic has no publicly disclosed Security Council multisig, no governor, no timelock (timelock_exists: false, governor_exists: false, multisig_address: null). Core contracts are immutable — no upgrade path, no threshold to reduce. The Drift Protocol attack vector that motivated F182 (3/5 to 2/5 Security Council change + timelock removal, 6 days before DPRK exploit) cannot replicate on Symbiotic's architecture. If governance-admin-analyst identifies a previously undisclosed Security Council structure on the mutable periphery, this assessment should be revisited.
Sources #
- InternalSymbiotic profile meta — governance fields.research/protocols/symbiotic/00-profile.meta.json — timelock_exists: false, governor_exists: false, multisig_address: null, immutable_core: trueretrieved 2026-05-16
- Paradigm — From Staking to RestakingParadigm blog: Symbiotic will never have a central multisig, slashing committee, or other permissioning mechanismsretrieved 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 →