Chainlink launches CCIP 2.0 with configurable verification and finality

What happened

Chainlink launched CCIP 2.0 with optional Cross-Chain Verifiers, configurable finality, modular fees, built-in compliance hooks, and custom, permissionless, or no-executor modes.

What changed

Integrators and token issuers can opt into additional verifiers and execution controls or permit transfers before full source-chain finality. Faster-than-finality settings create a distinct reorg-risk profile and require configuration across the participating sender, pool, verifiers, executor, and receiver.

What did not change

Existing integrations retain full-finality behavior by default. Chainlink says the default verifier and executor remain in place, the Router interface remains unchanged, and legacy pools and receivers cannot opt into faster-than-finality transfers.

Confirmed

• CCIP 2.0 was announced as live on September 28, 2026.
• Faster-than-finality execution is opt-in; full source-chain finality remains the default.
• Cross-Chain Verifiers can add issuer-operated or third-party verification requirements.
• Chainlink documentation warns that a sufficiently deep reorganization after early execution can cause duplicate execution, token-supply inflation, unbacked tokens, or loss.
• Existing v1 pools and receivers continue to use full finality.

Still open

• Which Ketju-relevant integrations or assets will adopt CCIP 2.0 optional features.
• The exact verifier, finality, rate-limit, and executor configuration of each future production lane.
• Whether any currently approved dependency path migrated as part of the launch.

What it means for an advisor

• Update CCIP diligence so reviews capture lane-specific verifier, finality, executor, and rate-limit settings rather than relying only on protocol-level branding.
• Treat faster-than-finality as a distinct risk configuration and verify explicit opt-in at every participating layer.
• Do not infer that existing CCIP-dependent positions changed behavior merely because CCIP 2.0 launched.

Previous interpretation

The CCIP memo reflects the prior architecture centered on full-finality execution and the default Chainlink verification and execution path.