We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
the latest Erigon3 doesn't ignore null element of topic error and thus returns 0 logs while being queried from web3.js 1.x applications.
Erigon2 used to ignore this and thus returned available logs from non-null elements, would like to know if it is a golang problem
Thanks.
Example query ( for ethereum mainnet )
{"jsonrpc":"2.0","id":18,"method":"eth_getLogs","params":[{"fromBlock":"0xaf1707","toBlock":"latest","topics":["0x90ec05050aa23d54ba425e926fe646c318e85825bc400b13a46010abe86eb2f0",null,null],"address":"0x5efda50f22d34f262c29268506c5fa42cb56a1ce"}]}
The text was updated successfully, but these errors were encountered:
91c029d
JkLondon
Successfully merging a pull request may close this issue.
Hello,
the latest Erigon3 doesn't ignore null element of topic error and thus returns 0 logs while being queried from web3.js 1.x applications.
Erigon2 used to ignore this and thus returned available logs from non-null elements, would like to know if it is a golang problem
Thanks.
Example query ( for ethereum mainnet )
The text was updated successfully, but these errors were encountered: