# Base Recalculates Its State Root and Reports No User Impact

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/50884
Published: 2026-11-07T14:48:47.000Z
Updated: 2026-11-07T14:48:47.000Z
Section: Technology

> Base urged node operators to install v1.5.3. Reth maintainers rated the update high priority for payload and non-payload builders.

Base said it recomputed its state root and confirmed it was correct, and separately said users were not affected; its notice described a Reth flaw that can cause nodes to calculate incorrect roots.

Blockaid warned that unpatched Reth-based nodes may stop syncing or return incorrect state proofs through eth_getProof, a risk covered in [Blockaid’s warning about incorrect Reth state proofs](<https://www.tokenpost.com/news/technology/50637>). Several OP Stack chains were among the affected networks.

Reth’s fix entered the codebase Nov. 3. Fixed releases include Reth v2.10.0, op-reth v2.8.1 and Base v1.5.3. Base urged node operators to install v1.5.3, while Reth maintainers rated the update high priority for payload and non-payload builders. At disclosure, the issue was classified as a client-correctness flaw, with no known attack or reported fund losses.

LayerZero also paused parts of its off-chain infrastructure on some EVM networks during the response, delaying cross-chain messages on affected routes. The messages were not lost; the pause was precautionary. [LayerZero’s pause of cross-chain services after the Reth state-root bug](<https://www.tokenpost.com/news/technology/50639>) was part of the broader response.



## Links in this article

- [Blockaid’s warning about incorrect Reth state proofs](https://www.tokenpost.com/news/technology/50637)
- [LayerZero’s pause of cross-chain services after the Reth state-root bug](https://www.tokenpost.com/news/technology/50639)
