Timelock on sensitive actions
Lombard 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 #
Upgrade path routes through TimeLock (1h delay). Pause functions (pauseTransfers, pauseMintBurn) and role-management functions appear to be direct AccessControl calls without TimeLock gating. The TimeLock duration itself (1h) is critically short. Not all sensitive actions are timelocked — partial timelock coverage.
Sources #
- Etherscanhttps://etherscan.io/address/0x055E84e7FE8955E2781010B866f10Ef6E1E77e59retrieved 2026-05-05
- https://etherscan.io/address/0x072072317469ebb6c340a47e41561c9c3b782bd9#coderetrieved 2026-05-05
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 lombard factor RD-F-033 score yellow collected_at 2026-05-05 12:03:08