Chainlink launches new version of its crypto bridge tech 'CCIP' to give apps more control over their security

Chainlink launched CCIP 2.0 on Sept. 28, 2026, updating its cross-chain messaging and token transfer infrastructure to give application teams more control over on-chain security checks. The new release allows projects to layer optional verifiers—either run by the projects themselves or provided by third parties such as Infosys and Nethermind—on top of Chainlink's built-in verifier network. Under CCIP 2.0, Chainlink's default verifier set is composed of 16 independent node operators that must reach a quorum for transfers to complete. That contrasts with some rival bridge configurations that have relied on a single verifier, an arrangement blamed for the April exploit that drained about $292 million in rsETH from Kelp DAO. Chainlink said the optional verifiers can be added by companies to provide custom checks for transfers. The release also changes how Chainlink handles its prior separate safeguard, the Risk Management Network. That network no longer functions as a distinct double-check layer; instead, Chainlink says optional verifiers can provide equivalent independent scrutiny. As a result, a user who opts not to add extra verifiers will rely on the single default 16-operator network rather than two separate networks. Chainlink said existing integrations will continue to work with CCIP 2.0 without modification. The company has not disclosed specific institutions using the new verifier options yet, though it noted that Aave and Maple have begun adopting some other features from the upgrade. Chainlink framed the change as simplifying security choices for application teams that may lack deep cross-chain security expertise.