Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Calling eth_getBlockByHash with event log transaction hash race condition #2168

Open
kev1n-peters opened this issue Mar 17, 2023 · 5 comments
Open

Calling eth_getBlockByHash with event log transaction hash race condition #2168

kev1n-peters opened this issue Mar 17, 2023 · 5 comments

Comments

@kev1n-peters
Copy link

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.
@kev1n-peters kev1n-peters mentioned this issue Mar 17, 2023
Closed
@crystalin
Copy link
Collaborator

Thank you @kev1n-peters, can you give us more information ?
Is this on a local node or in a public RPC node ?
What configuration is used ?

@kev1n-peters
Copy link
Author

A local node, version 0.30.0, happens sometimes when making the RPC call through a WebSocket.

@albertov19
Copy link
Contributor

Hey @kev1n-peters I think this PR should fix the issue -> polkadot-evm/frontier#1030

@aadam-10
Copy link

@albertov19 do you perhaps have any info on when we might expect that to be merged?

@albertov19
Copy link
Contributor

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@crystalin @aadam-10 @albertov19 @kev1n-peters