Parity-ethereum: Implement EIP-1767 GraphQL API to Ethereum node data

Created on 1 Aug 2019  ·  9Comments  ·  Source: openethereum/parity-ethereum

This is a feature request.

The current JSON RPC API has shortcomings, so EIP 1767, a GraphQL interface is proposed. It's implemented and released by Geth 1.9.0 and Pantheon, and it's in progress for Trinity. Also, feel free to join the discussion on EIP 1767.

A3-stale 🍃 F8-enhancement 🎊 M4-core ⛓ M6-rpcapi 📣 P5-sometimesoon 🌲 Q7-involved 💪

Most helpful comment

I put together an almost-client-agnostic test suite. Replace init-and-run.sh with a parity-specific script and you're ready to run the tests against your implementation. Beware, some test cases have issues, they are listed in the README, but the others are fine.
You can also join the graphql.eth Slack channel if you have any questions about using it.

All 9 comments

I put together an almost-client-agnostic test suite. Replace init-and-run.sh with a parity-specific script and you're ready to run the tests against your implementation. Beware, some test cases have issues, they are listed in the README, but the others are fine.
You can also join the graphql.eth Slack channel if you have any questions about using it.

Any update on this?

blocked on graphql-rust/juniper#2

@seunlanlege I understand you're waiting for the linked GraphQL library to have an async implementation. Isn't it an option to use the library as is now, then revisit this once they'll have async?

unfortunately no, light client uses async code for fetching data from full nodes.
If i did that now, i'd have to refactor to async later.
I'd rather this work be done at once.

Yeah, it makes perfect sense. Thanks for the update.

@adria0 why was this closed? OpenEthereum not planning on implementing a GraphQL interface?

Hi @liamaharon, I hope that somebody wants to implement this, unfortunately, all current developers now are just focused on fixing blocking bugs.

Thanks for the clarification @adria0

Was this page helpful?
0 / 5 - 0 ratings