Timelock duration on upgrades

QuickSwap'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 contract exists anywhere in QuickSwap's architecture. Cache timelock_address=null confirmed true negative. Admin multisig executes with zero delay. No TimelockController, no Compound Timelock, no custom timelock found on Polygon or any other chain.

Sources #

Internal
QuickSwap Profile §6 — No timelock.research/protocols/quickswap/00-profile.md §6: Timelock: None confirmed — cache timelock_address: null, config timelock_address: null. True negative.retrieved 2026-05-16
Internal
QuickSwap Data Cache — timelock_address=null.research/protocols/quickswap/00-data-cache.json: timelock_address=null, confirmed true negativeretrieved 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 quickswap factor RD-F-032 score red collected_at 2026-05-16 08:48:31