#Chainlink上线CCIP2支持企业验证
Chainlink has launched CCIP 2.0 today. The core is just one thing: cross-chain transfers. Institutions can add an extra layer of verification if they want—have themselves sign, outsource signing to companies like Infosys, and only after signing can the transfer reach the other chain. By default, the 16 Chainlink nodes still stand as the fallback.
There are also compliance checks, adjustable speed, and fees that can be itemized. AWS, Google Cloud, ANZ, and Fidelity International are all on the approved list.
In my personal view, this is meant to help banks and the parties issuing tokens “check the box” for cross-chain operations—not to do a favor for retail users. When a bridge incident happens, it often comes down to “only one person decides.” Being able to add a gate is a good thing. But adding verification doesn’t necessarily mean it’s safer—who operates the nodes, who manages the keys—those issues still shift some of the blame back onto you
Chainlink has launched CCIP 2.0 today. The core is just one thing: cross-chain transfers. Institutions can add an extra layer of verification if they want—have themselves sign, outsource signing to companies like Infosys, and only after signing can the transfer reach the other chain. By default, the 16 Chainlink nodes still stand as the fallback.
There are also compliance checks, adjustable speed, and fees that can be itemized. AWS, Google Cloud, ANZ, and Fidelity International are all on the approved list.
In my personal view, this is meant to help banks and the parties issuing tokens “check the box” for cross-chain operations—not to do a favor for retail users. When a bridge incident happens, it often comes down to “only one person decides.” Being able to add a gate is a good thing. But adding verification doesn’t necessarily mean it’s safer—who operates the nodes, who manages the keys—those issues still shift some of the blame back onto you
