## Critical Update: Migration to the `chainlink-ccip` Repository Before we dive into the upcoming section on Chainlink’s Cross-Chain Interoperability Protocol (CCIP), there is a critical update regarding the project structure that you need to be aware of. Since the creation of this course content, the official GitHub repository used for Chainlink CCIP development has migrated. The original repository featured in the video lectures has been **archived** by the maintainers and is now read-only. To ensure your code works correctly and adheres to current standards, you must use the new, active repository. ### The Repository Change You will notice that the videos may reference the old repository. Please note the following change: * **Archived (Do Not Use):** `smartcontractkit/ccip` * **Active (Use This):** `smartcontractkit/chainlink-ccip` You should direct all your cloning, referencing, and documentation searches to the new **`chainlink-ccip`** repository. ### Technical Impact on Your Workflow While the core concepts and logic of CCIP remain largely consistent, this migration introduces syntax and configuration changes that will affect your development workflow. As you proceed through the lessons, be prepared to adjust the following: 1. **Installation Commands:** Because the package location and name have changed, the command line instructions (using NPM, Yarn, or Foundry) used to install dependencies in the video will differ from what is currently required. 2. **Import Paths:** When writing your Smart Contracts or deployment scripts, the directory structure within the `node_modules` or library folders will be different. You will need to update your import statements to reflect the new file paths in the `chainlink-ccip` repository. 3. **API Adjustments:** There have been minor updates to the API. Expect slight differences in function calls or how you interact with the router and protocol compared to the video demonstrations. ### How to Navigate the Course To help you manage these changes, we have added **text-based notes and comments** accompanying the videos in this section. **Do not rely solely on the code explicitly typed in the video.** Instead, please verify the text resources provided with each lesson. These notes will highlight the specific tweaks required—such as the correct install commands and updated import paths—to ensure you can successfully build and deploy your project using the modern codebase.
chainlink-ccip RepositoryBefore we dive into the upcoming section on Chainlink’s Cross-Chain Interoperability Protocol (CCIP), there is a critical update regarding the project structure that you need to be aware of.
Since the creation of this course content, the official GitHub repository used for Chainlink CCIP development has migrated. The original repository featured in the video lectures has been archived by the maintainers and is now read-only. To ensure your code works correctly and adheres to current standards, you must use the new, active repository.
You will notice that the videos may reference the old repository. Please note the following change:
Archived (Do Not Use): smartcontractkit/ccip
Active (Use This): smartcontractkit/chainlink-ccip
You should direct all your cloning, referencing, and documentation searches to the new chainlink-ccip repository.
While the core concepts and logic of CCIP remain largely consistent, this migration introduces syntax and configuration changes that will affect your development workflow. As you proceed through the lessons, be prepared to adjust the following:
Installation Commands:
Because the package location and name have changed, the command line instructions (using NPM, Yarn, or Foundry) used to install dependencies in the video will differ from what is currently required.
Import Paths:
When writing your Smart Contracts or deployment scripts, the directory structure within the node_modules or library folders will be different. You will need to update your import statements to reflect the new file paths in the chainlink-ccip repository.
API Adjustments:
There have been minor updates to the API. Expect slight differences in function calls or how you interact with the router and protocol compared to the video demonstrations.
To help you manage these changes, we have added text-based notes and comments accompanying the videos in this section.
Do not rely solely on the code explicitly typed in the video. Instead, please verify the text resources provided with each lesson. These notes will highlight the specific tweaks required—such as the correct install commands and updated import paths—to ensure you can successfully build and deploy your project using the modern codebase.
An essential guide to the Chainlink CCIP Repository Migration - Learn why you must switch to the active chainlink-ccip repository and how to navigate differences in installation and syntax. This update ensures your workflow remains accurate by providing the correct import paths and commands to replace the archived video references.
Previous lesson
Previous
Next lesson
Next
Course Overview
About the course
Advanced smart contract development
How to develop a stablecoin
How to develop a DeFi protocol
How to develop a DAO
Advanced smart contracts testing
Fuzz testing
Manual verification
Web3 Developer Relations
$85,000 - $125,000 (avg. salary)
Web3 developer
$60,000 - $150,000 (avg. salary)
Smart Contract Engineer
$100,000 - $150,000 (avg. salary)
Smart Contract Auditor
$100,000 - $200,000 (avg. salary)
Security researcher
$49,999 - $120,000 (avg. salary)
Web3 engineer, educator, and Cyfrin co-founder. Patrick's smart contract development and security courses have helped hundreds of thousands of engineers kickstarting their careers into web3.
Guest lecturers:
Last updated on February 17, 2026
Duration: 37min
Duration: 3h 06min
Duration: 5h 03min
Duration: 6h 22min
Duration: 2h 48min
Duration: 1h 24min
Duration: 4h 28min
Duration: 1h 20min
Duration: 1h 11min
Course Overview
About the course
Advanced smart contract development
How to develop a stablecoin
How to develop a DeFi protocol
How to develop a DAO
Advanced smart contracts testing
Fuzz testing
Manual verification
Web3 Developer Relations
$85,000 - $125,000 (avg. salary)
Web3 developer
$60,000 - $150,000 (avg. salary)
Smart Contract Engineer
$100,000 - $150,000 (avg. salary)
Smart Contract Auditor
$100,000 - $200,000 (avg. salary)
Security researcher
$49,999 - $120,000 (avg. salary)
Web3 engineer, educator, and Cyfrin co-founder. Patrick's smart contract development and security courses have helped hundreds of thousands of engineers kickstarting their careers into web3.
Guest lecturers:
Last updated on February 17, 2026