LayerZero Pauses Parts of Infrastructure
A state-root calculation flaw in Reth and op-reth raised node synchronization risks, prompting a precautionary pause on some EVM networks.
Updated on Nov. 7, 2026 in Cybersecurity
LayerZero paused parts of its off-chain infrastructure for some EVM networks after a state-root calculation flaw in the Reth execution client and its op-reth derivative raised the risk of node synchronization failures. The precaution delayed cross-chain messages on affected routes, though those messages were not lost.
Why it matters
Unpatched nodes may stop syncing or return incorrect state proofs through the eth_getProof method, affecting networks that depend on these clients. Several OP Stack chains are among the affected networks, so the flaw reaches beyond a single application.
The fixed releases are reth v2.10.0, op-reth v2.8.1 and Base node-reth v1.5.3, following a code fix merged on Nov. 3. The number of nodes still running unpatched versions has not been reported.
The players
LayerZero
LayerZero is a cross-chain messaging protocol that enables applications to send messages and assets between blockchain networks.
Reth
Reth is an open-source Ethereum execution client written in Rust, maintained as a high-performance alternative for running Ethereum nodes.
The details
The flaw was a client correctness issue in the Reth execution client and its op-reth derivative, not a known attack. No funds had been lost at the time of disclosure, and some protocols paused deposits or cross-chain routing during the response.
Timeline
- Nov. 3: Reth merged a code fix for the state-root calculation flaw.
- Nov. 7: LayerZero paused parts of its off-chain infrastructure and the story was published.
The Tech Race
The disclosure centers on Reth, a Rust-based Ethereum execution client, and its op-reth derivative used by OP Stack chains. It shows how a single client implementation can become a shared dependency that propagates correctness risk across multiple networks.
Users of affected networks may see delayed cross-chain messages until the affected infrastructure resumes. Node operators running unpatched Reth or op-reth versions should upgrade to the fixed releases to avoid synchronization failures.
The takeaway
Operators of Ethereum and OP Stack nodes should confirm they run the fixed Reth, op-reth or node-reth release, since client-level correctness flaws can spread to every network that depends on them.
Further reading
For broader context on how software flaws create security exposure, explore our Cybersecurity coverage.
