1 min read
Add as a preferred source on Google

Reth Client Bug Can Produce Wrong State Roots Across EVM Networks

The flaw affects OP Stack networks. BNB Chain says opBNB does not use op-reth and the impact on BSC-Reth is limited.

Mentioned assets
A compact network appliance sits beside a branching metal model / TokenPost.ai
A compact network appliance sits beside a branching metal model / TokenPost.ai

A correctness flaw in the Reth client affects multiple Ethereum Virtual Machine (EVM) chains, including OP Stack networks, and may cause nodes to calculate an incorrect state root.

No exploitation or loss of funds has been identified so far. The flaw is a client correctness issue: it can lead a node to produce an incorrect state root, but no attack or financial damage has been confirmed.

BNB Chain said opBNB does not use op-reth and described the effect on BSC-Reth as limited. The distinction means opBNB does not run the client named in the vulnerability, while BSC-Reth is affected to a limited extent.

The BNB Chain team is developing a hotfix and closely monitoring network security. Developers and users do not need to take action for now, BNB Chain said. The broader issue affects multiple EVM chains, while BNB Chain describes limited impact on BSC-Reth and says opBNB does not use op-reth.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…