-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling eth_getBlockByHash with event log transaction hash race condition #2168
Comments
Thank you @kev1n-peters, can you give us more information ? |
A local node, version 0.30.0, happens sometimes when making the RPC call through a WebSocket. |
Hey @kev1n-peters I think this PR should fix the issue -> polkadot-evm/frontier#1030 |
@albertov19 do you perhaps have any info on when we might expect that to be merged? |
@crystalin what do you think? It has not been merged upstream in Frontier so it might not make it to client v0.31.0 right? |
eth_getBlockByHash
sometimes returns"not found"
when called with the transaction hash from a smart contract event log. It's hard to reproduce consistently which leads us to believe that there might be a race condition causing it in the moonbeam node.The text was updated successfully, but these errors were encountered: