Proposal execution delay < 24h
Chainlink CCIP's assessment for RD-F-038 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Normal path enforces 48-hour delay (green). However, bypasser role (MCMS at 0x177A28...) executes changes with no delay via bypasserExecuteBatch. This zero-delay path exists legitimately as a break-glass mechanism. Yellow: normal path is 48h, but bypass path is 0h. Both paths are MCMS-gated (multi-party, not EOA), reducing worst-case risk.
Sources #
- EtherscanCCIP RBACTimelock — EtherscanRBACTimelock minimumDelay = 172,800 seconds (48h) for normal pathretrieved 2026-05-16
- smartcontractkit/ccip-owner-contracts READMEccip-owner-contracts README — bypasser role executes with no delay via bypasserExecuteBatch; intended for break-glass scenariosretrieved 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 chainlink-ccip factor RD-F-038 score yellow collected_at 2026-05-16 01:55:09