-
Notifications
You must be signed in to change notification settings - Fork 38
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
[BUG] Graph-node is broken on mainnet due to eth_call response incompatibility #1012
Comments
related PR We are discussing how to revert it or if we have a better solution ASAP. |
The hotfix was applied on Godwoken mainnet_v1.
curl --location 'https://v1.mainnet.godwoken.io/rpc' \
--header 'Content-Type: application/json' \
--data '{
"method": "eth_call",
"params": [
{
"gas": "0xb71b00",
"from": "0x9c023610d438dE45B8D53358DE663233Ce752F77",
"to": "0x186181e225dc1ad85a4a94164232bd261e351c33",
"data": "0x38fff2d0"
},
"0x3c3b5"
],
"jsonrpc": "2.0",
"id": 1
}'
## Result
{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"execution reverted"}} |
It is looking good so far. I managed to sync subgraph locally. It seems fixed, but I will test more. Thank you for very fast response time. |
I think we should add graph-node compatibility test into our test workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Graph node completely stops working on Godwoken Mainnet as soon as it encounters errors in eth_call. Normally it should be handled by try_call and it was working fine until latest update of Godwoken which introduced "extra" field in eth_call response in case of error.
Godwoken:
Goerli:
Example request that triggers revert:
Response:
Graph errors:
I tried using version of graph-node: 0.25, 0.27, 0.29, 0.30. All broken.
The text was updated successfully, but these errors were encountered: