Large governance proposal queued
Chainlink CCIP's assessment for RD-F-101 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 v1 production signal. Applicable but modified — CCIP has no standard OZ/Compound Governor; proposals flow through ManyChainMultiSig (MCMS) + RBACTimelock. No unusual MCMS proposal pattern detected from public sources. Most recent documented governance actions were product deployments (v1.5 Jan 2025, v1.6 May 2025) — normal protocol lifecycle, not anomalous admin actions. The 2-day RBACTimelock minimum delay (172,800s per Etherscan-verified RBACTimelock) provides a veto window for node operators. No reports of unusual MCMS proposals in 2025-2026 from public sources.
Sources #
- EtherscanRBACTimelock — EtherscanRBACTimelock 0x9A709B7B69EA42D5eeb1ceBC48674C69E1569eC6 [? attribution unconfirmed] — minimumDelay = 172,800 seconds (2 days)retrieved 2026-05-16
- CCIP Onchain Architecture - UpgradabilityCCIP upgradability docs — two governance paths: time-locked review (2-day) and explicit-approval by independent signersretrieved 2026-05-16
Methodology #
Detect whether a governance proposal with potentially protocol-impactful payload has been queued for execution (including Security-Council threshold-reduction variant).
See the full factor methodology and distribution across all protocols →