Proposal execution delay < 24h
mETH Protocol's assessment for RD-F-038 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
TimelockController minDelay = 0 seconds. Effective execution delay after proposal pass = 0. This is below the 24h threshold. Any queued operation can be executed in the same block as scheduling, providing no meaningful window for community reaction or emergency intervention.
Sources #
- EtherscanTimelockController Etherscan — minDelay=0 confirmedTimelockController 0xc26016... constructor args: minDelay=0; getMinDelay() confirmed = 0 via Etherscan readContractretrieved 2026-05-16
- mETH Protocol profile §11 flags for governance-admin-analystProfile §6 and §11: TimelockController minDelay=0 flagged as ANOMALY — most material Cat 2 finding per profilerretrieved 2026-05-16
Methodology #
Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol meth-protocol factor RD-F-038 score red collected_at 2026-05-16 02:17:50