Timelock duration on upgrades
Frax Finance's assessment for RD-F-032 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Alpha TimelockController (0x821794): min delay ~86,400s (~1 day). Omega path: effective delay = 2-day veto window only (no post-veto timelock). frxUSD: NO timelock on admin actions per LlamaRisk explicit confirmation. Operative path (Omega + frxUSD) has 48h effective delay at best, 0h for direct multisig executions on frxUSD. Falls short of the 48-72h best-practice tier for $298M TVL protocols.
Sources #
- DocsHow It Works | Frax FinanceFrax docs: Alpha timelock initially set for two days (adjustable); Omega veto window is 2 daysretrieved 2026-05-17
- Frax Finance: Time Lock | EtherscanLegacy FXS Timelock 0x8412ebf45 — delay 172800s / 2 days; Alpha TimelockController 0x821794 — ~86400s confirmed via docsretrieved 2026-05-17
- Pegkeeper Onboarding Review: Frax frxUSD | Llama RiskLlamaRisk: no timelocks implemented in frxUSD contracts, meaning administrative actions have no enforced delayretrieved 2026-05-17
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 frax factor RD-F-032 score yellow collected_at 2026-05-16 20:44:31