Solv's $700M Bitcoin Move Turns Cross-Chain Security Into a Responsibility Test

## Solv's $700M migration is a bridge-security decision, not a simple vendor swap  According to [Decrypt](https://decrypt.co/367154/solv-protocol-dump-layerzero-migrate-700m-tokenized-bitcoin-chainlink), Solv Protocol said on May 7, 2026 that it will move infrastructure supporting more than $700 million in tokenized Bitcoin from LayerZero to Chainlink's Cross-Chain Interoperability Protocol, or CCIP. The affected assets are SolvBTC and xSolvBTC, and the immediate bridge-support changes cover Corn, Berachain, Rootstock, and TAC. The timing matters because the announcement follows a security review after recent cross-chain attacks, including the Kelp DAO exploit that put LayerZero's verifier design under public dispute. ### What Solv confirmed on May 7 Solv said it is deprecating LayerZero bridge support for SolvBTC and xSolvBTC on the four named networks while standardizing cross-chain transfers on Chainlink CCIP. Will Wang, Solv Protocol's chief technology officer, framed the move around security assurance rather than distribution growth.  > "Security is the foundation."  > - Will Wang, Solv Protocol CTO Launched in 2021 on Ethereum, Solv is built around SolvBTC, a Bitcoin-linked token used to deploy Bitcoin-based assets across several chains. That makes the bridge layer more than plumbing: it sits between reserve representation, chain-specific liquidity, and user-facing yield products. #### The four retiring routes define the immediate blast radius The named networks give the migration a concrete operational boundary. Solv did not say in the raw report that every chain or every bridge path changes at once. The first practical test is whether users receive clear route-level guidance before LayerZero support is closed for Corn, Berachain, Rootstock, and TAC. ### Why the Kelp dispute changes how this will be judged The comparison point is Kelp DAO. Attackers drained roughly $292 million from infrastructure tied to Kelp DAO, and the later dispute centered on whether a single-verifier setup was responsible and who approved it. LayerZero blamed North Korea's Lazarus Group and said Kelp used a setup that did not follow its multiple-validator recommendation; Kelp disputed that account and said LayerZero had approved the configuration. This matters for Solv because the market is no longer evaluating cross-chain bridges only by brand, fee, or chain coverage. It is asking where verification authority sits, how many independent parties check a transfer, and who carries responsibility when a configuration becomes the weak point. ## Tokenized Bitcoin now exposes two layers of trust SolvBTC and xSolvBTC are meant to let Bitcoin-linked assets operate inside DeFi and BTCfi markets. That creates one trust layer around Bitcoin reserve backing and another around cross-chain movement. A user may understand the asset wrapper, but still face a separate bridge-risk model when that wrapper moves between chains. ### The bridge is part of the product, not an external utility For a tokenized Bitcoin issuer, interoperability can add distribution, but it also enlarges the surface where operational mistakes matter. The stronger editorial read is not that Chainlink automatically solves bridge risk. It is that Solv is narrowing its standard route to a security model it is more willing to defend in public. #### CCIP changes the risk map; it does not erase risk The raw report says Kelp's redesign around Chainlink CCIP would use multiple independent validators rather than a single verifier. That is a meaningful difference in control design. It still leaves other variables: contract integration quality, route-specific pause controls, user communication, and whether incident evidence is disclosed fast enough if something breaks. ## LayerZero now faces a responsibility-boundary problem LayerZero's challenge is not only that one more protocol is leaving. The larger issue is that bridge providers can become part of the accountability chain even when the disputed configuration belongs to an integrating project. If a protocol says it followed vendor-approved settings, and the vendor says safer settings were available, the market still has to assess that ambiguity. ### The next signals are operational, not promotional The next useful evidence will be concrete: the shutdown timeline for LayerZero routes, whether any assets need user action, how Solv describes route safety after migration, and whether the LayerZero-Kelp dispute produces clearer public evidence. If those details stay vague, the migration will look like risk reduction by supplier replacement. If they become precise, it can become a stronger template for high-value wrapped-asset governance. --- Author: Coinalx Editorial Team｜First published: 2026-05-08 | Last updated: 2026-05-08 Source: [decrypt.co](https://decrypt.co/367154/solv-protocol-dump-layerzero-migrate-700m-tokenized-bitcoin-chainlink)