- Kraken will phase out LayerZero and rely on Chainlink CCIP as its exclusive cross-chain infrastructure for kBTC and future wrapped assets.
- The move follows a USD $292 million exploit involving Kelp and a LayerZero-powered bridge, which reignited concerns around cross-chain security.
- Billions in TVL have reportedly shifted away from LayerZero-based setups, while Chainlink strengthens its role in institutional-grade interoperability.
- Kraken keeps control over issuance and custody of kBTC; Chainlink CCIP replaces only the transport layer that moves tokens across blockchains.
Kraken is overhauling how its wrapped bitcoin token kBTC travels between blockchains. The exchange has decided to abandon LayerZero as its cross-chain provider and instead lean on Chainlink’s Cross-Chain Interoperability Protocol (CCIP) as the exclusive infrastructure for moving kBTC and other wrapped assets across networks.
The shift comes on the heels of a USD $292 million exploit tied to Kelp, a liquid restaking protocol whose bridge relied on LayerZero. That incident once again highlighted how fragile some interoperability setups can be when they hold large amounts of value, and it has prompted a broader rethinking of bridge architecture across the industry.
Why Kraken is replacing LayerZero with Chainlink CCIP
According to information cited from CoinDesk and public messaging by industry observers, Kraken will now use Chainlink CCIP as its sole cross-chain messaging and token transfer layer for kBTC and future wrapped products. In practice, this means that whenever those tokens need to move between supported blockchains, the routing and verification logic will be handled by Chainlink’s protocol rather than LayerZero.
The decision is not happening in a vacuum. It follows what has been described as the largest crypto exploit of 2026 so far, in which Kelp lost 116,500 rsETH (a restaked ether derivative) via a bridge configured with LayerZero technology. The exploit, valued at around USD $292 million, intensified scrutiny of existing cross-chain schemes, especially those protecting high-value collateral.
LayerZero later acknowledged that it had made a mistake in allowing its own verifier network to secure assets of substantial worth under the configuration used in Kelp’s bridge. That admission added pressure on the protocol and fueled doubts around legacy interoperability models that depend heavily on a small set of validators or centralized trust assumptions.
Within that context, Kraken’s move can be read as both a risk-management step and a signal to the rest of the market. When a major exchange revises its exclusive interoperability partner for core products like wrapped bitcoin, it usually reflects more than a cosmetic technical tweak; it indicates a shift in how institutional players perceive security trade-offs in cross-chain infrastructure.
The Kelp exploit and its ripple effects across interoperability
The Kelp incident has effectively become a reference point for cross-chain risk in 2026. Beyond the immediate loss of funds, it challenged assumptions about how much trust can be placed in bridge providers and their validator configurations, particularly when those providers secure assets that underpin complex DeFi strategies.
In the exploit, attackers targeted Kelp’s bridge to siphon off rsETH—its restaked ether token—using a flaw associated with the LayerZero-powered setup. The scale of the attack turned it into a case study for the broader ecosystem, prompting teams to reassess how much exposure they were willing to maintain to similar architectures.
The aftermath did not stop at Kelp. Several projects, including Kelp itself, Solv and Re, began to reconfigure or migrate away from the affected infrastructure. Various estimates suggest that more than USD $3 billion in total value locked (TVL) has shifted away from designs tied to LayerZero since the exploit, as protocols look for alternatives perceived as more robust or better aligned with institutional demands.
For Kraken, this backdrop created a strong incentive to move quickly. The exchange manages assets on behalf of a large user base, and any perceived fragility in its cross-chain plumbing can have reputational consequences. By adopting Chainlink CCIP as its exclusive interoperability layer, Kraken appears to be opting for an approach that it considers more appropriate for high-value, custodial wrapped tokens.
What changes for kBTC and Kraken’s wrapped assets
Kraken introduced kBTC in 2024 as a 1:1 bitcoin-backed token, initially deployed on Ethereum and OP Mainnet. The token is designed to let users put BTC to work in ecosystems where native bitcoin is harder to integrate, such as DeFi platforms, lending protocols, or decentralized exchanges built on smart contract networks.
As of the latest data referenced from CoinGecko in the original reporting, kBTC holds a market capitalization of around USD $260 million. That figure makes it a non-trivial piece of the wrapped bitcoin landscape, even if it is not the largest such token on the market.
With the migration to Chainlink CCIP, Kraken is not changing how kBTC is issued or backed. The exchange will continue to manage issuance and custody of the token, maintaining the 1:1 bitcoin reserve relationship. The modification lies in the infrastructure that moves kBTC across different chains.
This separation of roles matters: custody and backing remain squarely with Kraken, while the movement of tokens between blockchains is outsourced to Chainlink’s protocol. It is a way of unbundling the responsibilities so that a specialized interoperability provider focuses on cross-chain security, and the exchange continues to oversee reserves, issuance, and user-facing operations.
Networks involved and expansion plans for multichain support
In its communications, Kraken indicated that the migration will span several blockchains from the outset, including Ink, Ethereum, Unichain and Optimism. Those networks cover a significant share of the DeFi and layer-2 ecosystem where wrapped assets like kBTC can be actively used.
The exchange has also signaled that additional chains may be added over time, hinting at a broader multichain strategy built on top of Chainlink CCIP. For Kraken, aligning new integrations around a single interoperability standard could simplify internal processes and reduce the complexity associated with maintaining multiple bridge providers.
For users, the practical impact is that kBTC and future wrapped tokens should remain available across a growing list of networks, but their movement will be governed by a different set of security controls and risk models. In theory, having a standardized CCIP-based process may also make it easier for other protocols to integrate these assets, since they can rely on a common cross-chain framework.
Although precise timelines for every network shift have not been fully detailed, the direction of travel is clear: new wrapped offerings from Kraken are expected to launch natively under this Chainlink-based architecture, rather than being retrofitted from older designs tied to LayerZero.
Chainlink CCIP’s growing role in institutional-grade interoperability
The move by Kraken adds to a growing list of large industry players choosing Chainlink CCIP to support their cross-chain needs. In the previous year, Coinbase also selected CCIP as the exclusive bridge for roughly USD $7 billion in wrapped tokens, reinforcing the perception that Chainlink is becoming a go-to provider for institutional-scale interoperability.
For Chainlink, these decisions help solidify a narrative centered on security, standardization and conservative risk design. In an environment where a single implementation error may cost hundreds of millions of dollars, the bar for cross-chain solutions used by major custodians has risen significantly.
Interoperability is no longer viewed simply as a convenience feature that enables users to move tokens from one blockchain to another. It has turned into a critical component of risk management for exchanges, DeFi platforms, and token issuers that manage large treasuries and client funds.
At the same time, the broader cross-chain ecosystem is experiencing a phase of consolidation. After several high-profile hacks in recent years, projects are gravitating toward providers that offer tighter controls, redundant validations, and operational practices aimed specifically at high-value assets. Kraken’s announcement is a clear example of this trend playing out in real time.
This does not mean that the technical debate around interoperability architectures is settled. Different models—ranging from light-client-based bridges to externally validated messaging protocols—continue to compete, each with its own trade-offs in speed, decentralization, cost, and security. For now, though, the flow of institutional adoption appears to be favoring vendors that can demonstrate robust security practices and a track record of handling significant volumes.
Impact on LayerZero and shifting industry sentiment
Kraken’s decision, combined with the migrations by Kelp, Solv, Re and others, has obvious implications for LayerZero’s standing in the interoperability market. While LayerZero remains a widely used protocol, the recent changes suggest that some high-profile customers are reassessing whether its current configuration meets their risk requirements.
The reported movement of over USD $3 billion in TVL away from setups linked to LayerZero underlines how sensitive capital allocators have become to bridge incidents. For projects that depend on trust from institutional partners or heavily regulated entities, the perception of security can be just as important as technical features or performance metrics.
As a result, the chain of decisions triggered by the Kelp exploit is effectively redrawing the competitive map for cross-chain providers. Protocols that specialize in high-assurance designs are gaining traction, while those associated with recent failures are being pushed to revisit their assumptions, improve safeguards, or risk losing additional market share.
In that environment, Kraken’s move reads as a statement to both users and counterparties: the exchange is willing to revise core technical dependencies when it sees better-aligned options for security and operational resilience. This posture may influence how other major platforms evaluate their own infrastructure providers in the months ahead.
A strategic shift amid Kraken’s broader corporate agenda
The update to Kraken’s interoperability stack arrives at a time when its parent company, Payward, is pursuing a federal trust charter in the United States. The goal is to become a federally regulated crypto bank, a step that would give Kraken a different regulatory status and potentially broaden the services it can offer in the U.S. financial system.
When viewed together, the request for a federal charter and the decision to replace LayerZero with Chainlink CCIP point toward a broader strategy: tightening both the institutional and technological foundations of the business. For an exchange seeking more formal recognition from regulators, demonstrating rigorous control over key infrastructure components can be strategically important.
From a user’s vantage point, the cross-chain change may feel mostly invisible on a day-to-day basis. Deposits, withdrawals and transfers of kBTC across supported networks are expected to continue, albeit under different internal plumbing. The real difference lies in how risks are distributed between the exchange and its interoperability provider.
For the wider industry, however, Kraken’s choice will likely be taken as a data point in the ongoing conversation about cross-chain security standards. When large custodial platforms rewire their bridges, competitors, regulators and infrastructure developers tend to pay attention, using those moves as informal benchmarks for what is considered acceptable practice.
Ultimately, the combination of regulatory ambitions and infrastructure adjustments suggests that Kraken is aligning its operations with a more institutionally oriented future, where expectations around security, compliance, and resilience are significantly higher than in the early days of crypto trading.
All told, Kraken’s plan to phase out LayerZero in favor of Chainlink CCIP for kBTC and upcoming wrapped assets illustrates how a single exploit can accelerate structural change. In the wake of the USD $292 million Kelp attack and the subsequent migration of billions in TVL away from affected setups, cross-chain security has moved back to center stage, and major exchanges are adapting their architectures accordingly by opting for interoperability providers they deem better suited to safeguard high-value tokenized assets.
