Solv Protocol Moves $700M in Tokenized Bitcoin to Chainlink CCIP

TL;DR

• Solv Protocol is migrating $700M+ in tokenized Bitcoin (SolvBTC & xSolvBTC) from LayerZero to Chainlink CCIP across four chains.
• The KelpDAO exploit drained $292M (116,500 rsETH) from a LayerZero single-verifier bridge in April 2026, catalyzing the move.
• Combined Solv + KelpDAO migrations shift nearly $1B in assets to Chainlink CCIP, signaling a decisive DeFi flight to quality.

In the three weeks since KelpDAO's $292 million bridge catastrophe rewrote the cross-chain security playbook, the exits from LayerZero have accelerated. On May 7, 2026, Solv Protocol — one of the largest tokenized-Bitcoin platforms in decentralized finance — announced it is deprecating all LayerZero bridge support for SolvBTC and xSolvBTC and migrating that infrastructure to Chainlink's Cross-Chain Interoperability Protocol (CCIP), covering more than $700 million in tokenized BTC value. Taken together with KelpDAO's parallel pivot, the industry is watching the fastest voluntary infrastructure re-platforming it has seen since the 2022 Ronin hack.

The Migration: Mechanism, Scope, and the Four Chains That Lose LayerZero

Solv Protocol, launched in 2021 on Ethereum, built its business around SolvBTC — a wrapped Bitcoin token that lets holders deploy BTC across multiple blockchains to earn yield — and its yield-bearing variant xSolvBTC. These two assets sit at the core of what the protocol calls its BTCfi stack. As of the announcement, that stack carries more than $700 million in total asset value spread across several Layer-1 and Layer-2 networks.

In its official statement, Solv said it conducted a comprehensive internal security review of cross-chain systems before reaching its decision. The outcome: full standardization on Chainlink CCIP as the primary interoperability layer. LayerZero bridge support will be discontinued on four chains: Corn, Berachain, Rootstock, and TAC. The transition is being executed in phases to minimize disruption — users holding tokenized BTC positions across these chains will retain access throughout the migration window, though Solv has not published a granular timeline for completion.

Solv CTO Will Wang was direct in the company's public statement: "Security is the foundation of everything we build at Solv, and our migration to Chainlink CCIP reinforces that commitment at the highest level." Wang added that the move provides users "the highest assurance that proven, defense-in-depth infrastructure secures all cross-chain transfers."

The migration is technically significant beyond its dollar size. Solv had already been working with Chainlink for real-time collateral verification and SolvBTC pricing feeds — meaning the companies had an existing integration relationship. An official Chainlink X post confirmed that Solv Protocol has adopted the Cross-Chain Token (CCT) standard for SolvBTC.Jup across BNB Chain, Ethereum, and Solana, consolidating what was already a growing partnership into a full security architecture rebuild. What changes now is that CCIP becomes the exclusive cross-chain messaging backbone, retiring LayerZero's role entirely.

The Chainlink CCIP architecture that Solv is migrating to is materially different from what LayerZero offers in its default configuration. According to Chainlink's official CCIP documentation, the protocol runs cross-chain transactions through multiple decentralized oracle networks (DONs), a separate Risk Management Network, and a rate-limiting framework that enforces policies at both source and destination chains simultaneously. Chainlink Labs CBO Johann Eid framed Solv's migration as part of a clear industry pattern: "There is a clear and accelerating trend where protocols like Solv are migrating to Chainlink in a flight to quality." Eid also argued that major protocols are recognizing they can no longer rely on cross-chain infrastructure that "push liability onto users and blame them for systemic failures."

The KelpDAO Catalyst: How a $292M Off-Chain Attack Cracked the Bridge Market Wide Open

To understand why Solv's migration carries the weight it does, it is essential to understand what happened to KelpDAO on April 18, 2026 — and why the post-incident blame war between LayerZero and KelpDAO turned a single exploit into a systemic credibility crisis for the interoperability protocol.

On that Saturday, attackers — suspected by investigators to be linked to North Korea's Lazarus Group — drained 116,500 rsETH worth approximately $292 million from KelpDAO's LayerZero-powered bridge. According to a detailed post-mortem from Chainalysis's official blog, this was not a smart-contract bug — it was a sophisticated attack on off-chain infrastructure. The attackers compromised internal RPC nodes feeding data to the bridge verifier, then used a DDoS attack to knock clean backup nodes offline, forcing a failover to their poisoned infrastructure. The single verifier approved a fraudulent cross-chain message, and the bridge released the rsETH to an attacker-controlled address. At the transaction level, every on-chain call was indistinguishable from normal bridge activity: the validator signature was valid, the message format was valid, and the release function behaved exactly as designed.

The technical root cause was brutally simple: Kelp had deployed a 1-of-1 DVN (Decentralized Verifier Network) configuration — a setup requiring only one verifier to sign off on cross-chain messages. Once the attacker controlled that single verifier's view of reality, they effectively controlled the bridge. What made the fallout unusual was the scale of contagion: the attacker deposited stolen rsETH into Aave as collateral and borrowed against it, creating over $190 million in debt positions before Aave froze rsETH markets. Across DeFi, more than $13 billion was withdrawn in 48 hours, mostly by users with no rsETH exposure reacting to systemic fear.

The blame exchange that followed exposed a structural dispute about who bears responsibility for security configuration. LayerZero argued that Kelp used a single-verifier setup despite documented recommendations to use a multi-DVN model, and blamed Lazarus Group for the underlying attack. KelpDAO disputed this, arguing that LayerZero personnel had reviewed and approved that configuration before the exploit — and cited analysis showing that 47% of approximately 2,665 LayerZero applications were running the same 1-of-1 verifier setup at the time of the attack. LayerZero has since announced it will stop signing messages for projects using single-verifier configurations, but that decision came too late for KelpDAO's users — or for Solv's risk committee.

