Chainlink Unveils CCIP 2.0
Chainlink has introduced CCIP 2.0, allowing institutions to implement their own custom verification systems for cross-chain transactions, rather than depending solely on Chainlink's default network. This development follows a significant security breach in April, where North Korean hackers stole $292 million from Kelp DAO, prompting firms like Kraken to switch to Chainlink for enhanced security.
New Cross-Chain Verifier
The updated infrastructure aims to address vulnerabilities in traditional bridge setups, which have lost billions due to single points of failure. With CCIP 2.0, institutions can now manage their own Cross-Chain Verifiers (CCVs) to provide an extra layer of scrutiny before transactions are approved. They also have the option to engage third-party services, such as Infosys or Nethermind, with initial setups available through Amazon Web Services and Google Cloud.
Despite these changes, Chainlink's core verification process remains intact, requiring consensus from 16 independent node operators for every transaction. However, the Risk Management Network, which previously provided additional verification, has been diminished in its role, with its automated offchain function no longer active in current deployments.




