Hot-patch deploys without timelock (last 30 days)
Chainlink CCIP's assessment for RD-F-138 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Normal config changes route through MCMS -> RBACTimelock (2-day delay). Bypasser MCMS can execute with no delay (break-glass). Rate limit changes are applied immediately (no timelock). No specific bypass events in last 30 days identified. Yellow: regular config changes are timelocked but bypass path exists and rate limits change without delay.
Sources #
- DocsRate Limit Management Overview | Chainlink DocumentationRate limit changes take effect immediately — 'changes are applied on-chain and take effect immediately' per rate-limit-management docsretrieved 2026-05-16
- smartcontractkit/ccip-owner-contracts READMEccip-owner-contracts README — bypasser role for break-glass scenarios; zero delay executionretrieved 2026-05-16
Methodology #
Count upgrades executed in the last 30 days without going through the declared timelock path.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol chainlink-ccip factor RD-F-138 score yellow collected_at 2026-05-16 01:55:09