You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Desktop (please complete the following information):
Operating System: Ubuntu 20.04 LTC
Version: 1.28.0
Installation Method: PPA
Consensus Client: lighthouse v5.3.0
Additional context
In very rare cases, only for specific blocks, a response with an empty hash will always be returned.
This issue started occurring after upgrading from Nethermind 1.20.3 to 1.25.4 and has also been observed in version 1.28.0.
The issue happens on both mainnet and Sepolia networks.
It is rare, occurring around 1-3 times per month.
Restarting Nethermind resolves the issue, and the transaction hashes appear correctly in the response after the restart.
The text was updated successfully, but these errors were encountered:
emkjp
changed the title
Occasinal Missing Transaction Hashes in eth_getBlockByNumber
Occasional Missing Transaction Hashes in eth_getBlockByNumberSep 13, 2024
Description
When using Nethermind, the eth_getBlockByNumber RPC occasionally returns a response where the transaction hash is missing.
Steps to Reproduce
JSON RPC call:
Actual behavior
Response (with missing transaction hashes):
Expected behavior
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: