Chainlink CCIP Release Notes

The new CCIP Directory provides access to network, token, and lane configuration details, replacing the former CCIP Supported Networks pages.

The CCIP Explorer has been refreshed with a new home page, and the Transaction Details now load in a side panel. The CCIP Explorer also supports the option to display CCIP Private Transactions.

Chainlink's Cross-Chain Token (CCT) standard is now available, introducing a self-service model that allows token developers to enable their tokens in CCIP independently.

• Token developers can deploy, configure, and manage their tokens and token pools in Chainlink's Cross-Chain Interoperability Protocol (CCIP) without requiring manual deployment.
• Chainlink provides fully audited token pools, supporting either Burn & Mint or Lock & Mint mechanisms, which can be combined to provide different token handling mechanisms.
• Token developers maintain complete ownership of their token contracts, pools, and implementation logic, including configuration of rate limits for token transfers across multiple blockchains.
• The CCT standard avoids vendor lock-in and hard-coded functions, ensuring complete autonomy for projects managing cross-chain assets.
• CCT leverages Chainlink's Decentralized Oracle Networks (DONs) to provide secure cross-chain token operations, supported by the Risk Management Network and configurable rate limits.

Read the CCT conceptual documentation for more information. To learn how to enable your tokens in CCIP in minutes, follow the CCT tutorials.

Chainlink CCIP is available on Soneium Minato testnet. Visit the CCIP Directory page for more information.

Chainlink CCIP is publicly available on Scroll mainnet and testnet.

• Visit the CCIP Directory page for more information.

Chainlink CCIP is publicly available on Linea mainnet and testnet.

• Visit the CCIP Directory for more information.

Chainlink CCIP 1.5 is now available on testnet, introducing several new features and enhancements.

Risk Management Network Coverage: Certain CCIP integrations may not initially include the Risk Management Network (RMN). Blockchains can be integrated with CCIP in a phased approach, starting with the deployment of the Committing and Executing Decentralized Oracle Networks (DONs), followed by the addition of the Risk Management Network in a subsequent update. During a phased deployment, the relevant Commit Stores are configured in the Risk Management contract to always be considered blessed until the Risk Management Network has been deployed for that blockchain. Please refer to the CCIP Directory to identify which integrations utilize a phased approach, and review the CCIP Service Responsibility for more information.

New Version of EVMExtraArgs: Chainlink CCIP 1.5 introduces a new version of EVMExtraArgs, allowing users to set the allowOutOfOrderExecution parameter. This feature enables developers to control the execution order of their messages on the destination blockchain. The allowOutOfOrderExecution parameter is part of EVMExtraArgsV2 and is available only on lanes where the Out of Order Execution property is set to Optional or Required. Please consult the CCIP Directory to determine if your target lane supports this feature.

Chainlink CCIP is publicly available on ZKsync mainnet and testnet.

• Mainnet lane details
• Testnet lane details

Chainlink CCIP is publicly available on Metis mainnet and testnet.

• Mainnet lane details
• Testnet lane details

Chainlink CCIP is publicly available on Blast mainnet and testnet.

• Mainnet lane details
• Testnet lane details

Chainlink CCIP is publicly available on Mode mainnet and testnet.

• Mainnet lane details
• Testnet lane details

Chainlink CCIP is publicly available on Gnosis mainnet.

• Mainnet lane details

Chainlink CCIP is publicly available on Celo mainnet and Alfajores testnet.

• Mainnet lane details
• Testnet lane details

Chainlink CCIP is publicly available on the Polygon Amoy testnet.

• Testnet lane details

Chainlink CCIP is now Generally Available (GA) on mainnet and testnet.

To support your development and implementation needs, we encourage you to reach out to our team of experts for guidance and support. For expert advice, visit the Chainlink CCIP Contact form.

Additionally, the Chainlink CCIP local simulator is available to enhance your development workflow with CCIP. This tool allows you to simulate Chainlink CCIP functionality locally within your Hardhat and Foundry projects. The simulator is designed so you can test your contracts locally and transition smoothly to test networks without any modifications.

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.

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.

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.

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.

Chainlink CCIP is publicly available on the BNB Chain and Base mainnets. See the CCIP Directory page for more information.

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

Chainlink CCIP is publicly available on the BNB Chain and Base mainnets. See the CCIP Directory page for more information.

Chainlink CCIP is publicly available on the following testnet chains:

• Ethereum Sepolia
• Optimism Goerli
• Avalanche Fuji
• Arbitrum Goerli
• Polygon Mumbai

See the CCIP Directory page for more information.

Chainlink CCIP is available in early access on the following mainnet chains:

• Ethereum Sepolia
• Optimism Goerli
• Avalanche Fuji
• Arbitrum Goerli
• Polygon Mumbai

See the CCIP Directory page for more information.