Timelock on sensitive actions
Curve Finance's assessment for RD-F-033 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Ownership/upgrade/fee actions: timelocked via 7-day Aragon vote. Parameter changes: timelocked via 7-day vote. Emergency eDAO actions (kill pool, kill gauge): 24-hour vote only — no 7-day timelock. The rescue/kill path for emergency is not subject to the full 7-day delay. 3-of-5 action types effectively timelocked at 7 days; emergency 'kill' is not.
Sources #
- DocsCurve DAO Protocol Ownership — action type timelockscurve.readthedocs.io/dao-ownership.html — ownership admin 30% quorum 51% support; parameter admin 15% quorum 51% support; emergency DAO 24hretrieved 2026-04-28
Methodology #
For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol curve-v2 factor RD-F-033 score yellow collected_at 2026-04-28 19:48:40