Chainlink Node v2.8.0 is now available. See the Release Notes for details.

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 v1.2.0 configuration page.
• USDC transfers are currently supported on several lanes. See the the Supported Networks 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.

You can use external module imports with Chainlink Functions source code on mainnet networks. See the Using Imports with Functions tutorial to see an example of how to import and use imported modules with your Functions source code. This feature requires the Functions Toolkit NPM package v0.2.7 or later.

Chainlink Functions is available on Arbitrum Mainnet.

Chainlink CCIP is publicly available on Arbitrum Sepolia. See the CCIP testnet configuration page for more information.

You can use external module imports with Chainlink Functions source code on testnet networks. See the Using Imports with Functions tutorial to see an example of how to import and use imported modules with your Functions source code. This feature requires the Functions Toolkit NPM package v0.2.7 or later. This feature is available only on testnets. Modules will not import or execute on Functions requests for mainnet networks at this time.

Chainlink Functions is available on the Arbitrum Sepolia testnet.

Chainlink Node v2.7.2 is now available. See the Release Notes for details.

CCIP v1.0.0 has been deprecated on testnet. You must use the new router addresses listed in the CCIP v1.2.0 configuration page 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 v1.2.0 configuration page.USDC transfers are currently supported on several lanes. See the the Supported Networks 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.

Chainlink Automation is live on Base.