Timelock duration on upgrades

Symbiotic's assessment for RD-F-032 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No TimelockController or equivalent deployed for Symbiotic core protocol. Factory whitelist/blacklist changes execute immediately via Safe majority. Data cache confirms governance.timelock_address=null. The immutable-core design explicitly omits timelocks — new implementations can be whitelisted with no delay.

Sources #

Internal
Symbiotic Data Cache — Timelock null.research/protocols/symbiotic/00-data-cache.json — governance.timelock_address: nullretrieved 2026-05-16
GitHub
MigratablesFactory.sol — no timelock on whitelist()MigratablesFactory.sol whitelist() is onlyOwner with no delay modifierretrieved 2026-05-16

Methodology #

Read the timelock delay (in hours) between a queued upgrade proposal and its executable state.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol symbiotic factor RD-F-032 score red collected_at 2026-05-16 09:25:24