Guardian/pause-keeper distinct from upgrader
Symbiotic's assessment for RD-F-034 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No pause mechanism exists at the core protocol layer. OperatorRegistry and NetworkRegistry are permissionless with no pause function. DefaultCollateral has no pause. Vault-level pause is a per-vault curator option (user-deployed, not protocol-controlled). Guardian/pauser role distinction is not applicable to this architecture.
Sources #
- DocsParadigm — Symbiotic design: no pause at coreParadigm blog — immutable core with no permissioning mechanismsretrieved 2026-05-16
- OperatorRegistry — No pause mechanismOperatorRegistry source — no Pausable inherited, no pause() function in ABIretrieved 2026-05-16
Methodology #
Determine whether a pauser/guardian role exists and is held by an address distinct from the upgrader address.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol symbiotic factor RD-F-034 score not_applicable collected_at 2026-05-16 09:25:24