★ delegatecall/call in proposal execution without allowlist
mETH Protocol'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 Governor or proposal execution contract with delegatecall path. TimelockController is OZ standard and executes direct function calls (not delegatecall). No user-supplied call targets in the governance execution path. Attack surface for delegatecall-based proposal execution does not exist in current architecture.
Sources #
- EtherscanTimelockController source code on EtherscanTimelockController is OZ standard implementation — source verified on Etherscan; executes direct calls, not delegatecallretrieved 2026-05-16
- mETH Protocol contracts repositoryrenounce_for_public.s.sol confirms direct function call structure; no proposal execution contract found in mantle-lsp/contractsretrieved 2026-05-16
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 meth-protocol factor RD-F-039 score green collected_at 2026-05-16 02:17:50