By contrast, Chainlink CCIP's architecture, as described in its official product documentation, deploys at least 16 independent node operators to validate each cross-chain transaction, and runs a separate Risk Management Network written in a completely different codebase to independently monitor for anomalous activity. Chainlink founder Sergey Nazarov has described CCIP as the only bridge where "three oracle networks — not three nodes, but three individual, separate networks" are responsible for confirming distinct aspects of each transaction. That architecture means compromising a single node or even a single code path cannot be sufficient to authorize fraudulent withdrawals. Bridge exploits, Chainlink argues in its official CCIP blog post, are "the direct result of poor design choices and development shortcuts" rather than inevitable outcomes of cross-chain systems.

For historical context, cross-chain bridges have collectively shed billions in user funds. Bridge protocols alone account for approximately $2.90 billion in cumulative DeFi losses, according to DeFiLlama data — a figure that takes on new weight when viewed alongside the 2022 Ronin bridge exploit ($622 million) and the 2024 WazirX hack ($230 million), both tied to nation-state actors. The KelpDAO exploit, now the largest single DeFi security incident of 2026, adds urgency to a debate the industry has been deferring since the first major bridge hack.

Industry Implications: Chainlink's Infrastructure Consolidation Moment — and LayerZero's Reckoning

The Solv migration, taken in isolation, would be a significant but bounded story about one protocol's infrastructure upgrade. In context — coming days after KelpDAO announced its own migration to CCIP — it represents something qualitatively different: the beginning of a market consolidation moment for cross-chain security infrastructure, where reputational shock is driving procurement decisions at a pace that normal technology adoption cycles do not produce.

The combined asset value moving from LayerZero to Chainlink CCIP across the two migrations now stands at nearly $1 billion. Chainlink's CBO Eid described the trend explicitly: "the industry's largest protocols are realizing they can no longer rely on cross-chain and oracle infrastructure that push liability onto users." That framing positions CCIP not just as a technical alternative but as a statement of institutional-grade accountability — a distinction that matters increasingly as tokenized real-world assets and institutional capital enter on-chain markets.

For LayerZero, the reputational calculus is challenging. The protocol is widely deployed — its data indicates thousands of applications built on its messaging infrastructure — and it has moved to reform its DVN policies since the exploit. But the public dispute with KelpDAO over who approved the fatal 1-of-1 configuration has been damaging precisely because it occurred in public, in real time, while users were counting losses. LayerZero's native token has experienced market pressure since the exploit, and the high-profile departures of two major protocols signals to remaining integrators that they should examine their own verifier configurations carefully.

There is a counterpoint worth acknowledging: Chainlink CCIP itself has not been stress-tested at the scale or adversarial sophistication that nation-state-backed groups have deployed against layered bridge infrastructure. Critics of security-by-architecture arguments note that complexity itself can introduce unforeseen attack surfaces, and that "battle-tested" infrastructure has not been battle-tested against every conceivable adversary. The fact that CCIP has not suffered a reported exploit to date is partly a function of the adversarial attention that higher-TVL, longer-lived bridges attract over time. As Solv's $700M migrates in, CCIP's security model will face genuine live-fire conditions rather than theoretical ones.

The broader BTCfi narrative is also relevant here. Solv's migration is not just a bridge story — it is a statement about what infrastructure Bitcoin-native yield products require to reach institutional scale. Chainlink is already certified to institutional security standards including SOC 2 Type 2, SOC 2 Type 1, and ISO/IEC 27001:2022, validated by Deloitte & Touche LLP. For asset managers evaluating wrapped Bitcoin products as on-chain treasury alternatives, that certification stack matters in ways that pure on-chain track records do not.

Key Takeaways

• Bridge infrastructure is now a make-or-break reputational factor: a single 1-of-1 verifier misconfiguration cost LayerZero two of its highest-TVL clients within weeks.
• LayerZero pushes back, blaming Kelp's application-level config choice, but its own data shows 47% of its ~2,665 apps ran the same single-verifier setup at attack time.
• Watch for: Solv phased deprecation timeline on Corn/Berachain/Rootstock/TAC; whether other large BTCfi protocols audit bridge stacks; and LayerZero's DVN-reform rollout response.

What Comes Next: Three observable signals will tell us whether this is the start of a durable infrastructure consolidation or a post-shock overcorrection. First, watch the LayerZero DVN-reform rollout: if the protocol can credibly enforce multi-verifier minimums across its remaining ~2,600 applications before the next exploit, it retains a path back. Second, track Solv's phased deprecation timeline on the four affected chains — any delays or user-liquidity disruptions will be scrutinized as evidence that migration costs are higher than the protocol acknowledged. Third, monitor whether other BTCfi and liquid staking protocols with nine-figure TVL now accelerate their own bridge security reviews, or whether Solv and KelpDAO remain isolated cases. If a third major protocol announces a CCIP migration in the next 60 days, the consolidation thesis becomes structurally credible — and LayerZero's position as a high-value-asset bridge becomes untenable without a verified architectural reform.

How we report: This article cites primary sources, regulatory filings, and on-chain data where available. BlockAI News uses AI tools to assist with research and first-draft generation; every article is reviewed and edited by a human editor before publication. Read our full How We Report page, Editorial Policy, AI Use Policy, and Corrections Policy.