Timelock duration on upgrades

Fluid'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 timelock on Fluid protocol upgrades. Avocado admin calls addImplementation()/removeImplementation()/setAdmin() on FluidLiquidityProxy with zero delay. InstaTimelock (2-day) covers legacy INST layer only. Fluid protocol: timelock_address = null per data cache.

Sources #

GitHub
Infinite Proxy: addImplementation() and setAdmin() — onlyAdmin only, zero delayfluid-contracts-public/contracts/infiniteProxy/proxy.solretrieved 2026-04-29
Etherscan
InstaTimelock: 2-day delay, admin = InstaGovernorBravoDelegator — governs INST layer only0xC7Cb1dE2721BFC0E0DA1b9D526bCdC54eF1C0eFCretrieved 2026-04-29

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 fluid factor RD-F-032 score red collected_at 2026-04-29 10:35:01