★ delegatecall/call in proposal execution without allowlist
Chainlink CCIP's assessment for RD-F-039 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No OZ/Bravo Governor with delegatecall proposal execution. The CallProxy (17 SLOC) makes ordinary calls to the RBACTimelock — not delegatecall. The RBACTimelock executes scheduled calls to target contracts. No proposal-supplied arbitrary delegatecall target exists.
Sources #
- GitHubsmartcontractkit/ccip-owner-contracts READMEccip-owner-contracts README — CallProxy is callable by anyone and forwards to RBACTimelock; no delegatecall in execution pathretrieved 2026-05-16
- Code4rena 2023-07 ccip-owner-contracts auditCode4rena 2023-07 chainlink audit scope — CallProxy.sol 17 SLOC described as call-forwarding (ordinary call, not delegatecall) to RBACTimelockretrieved 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 chainlink-ccip factor RD-F-039 score not_applicable collected_at 2026-05-16 01:55:09