Nethermind, one of Ethereum’s largest engineering firms, has ended its role as a third-party verifier in LayerZero’s decentralized verifier network and will move its cross-chain operations to Chainlink’s cross-chain interoperability protocol, or CCIP.
The company said the decision followed an extensive internal review and represents a long-term commitment to Chainlink’s infrastructure for cross-chain messaging. Nethermind has already joined the Chainlink network as a node operator and strategic technology provider, positioning the firm to contribute to CCIP’s security operations as well as Chainlink data feeds.
The move removes Nethermind from LayerZero’s DVN system, where independent entities verify whether messages moving between blockchains are authentic and have not been altered. For applications using LayerZero’s framework, those verifiers are part of the security model governing cross-chain actions such as token transfers, contract calls, and data delivery.
Daniel Celeda, chief executive officer of Nethermind, said the company had made a long-term decision to concentrate its cross-chain work on Chainlink. Nethermind did not provide a completion date for the transition, though it said it would publish updates as migration work proceeds.
a major Ethereum engineering firm changes networks
Nethermind’s departure gives Chainlink another high-profile infrastructure participant with deep roots in Ethereum’s core technology stack. Founded in 2017, the firm develops Nethermind, one of Ethereum’s main execution clients, the software that processes transactions and executes smart contracts on the network.
Nethermind said its software supports more than 16,000 Ethereum validators and over $5 billion in delegated assets. The company also provides security work, formal verification, engineering tools, and institutional-grade blockchain infrastructure. Its stated client and ecosystem relationships include EtherFi, Gnosis, Lido, StarkWare, World, and Arbitrum.
Under the new arrangement, Nethermind said it will provide more than node operations. Its work as a Chainlink technology provider is expected to include infrastructure services, technical integration support, and engineering tools for blockchain application teams. The company also said it plans to contribute to the security of CCIP and support Chainlink data feeds, which deliver external market information to smart contracts.
That combination gives Nethermind a role spanning several layers of the Chainlink ecosystem. Running nodes concerns the validation and delivery of network services, while engineering support can help protocols integrate cross-chain messaging or price-data infrastructure into their applications.
bridge security has become a sharper competitive issue
The migration follows a period in which cross-chain security design has received renewed scrutiny after an April attack on Kelp DAO’s rsETH bridge. The incident led to the loss of 116,500 rsETH, valued at roughly $292 million at the time, from a bridge using LayerZero infrastructure.
Nethermind did not say whether that event triggered or accelerated its internal review. Its announcement also did not identify a particular technical weakness in LayerZero’s software, disclose financial terms connected to the move, or state that LayerZero’s DVN design was responsible for the Kelp DAO loss.
Those distinctions matter because cross-chain systems are assembled from several components: the messaging protocol, application-level smart contracts, verification configuration, token contracts, operational controls, and the entities responsible for signing or validating messages. A failure in one layer does not automatically establish a flaw in every other layer.
Yet the attack has added pressure to an already competitive market for cross-chain infrastructure. Protocol teams selecting a messaging system must weigh cost, transaction speed, supported networks, integration complexity, and security architecture. The number and independence of parties required to verify a cross-chain instruction can be particularly consequential, since these systems handle messages that may authorize the release or creation of tokens on another blockchain.
Chainlink’s CCIP is designed around a network approach that combines decentralized oracle operators with additional risk-management controls. LayerZero’s architecture, meanwhile, allows applications to select the verifier configuration they want to use through its DVN model. That flexibility can give developers more control over cost and trust assumptions, but it also places greater responsibility on teams to understand the settings governing their bridge or messaging pathway.
capital and volume migrate toward CCIP
Chainlink said its cross-chain infrastructure absorbed more than $7 billion in migrating token value during the second quarter of the year. It also reported that transfer volume through CCIP rose 353% to $4.90 billion during that period.
The company said CCIP currently helps secure more than $110 billion in digital assets across supported applications and networks. It also said several software teams moved more than $4 billion in managed capital onto the framework as they reassessed cross-chain security arrangements.
Those figures should be read as indicators of protocol usage and migration activity rather than as a direct measure of security. A larger amount of value using one interoperability network can reflect developer preference, established integrations, liquidity needs, or the availability of particular blockchain connections. It also raises the stakes for node operators and security systems responsible for processing messages.
Nethermind’s decision adds credibility to Chainlink’s effort to present CCIP as infrastructure suited for higher-value token transfers and institutional applications. The firm’s experience with Ethereum clients, formal verification, and production infrastructure could be especially relevant where cross-chain protocols seek stronger operational assurance rather than simply broader network coverage.
users face configuration questions, not just protocol choices
For holders of yield-bearing tokens and users of cross-chain bridges, Nethermind’s move is a reminder that the name of a messaging protocol alone does not describe the full risk profile of a transfer.
Applications can use different configurations even when built on the same underlying interoperability framework. Users considering a bridge or cross-chain vault may want to check which contracts hold assets, what verifier or oracle arrangement secures transfers, whether there are emergency controls, and how upgrades are governed. Native transfers supported directly by a blockchain’s own infrastructure can carry different assumptions from wrapped or bridge-issued versions of an asset.
Nethermind has not announced a deadline for its LayerZero withdrawal or full CCIP migration. Its decision nevertheless places one of Ethereum’s established infrastructure providers on Chainlink’s side of an increasingly consequential contest over how digital assets move between blockchains.
To deepen your understanding of oracle networks and cross-chain security, explore our guide on oracle networks today.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
