Chainlink has launched the Cross-Chain Interoperability Protocol (CCIP) 2.0, which enables users to add their own security checks for transfers between blockchains. The update comes five months after the Kelp DAO hack in April, which resulted in the theft of approximately $292 million. This incident, linked to the Lazarus group, raised concerns about the risks associated with bridges operating on a single verification basis, as is the case with LayerZero technology.
According to Chainlink, CCIP has secured over $84 billion in cross-chain token value, with more than $15 billion migrating to the network in the last four months. CCIP 2.0 provides users with the ability to add their own checks to transfers, operating on a default network of 16 independent operators for verification. This allows companies to use their own security solutions or engage external providers such as Infosys and Nethermind. At the same time, Chainlink continues to verify all transfers through its network of operators.
According to Johann Eid, Managing Director of Chainlink Labs: "Historically, outdated bridges have lost billions due to unprotected infrastructure, while proprietary developments have been slow and costly." Additionally, Chainlink has also changed its protection mechanism, which previously used a separate network of nodes for double-checking transactions. Now, these independent checks can only come from user-added verifiers, meaning that without additional checks, users rely solely on one verification network. Users of the existing Chainlink service have automatically transitioned to the new version of CCIP 2.0. However, the company has not yet announced which institutions are using the new verifiers; it is only known that Aave and Maple have begun implementing other features of the update.
Related articles
