The maximum gasLimit that you can set for CCIP messages on mainnet has been increased to 3,000,000 gas units. The change has been documented in the Service Limits page.

Chainlink's CCIP now supports WETH (Wrapped Ether) transfers through the Lock and Unlock token mechanism.

This feature allows CCIP to securely lock tokens on the source blockchain and subsequently release an equivalent amount of tokens on the destination blockchain, facilitating seamless cross-chain transfers of WETH. The introduction of this mechanism enables WETH transfers across several key lanes.

For a specific lane configuration, see the CCIP Directory. For more detailed information about the Lock and Unlock mechanism and its applications, read the Token Pools page.

CCIP v1.0.0 is no longer supported on mainnet. You must use the new router addresses listed in the CCIP Directory page.

Chainlink CCIP is publicly available on Wemix and Kroma for both mainnet and testnet. See the CCIP Directory for network details.

CCIP v1.0.0 is no longer supported on testnet. You must use the new router addresses listed in the CCIP Directory.

Chainlink Data Streams is available in Early Access on Arbitrum Sepolia. Verifier proxy addresses and Feed IDs are available on the Data Streams Feed IDs page.

CCIP v1.0.0 has been deprecated on mainnet. You must use the new router addresses listed in this page before March 31st, 2024. Please note that there is no change to the router interface. The CCIP v1.0.0 mainnet routers will continue to function in parallel until March 31st, 2024, but we highly recommend switching to the v1.2.0 routers as soon as possible. If you currently use CCIP v1.0.0, use the @chainlink/contracts-ccip npm package version 0.7.6. To migrate to v1.2.0, use version 1.2.1 of the npm package or later. Please refer to the release notes for a comprehensive overview of the enhancements and new features in v1.2.0.

• There is no change to the router interface, but you must use the new router addresses listed in the CCIP Directory.
• USDC transfers are currently supported on several lanes. See the the CCIP Directory page to get a specific lane's token addresses and rate limits.
• The message sequencing process is simplified in CCIP message handling by removing the strict sequencing flag from the extraArgs field in CCIP messages.
• The gas limit and maximum message data length for CCIP messages have been adjusted on mainnets. These changes are detailed in the Service Limits documentation.
• To interact with CCIP v1.2.0, use the @chainlink/contract-ccip npm package.

Chainlink CCIP is publicly available on Arbitrum Sepolia. See the CCIP Directory for more information.

CCIP v1.0.0 has been deprecated on testnet. You must use the new router addresses listed in the CCIP Directory before January 31st, 2024. Please note that there is no change to the router interface. The CCIP v1.0.0 testnet routers will continue to function in parallel until January 31st, 2024, but we highly recommend switching to the v1.2.0 routers as soon as possible. If you currently use CCIP v1.0.0, use the @chainlink/contracts-ccip npm package version 0.7.6. To migrate to v1.2.0, use version 1.2.1 of the npm package or later.

• There is no change to the router interface, but you must use the new router addresses listed in the CCIP Directory.USDC transfers are currently supported on several lanes. See the the CCIP Directory page to get a specific lane's token addresses and rate limits.
• We've simplified the message sequencing process in our CCIP message handling by removing the strict sequencing flag from the extraArgs field in CCIP messages.
• The gas limit and maximum message data length for CCIP messages have been adjusted on testnets. These changes are detailed in the Service Limits documentation.
• To interact with CCIP v1.2.0 , use the @chainlink/contract-ccip npm package.

Arbitrum Goerli is no longer supported. Arbitrum Sepolia support will be added at a later date.