Nethermind Leaves LayerZero to Become a Chainlink Node Operator in a Widening $15 Billion Exodus

MakeCryippreferred on

• Nethermind, the firm behind Ethereum’s largest execution client, has left its role as a LayerZero verifier and joined Chainlink as a node operator securing its Cross-Chain Interoperability Protocol and Data Feeds.
• Every earlier departure in the roughly $15 billion shift from LayerZero to Chainlink, including BitGo’s $7.4 billion in wrapped bitcoin and Wyoming’s state stablecoin, involved assets leaving the network, not the operators who ran it.
• The move comes just over three months after LayerZero publicly admitted it had let its own verifier operate as the sole check on high-value transactions, an arrangement tied to Kelp DAO’s $292 million exploit.

Nethermind, the engineering firm behind roughly a third of Ethereum’s validator software, has left its role as one of LayerZero’s largest verifiers and signed on with Chainlink as a node operator, the company announced Aug. 19.

The new role puts Nethermind to work securing Chainlink’s Cross-Chain Interoperability Protocol, which handles cross-chain messaging and token transfers, and its Data Feeds service, which delivers onchain price data to DeFi protocols. Nethermind’s prior job at LayerZero was similar in kind: as a Decentralized Verifier Network operator, it checked that cross-chain messages on LayerZero were genuine before they were acted on.

“Being a node operator carries real responsibility for a network’s reliability, and that’s consistent with how we approach every engineering commitment we make,” Nethermind CEO Daniel Celeda said. “We have always made deliberate, long-term bets on the infrastructure we believe will define the next era of onchain finance, and consolidating our cross-chain operations to Chainlink CCIP reflects that conviction.”

Chainlink Labs Chief Business Officer Johann Eid called Nethermind “one of the most respected engineering firms in the industry.”

Why This Exit Doesn’t Match the Rest of the Exodus

Nethermind’s move joins a list of parties that have shifted business away from LayerZero toward Chainlink’s CCIP over the past several months, a migration that has now pledged close to $15 billion in value. But every name on that list before Nethermind, BitGo’s $7.4 billion in wrapped bitcoin, Wyoming’s state-issued stablecoin, Kraken, Mantle, Kelp DAO, Lombard, Solv Protocol and Re, was an asset holder moving funds or tokens off LayerZero’s rails.

Nethermind held no assets on LayerZero. It ran part of the security layer other people’s assets depended on. That distinction matters: an asset holder switching providers is a customer voting with its wallet. A verifier walking away from the network it helped secure is closer to an inspector resigning from the agency it audited for. No other DVN operator has left LayerZero this way so far.

From Kelp’s $292 Million Loss to LayerZero’s Own Apology

The exodus traces back to April 18, when an attacker drained 116,500 rsETH, worth about $292 million, from Kelp DAO’s LayerZero-based bridge by calling a function on LayerZero’s EndpointV2 contract. Kelp had secured that bridge with a single verifier, LayerZero Labs’ own DVN, rather than requiring multiple independent verifiers to agree before a transaction went through.

LayerZero initially said its protocol had worked as intended and pointed to Kelp’s choice of a single-verifier setup. Kelp disputed that account, saying LayerZero staff had approved the configuration over more than two years of discussions and that LayerZero’s own published integration guide defaulted to the same single-verifier setup, with no alternative configured. Kelp also said roughly 47% of active LayerZero applications, representing more than $4.5 billion in value, were running the identical configuration at the time of the attack.

On May 9, LayerZero reversed its position.

“We made a mistake by allowing our DVN to act as a 1/1 DVN for high-value transactions,” the company said, adding: “We didn’t police what our DVN was securing, which created a risk we simply didn’t see.”

The $15 Billion Migration Now Includes the People Who Ran the Verifiers

Nethermind’s announcement lands just over three months after that admission, and a day after Wyoming’s Stable Token Commission moved its own stablecoin, the Frontier Stable Token, to Chainlink following a security review, becoming the first U.S. government entity to do so. Nethermind and Chainlink have not said what specifically Nethermind’s internal review found, describing it only as “extensive.”

What Nethermind’s Own History Suggests About the Move

Nethermind’s own client software is not free of the kind of risk it now says it wants to avoid. In February, security firm Octane Security used an AI auditing tool to find a high-severity bug in Nethermind’s Ethereum client that could have caused validators to miss rewards and take penalties if exploited. Nethermind fixed it before it was used, and the Ethereum Foundation paid a $50,000 bounty for the find. Given that Nethermind’s software still underpins a large share of Ethereum’s own validator set, its new emphasis on “responsibility for a network’s reliability” reads less like marketing language and more like a lesson drawn from its own operating history, applied to the choice of which network to help secure next.