Chainlink CCIP: control-plane safety record
5 indexed control-plane surfaces for Chainlink CCIP, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x0B04…0602, 0x4483…9449, 0x8022…6f7D, 0xb227…5Cb6
What differs
Changed / discrepant
- Timelock proposers: a 6-of-12 Safe besides the ManyChainMultiSigs (docs: all proposals from an MCMS): RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449: getRoleMemberCount(PROPOSER_ROLE) = 3: ManyChainMultiSig 0xE53289F32c8E690b7173aA33affE9B6B0CB0012F (the MCMS the docs link), GnosisSafeProxy … observed vs docs.chain.link (CCIP upgradability): 'All proposals originate from a ManyChainMultiSig (MCMS), which requires multiple independent signers to sign off.' documented
Show the full onchain evidence
RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449: getRoleMemberCount(PROPOSER_ROLE) = 3: ManyChainMultiSig 0xE53289F32c8E690b7173aA33affE9B6B0CB0012F (the MCMS the docs link), GnosisSafeProxy 0xD6597750bf74DCAEC57e0F9aD2ec998D837005bf (Safe v1.3.0, 6-of-12; also a canceller) and ManyChainMultiSig 0xD9757aA52907798d1aF2FDa7A6C0cC733E5aCf7e.
Show the full documented text
docs.chain.link (CCIP upgradability): 'All proposals originate from a ManyChainMultiSig (MCMS), which requires multiple independent signers to sign off.' / 'For example, you can view the Ethereum mainnet MCMS on Etherscan.'
Matched
- CCIP configuration owner: an RBACTimelock (Router, RMN proxy, TokenAdminRegistry, CCIPHome): matches the documentation
- RMN: uncurse is owner-only and the owner is an RBACTimelock; curse also by authorized callers: matches the documentation
- CCIP Directory addresses resolve on-chain; TokenAdminRegistry owned by the RBACTimelock: matches the documentation
- RBACTimelock operation 0x67cdd78a: scheduled and executed since #26,433,001: matches the documentation
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Weak · 0s: a bypasser role can execute without waiting the timelock delayEvidence: chainlink-ccip-config-owner-rbac-timelock-s24: BYPASSER_ROLE has 1 member, ManyChainMultiSig 0x117ec8aD107976e1dBCc21717ff78407Bc36aADc, which can execute calls immediately through bypasserExecuteBatch (no …
- Signer quorum
- Strong · Lowest controlling quorum: 6-of-12Evidence: chainlink-ccip-timelock-proposers-s24: … 0xD6597750bf74DCAEC57e0F9aD2ec998D837005bf (Safe v1.3.0, 6-of-12; also a canceller) and ManyChainMultiSig …
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Weak · Documentation differs from the chain (parameter delta)
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D"})Provenance · research credit
Reported by @random-solver through the Pacta Wave 2 pool (PR #111, fixture bounties/wave-2/ethereum-chainlink-ccip-timelock-op-0x67cd-post-pin.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0x8017…580e); credited on chainlink-ccip-rbactimelock-op-0x67cd-executed-s32. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.
CCIP configuration owner: an RBACTimelock (Router, RMN proxy, TokenAdminRegistry, CCIPHome)
Observed onchain. Router 0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D (Router 1.2.0, Sourcify match): owner() = RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449 (getMinDelay() = 10800s, 3 hours, for scheduled operations), which also owns the RMN proxy 0x411dE17f12D1A34ecC7F45f49844626267c75e81, TokenAdminRegistry 0xb22764f98dD05c789929716D677382Df22C05Cb6 and CCIPHome; BYPASSER_ROLE has 1 member, ManyChainMultiSig 0x117ec8aD107976e1dBCc21717ff78407Bc36aADc, which can execute calls immediately through bypasserExecuteBatch (no schedule, no delay).
Documented. docs.chain.link (CCIP upgradability): 'All configuration changes to CCIP-owned contracts must pass through a Role-Based Access Control Timelock (RBACTimelock) contract. Token pools are owned by token issuers, who configure them directly.' / 'The timelock then calls the target CCIP contracts with the specified changes.'
cast call 0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D \ "owner()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
RMN: uncurse is owner-only and the owner is an RBACTimelock; curse also by authorized callers
Observed onchain. RMN 0x0B047953451A207743fB62541B21199b95190602 (RMN 2.1.0, getARM() of the proxy 0x411dE17f12D1A34ecC7F45f49844626267c75e81; not verified on Sourcify): owner() = RBACTimelock 0x6608920e3F6b591EC3Cf15CA1DDf66fBE117F56A (getMinDelay() = 10800s for scheduled operations, admin = 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449; BYPASSER_ROLE has 1 member, 0x8C00Cc7cC37396e88BbFe66371341a59D1b5771F, which can execute calls immediately through bypasserExecuteBatch, no delay); isCursed() = false; 2 authorized curse callers.
Documented. docs.chain.link (RMN / RMN proxy API reference): 'Uncurses one subject or an array of subjects. Owner-only.' / 'Curses one subject or an array of subjects. Callable by the owner or an authorized caller.' / 'The owner may update the implementation via setARM'
cast call 0x0B047953451A207743fB62541B21199b95190602 \ "owner()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Timelock proposers: a 6-of-12 Safe besides the ManyChainMultiSigs (docs: all proposals from an MCMS)
Observed onchain. RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449: getRoleMemberCount(PROPOSER_ROLE) = 3: ManyChainMultiSig 0xE53289F32c8E690b7173aA33affE9B6B0CB0012F (the MCMS the docs link), GnosisSafeProxy 0xD6597750bf74DCAEC57e0F9aD2ec998D837005bf (Safe v1.3.0, 6-of-12; also a canceller) and ManyChainMultiSig 0xD9757aA52907798d1aF2FDa7A6C0cC733E5aCf7e.
Documented. docs.chain.link (CCIP upgradability): 'All proposals originate from a ManyChainMultiSig (MCMS), which requires multiple independent signers to sign off.' / 'For example, you can view the Ethereum mainnet MCMS on Etherscan.'
cast call 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449 \ "getRoleMemberCount(bytes32)" 0xb09aa5aeb3702cfd50b6b62bc4532604938f21248a27a1d5ca736082b6819cc1 \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
CCIP Directory addresses resolve on-chain; TokenAdminRegistry owned by the RBACTimelock
Observed onchain. TokenAdminRegistry 0xb22764f98dD05c789929716D677382Df22C05Cb6 (TokenAdminRegistry 1.5.0, Sourcify match): owner() = RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449; Router 0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D.getArmProxy() = 0x411dE17f12D1A34ecC7F45f49844626267c75e81.
Documented. docs.chain.link (CCIP Directory, Ethereum): 'Router 0x8022...6f7D' / 'RMN 0x411d...5e81' / 'Token admin registry 0xb227...5Cb6'
cast call 0xb22764f98dD05c789929716D677382Df22C05Cb6 \ "owner()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
RBACTimelock operation 0x67cdd78a: scheduled and executed since #26,433,001
Observed onchain. Chainlink CCIP RBACTimelock 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449 (Ethereum): isOperationDone(0x67cdd7…50d829) = true at this pin; isOperation = false at Pacta's published pin #26,433,001 (record chainlink-ccip-timelock-proposers-s24). ERC20LockBox 0xEd3fc513F5888BD65E868ba77D25E8799FfFa18e (no code at #26,433,001) owner() = 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449 at this pin. getMinDelay() = 10,800 s at both pins.
Documented. 'This repo contains a set of contracts used for administering Chainlink contracts' (github.com/smartcontractkit/ccip-owner-contracts)
cast call 0x44835bBBA9D40DEDa9b64858095EcFB2693c9449 \ "isOperationDone(bytes32)" 0x67cdd78af74492609eb87e0b8b8c6afb4e4fe86d95b4c11ec5c0d4116350d829 \ --block 26451608 --rpc-url "$ETH_RPC_URL" cast block 26451608 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x0266af5bcad519d93b3be78e41b76a62985e22fbe4feef043ac3225f6f217a17
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Chainlink CCIP differs from what the protocol documents. It turns to the neutral Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/chainlink-ccip/)
<a href="https://pacta.wtf/protocols/chainlink-ccip/"><img src="https://pacta.wtf/badges/chainlink-ccip.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/chainlink-ccip.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/chainlink-ccip.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Chainlink CCIP on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.
Maintaining Chainlink CCIP? Verify and reconcile the record
Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.
Need procurement paperwork? Request a commercial invoice (PDF).