★ delegatecall/call in proposal execution without allowlist

ether.fi's assessment for RD-F-039 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No on-chain proposal executor contract. Execution flows: Safe → OZ TimelockController.execute() → target.call(). OZ TimelockController uses `call` (not `delegatecall`) on the target. No general-purpose arbitrary-target proposal executor with delegatecall found.

Sources #

GitHub
EtherFiTimelock — OZ TimelockController baseEtherFiTimelock.sol — inherits OZ TimelockController (uses call, not delegatecall)retrieved 2026-04-28

Methodology #

Determine whether the governance executor contract uses `delegatecall` or `call` with proposal-supplied target, without enforcing an allowlist of permitted targets.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol ether-fi factor RD-F-039 score green collected_at 2026-04-28 13:58:46