A bug in Reth’s handling of trie updates caused trie tables in Reth nodes to contain incorrect information, resulting in nodes computing an incorrect state root at later blocks.
On September 1st, 10:34 PM EDT we were alerted by users in the Reth telegram channel, and on Github, that some Reth nodes had stalled with the log “mismatched block state root”.
First reports of the bug:
https://github.com/paradigmxyz/reth/issues/18205
User nodes were stalling on the following block:
23272427
0xcab98ac6afa8461e2e9f29bd155e1e22d989cdf91f49ab67293af331767dcdaa
On September 2nd, 7:47 AM EDT we identified steps for mitigating the issue, which were communicated over Twitter and Telegram, the standard communication methods for Reth support: