You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling ethclient.Client.HeaderByNumber should return the correct block hash
Actual behaviour
Invalid block hash is returned when Geth version on the server is v1.10.8 and the call is made using the ethclient.Client.HeaderByNumber. The problem also happens when calling the ethclient.Client.BlockByNumber.
I've tried calling the method using the client library with versions v1.10.4, v1.10.5, v1.10.6, v1.10.7 and v1.10.8, the behavior is the same, it seems to be something related to the server response instead of something in the client.
The behaviour is the same independently of the network, we tested it in Goerli and Rinkeby
When making the jsonRPC request directly via HTTP, the hash is correct:
System information
Geth version:
1.10.8
OS & Version: Linux
Expected behaviour
When calling
ethclient.Client.HeaderByNumber
should return the correct block hashActual behaviour
Invalid block hash is returned when Geth version on the server is v1.10.8 and the call is made using the
ethclient.Client.HeaderByNumber
. The problem also happens when calling theethclient.Client.BlockByNumber
.I've tried calling the method using the client library with versions v1.10.4, v1.10.5, v1.10.6, v1.10.7 and v1.10.8, the behavior is the same, it seems to be something related to the server response instead of something in the client.
The behaviour is the same independently of the network, we tested it in
Goerli
andRinkeby
When making the
jsonRPC
request directly via HTTP, the hash is correct:output:
it also works properly via when querying via
GraphQL
:response:
Steps to reproduce the behaviour
Ref block: https://goerli.etherscan.io/block/5259636
output:
The text was updated successfully, but these errors were encountered: