Nethermind, one of the leading Ethereum client developers, has stopped operating as a verifier in the LayerZero ecosystem and is moving its cross-chain operations to Chainlink infrastructure. The decision followed an extensive internal review of the two infrastructure providers, although the company did not disclose the specific technical or operational criteria that determined the outcome.
Key fact: Nethermind has joined the Chainlink network as a node operator and strategic technology partner. The company will help secure CCIP and Data Feeds while also supporting developers and institutional participants integrating Chainlink infrastructure.
Nethermind announced the move on August 19, 2026. The company will operate nodes in the Chainlink network while continuing to provide engineering tools, infrastructure services, and technical support to developers using cross-chain solutions.
Nethermind CEO Daniel Celeda described the transition as a long-term infrastructure decision and emphasized the responsibility node operators carry for network reliability.
"Being a node operator carries real responsibility for network reliability, and that aligns with how we approach every engineering commitment we take on."
The financial terms of the agreement between Nethermind and Chainlink were not disclosed. The company also did not provide a firm deadline for completing the migration, saying only that it would publish updates as the transition progresses.
LayerZero uses so-called Decentralized Verifier Networks, or DVNs, which independently confirm the authenticity of messages transmitted between different blockchains.
Applications using LayerZero can choose which DVNs verify their messages and determine how many approvals are required before an operation can be executed on the destination chain.
Each DVN combines smart contracts with off-chain infrastructure. Once a cross-chain message is sent, the selected verifiers check its cryptographic fingerprint. Only after the required confirmations are received can the message be accepted and executed on another network.
Nethermind previously operated as one of the independent infrastructure providers available to developers under this model.
After the transition, Nethermind will participate in the operation of the Cross-Chain Interoperability Protocol, or CCIP. Chainlink describes this architecture as a system that relies on independent node operators, transaction limits, and an additional risk-monitoring mechanism.
A separate Risk Management Network monitors cross-chain activity independently from the primary message-routing nodes and can provide an additional layer of transaction verification.
Important nuance: Chainlink positions its model as a security-by-default architecture. However, Nethermind's migration alone does not prove that CCIP eliminates the technical, operational, or governance risks inherent in cross-chain infrastructure.
Nethermind's decision came several months after a major incident involving Kelp DAO, which used LayerZero to move rsETH between networks.
On April 18, attackers created a forged cross-chain message and were able to mint 116,500 unbacked rsETH worth approximately $290 million.
After minting the fraudulent tokens, a significant portion was used as collateral in Aave lending markets to borrow wrapped Ether. As a result, the damage spread beyond the bridge itself.
One of the key factors was a security configuration that relied on a single verifier.
After the attack, Kelp DAO said LayerZero had been aware of its 1-of-1 verifier configuration and had not previously considered it unsafe. The project later announced that rsETH would migrate to Chainlink.
LayerZero CEO Bryan Pellegrino rejected that interpretation. According to him, the original configuration used multiple verifiers, including LayerZero Labs and Google, but Kelp DAO later changed it to a single-verifier setup that LayerZero did not recommend for production use.
Following the incident, LayerZero said it would no longer approve messages for applications protected by only one DVN and would move affected projects toward configurations using multiple independent verifiers.
Important: Nethermind did not say that the Kelp DAO incident directly caused its migration. The company also did not claim to have identified a fundamental flaw in LayerZero's core protocol.
Nethermind is not the only major market participant to reassess its cross-chain infrastructure. During 2026, several large projects announced migrations from LayerZero to Chainlink CCIP.
In August, BitGo selected Chainlink as the exclusive cross-chain provider for Wrapped Bitcoin. At the time of the announcement, the WBTC ecosystem was valued at approximately $7.3 billion.
Following the April exploit, Kelp DAO also announced that rsETH would migrate to Chainlink. The asset represented several billion dollars in value.
Aave expanded its use of CCIP in July. Chainlink had already been used for GHO stablecoin transfers and governance messaging, after which the integration was extended to deposits, withdrawals, vault rebalancing, and asset movements across chains.
Scale: The combined value associated with publicly disclosed migrations to Chainlink has approached $15 billion.
One of the most notable transitions involved Wyoming's Frontier Stable Token, or FRNT.
On August 18, the Wyoming Stable Token Commission said it had completed its migration from LayerZero to Chainlink following an internal security review.
FRNT is issued by a U.S. public-sector entity and backed by reserves consisting of cash and short-term U.S. Treasury securities. Income generated from the reserves supports Wyoming's School Foundation Program.
The stablecoin operates across several networks, including Ethereum, Solana, Base, Arbitrum, and Avalanche.
The commission cited operational security and disclosure practices among the important evaluation criteria. Executive Director Anthony Apollo said CCIP was the only system reviewed by the state that met its security and reliability requirements across the board.
Under a multi-year agreement, Chainlink became the exclusive cross-chain infrastructure provider for FRNT, while the LayerZero bridge was decommissioned.
The full Wyoming security review was not made public, meaning the exact technical evaluation criteria remain unavailable.
LayerZero's response: The company said it respected Wyoming's decision and was assisting with the migration. Representatives also emphasized that LayerZero had strengthened its security mechanisms in recent months.
If all cross-chain messages are approved by one party, compromising that party creates a single point of failure. An attacker may then be able to sign fraudulent messages that the rest of the system accepts as legitimate.
The incident intensified debate over whether infrastructure should allow developers to select configurations that are considered too risky for production environments.
After the attack, LayerZero effectively revised its approach by refusing to support applications using only one DVN.
Main lesson: Infrastructure flexibility is useful only when developers fully understand the consequences of each setting. For systems managing billions of dollars, unsafe configuration freedom can be extremely expensive.
| Project | Direction | Approximate Scale | Period |
|---|---|---|---|
| BitGo / WBTC | Chainlink CCIP | About $7.3 billion | August 2026 |
| Kelp DAO / rsETH | Chainlink | More than $2 billion | May 2026 |
| Aave | Expanded CCIP use | Billions of dollars in assets | July 2026 |
| Wyoming / FRNT | Chainlink CCIP | Not disclosed | August 2026 |
| Nethermind | Chainlink operator | Infrastructure partnership | August 2026 |
These transitions differ in nature: some relate to specific tokens, while others involve protocol infrastructure or node-operator roles. As a result, the combined figure should not be interpreted as a simple amount of capital that physically moved from one system to another at the same time.
LayerZero remains one of the largest interoperability projects, but a series of high-profile migrations is increasing pressure on the company.
At the same time, LayerZero's architectural flexibility remains an advantage for projects that want to define their own trust model and independently choose verifier networks.
For Chainlink, Nethermind's arrival strengthens not only the technical infrastructure but also CCIP's reputation among institutional participants.
Nethermind has experience in Ethereum client development, network infrastructure, formal verification, and auditing. Its participation as a node operator increases the diversity and professional depth of the operator network.
At the same time, Chainlink is building an ecosystem in which CCIP becomes more than a message-passing mechanism. It is increasingly positioned as an infrastructure standard used by DeFi protocols, custodians, and public-sector entities.
Strategic effect: The more major infrastructure operators and asset issuers adopt the same standard, the stronger its network effect becomes. Integrations become easier, and new projects have less incentive to choose a less widely adopted alternative.
Current events highlight several principles that are becoming especially important for projects using cross-chain messaging.
The main conclusions are:
Strategic conclusion: The current shift is less about declaring a winner between LayerZero and Chainlink and more about changing market requirements. When cross-chain infrastructure is responsible for moving billions of dollars in assets, flexibility alone is no longer enough — security must be built into the architecture, verifiable, and understandable not only to developers but also to institutional operators.
For Nethermind, the Chainlink partnership represents a long-term infrastructure bet. For Chainlink, it is another sign of growing institutional demand for CCIP. For LayerZero, it creates further pressure to strengthen safe configurations and transparency.
For the industry as a whole, the developments show how rapidly the interoperability sector is maturing. Cross-chain bridges are no longer treated as secondary DeFi features. They are becoming critical infrastructure whose failure or compromise can spread consequences across multiple networks and protocols.
"The reliability of a distributed system is determined not only by how well it operates under normal conditions, but also by how predictably it behaves when individual components fail."
— A principle of fault-tolerant distributed systems design
