-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
Graphql service return empty accessList's storageKeys on goerli network data where it should not #23640
Labels
Comments
jangko
changed the title
Graphql service returned empty accessList's storageKeys on goerli network data where it should not
Graphql service return empty accessList's storageKeys on goerli network data where it should not
Sep 26, 2021
Getting it:
Checking it:
I'm syncing up a goerli node now to test the graphql, beacuse the node I was using above doesn't have graphql enabled. |
holiman
added a commit
to holiman/go-ethereum
that referenced
this issue
Sep 28, 2021
fjl
pushed a commit
that referenced
this issue
Sep 28, 2021
sidhujag
pushed a commit
to syscoin/go-ethereum
that referenced
this issue
Sep 28, 2021
yongjun925
pushed a commit
to DODOEX/go-ethereum
that referenced
this issue
Dec 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using geth's graphql to fetch block header and transactions of goerli net. At block 5000628 and tx no 71, one of the storageKeys is empty, but from JSON-RPC I got non-empty storageKeys. Same thing happened on block 5000647 tx no 42.
But the strange thing is both sender and tx hash returned by graphql query are correct. And using this sender and txhash I'm able to tell that the query result is wrong.
System information
Geth
Version: 1.10.8-stable
Git Commit: 2667545
Git Commit Date: 20210824
Architecture: amd64
Go Version: go1.16.4
Operating System: windows
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
using graphql client such as altair, connect to http://127.0.0.1:8545/graphql
or using geth's built-in client http://127.0.0.1:8545/graphql/ui
then send this query:
The text was updated successfully, but these errors were encountered: