-
Notifications
You must be signed in to change notification settings - Fork 835
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
Discussion: differences in graphQL responses between Besu and Geth due to number encoding #1577
Comments
Any change to GraphQL output would involve changing the spec and the schema - https://eips.ethereum.org/EIPS/eip-1767. Our GraphQL library strongly maps the types in the schema with it's output, and any change to the output requires a change in the schema. |
Okay thank you for your response @shemnon , we are working on fixing some query responses to align better with the spec. I noticed however that we're failing to serve a couple of queries on Do you have any further insights on this? |
I had a chat with Danno: |
The hive test suite GraphQL tests found inconsistencies in the responses between the besu and geth clients in the number encoding, where Geth returns hex for certain fields as opposed to Besu which returns number/float.
I've created a gist documenting the queries for which the responses of Geth and Besu differ due to different number encoding here. (The GraphQL test logs can also be viewed on our hive test run visualizer).
Geth uses hex strings because JSON numbers are often implemented as floats, which cannot reliably represent all possible 64-bit integers. It would be nice to have a discussion about this to see if Besu wants to potentially switch to using hex as well.
cc @fjl
The text was updated successfully, but these errors were encountered: