Timelock on sensitive actions
ether.fi'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 #
Upgrades require EtherFiTimelock (1h) + 4-of-7 Safe — timelocked. However: weETH.recoverETH(), weETH.recoverERC20(), weETH.recoverERC721() are callable by WEETH_OPERATING_ADMIN_ROLE WITHOUT timelock. EtherFiNodesManager.sweepFunds() callable by ETHERFI_NODES_MANAGER_ADMIN_ROLE WITHOUT timelock. Pause/unpause operations bypass timelock by design (PROTOCOL_PAUSER role).
Sources #
- GitHubWeETH recover functions — untimelocked admin pathWeETH.sol — recoverETH/recoverERC20 with WEETH_OPERATING_ADMIN_ROLE, no timelockretrieved 2026-04-28
- EtherFiNodesManager.sweepFunds — untimelockedEtherFiNodesManager.sol — sweepFunds with ETHERFI_NODES_MANAGER_ADMIN_ROLEretrieved 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 ether-fi factor RD-F-033 score yellow collected_at 2026-04-28 13:58:46