#Chainlink #CCIP
The trust model of cross-chain bridges is being dismantled and rebuilt: Chainlink will release CCIP 2.0 on September 28, delegating the ability to add security checks to enterprises themselves.
The default verification network—made up of 16 node operators—will continue to perform transaction-by-transaction checks. But now enterprises can also run their own set of validators, or outsource to providers such as Infosys and Nethermind. For enterprise fund operators, this addresses accountability—after something goes wrong, they don’t have to rely solely on explanations from the protocol party.
One sentence to judge it: what determines the quality of this upgrade isn’t the feature list, but how many institutions are willing to publicly disclose their validator configurations; if, within a year, only a handful of names run custom validators, then it will remain at the “optional” level.
$HBAR $TRUMP $SEI
The trust model of cross-chain bridges is being dismantled and rebuilt: Chainlink will release CCIP 2.0 on September 28, delegating the ability to add security checks to enterprises themselves.
The default verification network—made up of 16 node operators—will continue to perform transaction-by-transaction checks. But now enterprises can also run their own set of validators, or outsource to providers such as Infosys and Nethermind. For enterprise fund operators, this addresses accountability—after something goes wrong, they don’t have to rely solely on explanations from the protocol party.
One sentence to judge it: what determines the quality of this upgrade isn’t the feature list, but how many institutions are willing to publicly disclose their validator configurations; if, within a year, only a handful of names run custom validators, then it will remain at the “optional” level.
$HBAR $TRUMP $SEI
