The Automation StreamsLookup error handler is available to help you handle potential errors with StreamsLookup upkeeps. When you add the new checkErrorHandler function, you can define custom logic to handle some errors offchain and handle other errors onchain in performUpkeep.

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

The Chainlink Automation debugging script is available to help you debug and diagnose possible issues with registered upkeeps in Automation 2.1 registries. The script can debug custom logic upkeeps, log trigger upkeeps, and upkeeps that use StreamsLookup.

Chainlink Automation is live on Optimism Sepolia.

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

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

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

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.

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 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.