Chainlink CCIP 2.0 flagged for potential token transfer delays
- —CCIP 2.0 launched on September 28 with CCVs, faster transfers and an ACE engine
- —The default Committee Verifier comprises 16 independent node operators
- —If a required CCV fails to respond, message execution is delayed
- —ACE policies on the destination chain can reject token minting after source-side burn
Why it matters: Institutional transfers via CCIP 2.0 cannot be treated as complete once the source-chain transaction settles; destination execution must be verified separately.
Source: TokenPost