3 hours ago
4
Key Takeaways
- CCIP 2.0 lets issuers require extra checks for a token transfer.
- Different assets can use different security and finality settings.
- Custom verification shifts more responsibility to the issuer.
- Faster routes may rely on different assumptions about finality.
- Users need to assess the specific token route, not only the bridge brand.
Chainlink’s CCIP 2.0 release notes introduce Cross-Chain Verifiers, new token-pool functions and configurable finality settings. Its security overview explains the broader architecture into which those features fit.
What changed?
Think of a bridge transfer as a gate between two blockchains. Before the gate opens, someone has to confirm that the asset was locked or destroyed on the other side. CCIP 2.0 lets the token issuer decide which additional checks...
English (US)