Several decentralized finance protocols overseeing close to $1 billion in combined assets are moving, or have chosen to build, their cross-chain infrastructure around Chainlink’s Cross-Chain Interoperability Protocol (CCIP) instead of Layerzero. The most prominent moves involve Solv Protocol and Re, while Huma Finance has also selected CCIP for a new product. Together, these decisions underscore a broader market preference for bridge designs that emphasize default security protections after a major exploit hit the ecosystem earlier this year.
Solv migrates tokenized bitcoin infrastructure
Solv Protocol said it is migrating its full tokenized bitcoin stack, including SolvBTC and xSolvBTC, from Layerzero to Chainlink CCIP. The transition covers roughly $700 million in assets and spans bridge deployments on Corn, Berachain, Rootstock, and TAC. As the process unfolds in phases, Layerzero support on those chains is being deprecated.
According to Solv, the decision followed an extensive security review. The team framed the shift as a move toward what it called a more secure cross-chain setup, while also noting that CCIP was already part of its collateral verification architecture. In that sense, the migration appears to be both a security upgrade and an operational consolidation of tools already used within the protocol.
Re makes CCIP the exclusive bridge for reUSD
Onchain reinsurance protocol Re, also known as re.xyz, has taken a similarly decisive step. The team selected Chainlink CCIP as the exclusive cross-chain infrastructure for reUSD, its yield-bearing stablecoin. Re said reUSD has a market capitalization of more than $160 million, while the protocol’s total value locked stands above $475 million.
Re cited several factors behind the choice. Among them were CCIP’s redundant validation by 16 or more independent node operators, native rate-limit circuit breakers designed to react to abnormal transfer activity, and SOC 2 Type 2 compliance. The protocol said that, in the wake of recent DeFi hacks, it prioritized security track record, third-party audits, and institutional-grade standards over speed and cost when evaluating bridge providers.
KelpDAO exploit intensified scrutiny on bridge risk
The backdrop to these migrations is the April 18, 2026 exploit involving a Layerzero-powered bridge used by KelpDAO. In that incident, attackers drained approximately 116,500 rsETH, worth around $292 million at the time. Reports said the stolen funds were later used as collateral on Aave v3, turning the exploit into one of the year’s most closely watched security failures in DeFi.
KelpDAO attributed the breach to a 1-of-1 verifier configuration within Layerzero’s setup, arguing that the design introduced a dangerous single point of failure. Layerzero rejected that characterization, saying KelpDAO had manually chosen a single-verifier model that went against Layerzero’s own recommendations. The company also said it would no longer support such configurations in the future.
That public disagreement did more than assign blame. It reopened a broader industry debate about how verifier configurations should be handled in omnichain token systems, whether users and protocols can safely rely on flexible models, and how much responsibility should sit with protocol operators versus infrastructure providers. In practice, the exploit pushed teams to revisit not just bridge performance, but the safety assumptions built into default deployments.
Why CCIP is gaining attention
Chainlink CCIP uses a different security model from the one at the center of the Layerzero controversy. Each bridge lane relies on multiple independent decentralized oracle networks, with validation handled by 16 or more security-reviewed node operators. Execution and risk management are separated across different codebases, and built-in transfer rate limits serve as circuit breakers if suspicious volume appears.
For protocols managing large or institutionally sensitive pools of capital, those design choices are increasingly being viewed as important baseline protections rather than optional features. Solv specifically noted that CCIP had already been integrated into part of its stack, making the migration a natural extension of infrastructure it already trusted. Re described the move as an obvious upgrade given Chainlink’s role in its broader architecture.
Chainlink founder Sergey Nazarov commented publicly on the trend, saying he was encouraged to see teams recognize the value of what he described as “real security.” He added that, in an industry where securing value is central to every product, reliable and secure infrastructure tends to prevail over lower-quality alternatives. He also said the replacement of weaker oracle and infrastructure setups by Chainlink-based systems has been an ongoing trend for years.
Huma joins the shift, though not as a migration
Huma Finance, a PayFi-focused network, also chose CCIP as the exclusive bridge for its PST yield product. Unlike Solv and Re, however, Huma was not migrating away from an active Layerzero deployment. Instead, its decision was presented as a forward-looking infrastructure choice made after the same kind of security evaluation that influenced the other protocols.
This distinction matters because it suggests the movement is not solely reactive. In some cases, teams are not merely replacing one provider after a breach; they are setting infrastructure standards for future products based on what they now view as stronger security assumptions. That gives Chainlink CCIP an opportunity not only to win migrations, but also to shape the default choice for new cross-chain deployments.
A broader signal for DeFi bridge standards
Measured by the scale of affected assets, the shift is significant. Solv alone accounts for about $700 million, while Re brings a stablecoin with over $160 million in market value and a protocol TVL above $475 million. Even without counting all figures the same way, the overall movement highlights a substantial reallocation of confidence in cross-chain infrastructure.
The larger takeaway is that bridge selection is no longer being framed primarily around convenience, flexibility, or cost efficiency. After a nine-figure exploit, default architecture has become central to protocol decision-making. Teams appear increasingly unwilling to depend on configurations that can expose them to catastrophic failure if implemented incorrectly.
For holders of rsETH, SolvBTC, xSolvBTC, and reUSD, the protocols involved have said the transitions are being managed in phases and should require little action from users in most cases. Operationally, that means the migration story is less about retail disruption and more about the internal standards protocols are choosing for the next stage of cross-chain finance.
In that sense, this is more than a vendor switch. It is a signal that, across DeFi, the market is placing higher value on bridge systems that embed security into their default architecture. The recent decisions by Solv, Re, and Huma suggest that after the KelpDAO incident, security-first cross-chain design is becoming a defining competitive advantage.