Nethermind Becomes Third Firm to Leave LayerZero for Chainlink

Cross-chain infrastructure moves assets and instructions between otherwise separate blockchains, and someone has to attest that each message is genuine. In LayerZero's design, that job falls to decentralized verifier networks (DVNs), independent operators that applications can select and require to sign off before a transaction proceeds. Nethermind ran one of the more prominent ones. It will now help operate Chainlink's rival system, the Cross-Chain Interoperability Protocol (CCIP), instead.

It is the third significant departure since April, when an attack on a LayerZero-powered bridge cost the liquid restaking protocol Kelp DAO 116,500 rsETH, its restaked ether token, worth about $292mn at the time. For anyone relying on cross-chain infrastructure to move assets, the question is whether that represents three independent commercial decisions or a market quietly repricing one provider's security.

What the company did and did not say

Nethermind said it had migrated away from its verifier operations following an "extensive review" and would contribute engineering tools and integration support alongside running nodes. It did not identify any technical problem with LayerZero, did not say the review was prompted by the Kelp attack, and did not disclose financial terms or a completion date.

The sharper characterization came from the other side of the deal. A Chainlink spokesperson told The Block the move reflected a shift by a prominent LayerZero operator towards Chainlink's "secure-by-default architecture". That is the beneficiary describing its own win, and Nethermind's own statement makes no such claim.

Three departures in four months

The pattern is what makes this more than a supplier switch. Custodian BitGo moved a key integration to Chainlink in early August, in a decision Sandmark linked at the time to lingering wariness of LayerZero after the Kelp hack. Virtuals, the AI agent platform, shifted more than $700mn of its token to CCIP after a security review of its token routes.

Nethermind is the most pointed of the three because it is not a customer choosing a supplier. It is an operator that helped run the system, and it has moved to the competitor.

Neither system eliminates the risk

Chainlink says CCIP uses independent node operators, transaction limits and a separate risk-management network to monitor activity. Those are design claims from the provider, not independent findings, and no cross-chain architecture has yet proved immune to the class of failure that hit Kelp. What has changed is not the technology's guarantees, but who the market believes.

Sandmark put its findings to LayerZero on 20 Aug, asking whether it recognized a pattern of operators and applications moving to alternative cross-chain infrastructure since April, and what changes it had made to its verifier framework since the Kelp DAO incident. It had not responded by the time of publication. This article will be updated with any comment received.