Chainlink CCIP 2.0 exposes bridge risk, and issuer gates trigger stalls
Chainlink CCIP 2.0 adds optional Cross-Chain Verifiers (CCVs) that issuers or third parties can require alongside its default verifier. Tokens may be locked or burned on the source chain before all attestations arrive; the destination chain will not release or mint them until every required proof is supplied. An unavailable or unresponsive required verifier can therefore leave a transfer pending, and changing the executor or paying gas cannot bypass the check. Failed destination attempts may be retried after the problem is fixed, but Chainlink documents no general automatic refund or cancellation if a required verifier never attests. Whether this affects a particular token depends on its pool and route configuration; no named production asset using an issuer-run required CCV is identified.
