From 9854104efb3789fceb86984b7201f57f8b54ae5b Mon Sep 17 00:00:00 2001 From: Nick Johnson Date: Sun, 24 Feb 2019 09:37:10 +1300 Subject: [PATCH] Automatically merged updates to draft EIP(s) 1767 Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing --- EIPS/eip-1767.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/EIPS/eip-1767.md b/EIPS/eip-1767.md index adf9daaa..013cbd2d 100644 --- a/EIPS/eip-1767.md +++ b/EIPS/eip-1767.md @@ -1,7 +1,7 @@ --- eip: 1767 title: GraphQL interface to Ethereum node data -author: Nick Johnson (@arachnid) +author: Nick Johnson (@arachnid), Raúl Kripalani (@raulk), discussions-to: https://ethereum-magicians.org/t/graphql-interface-to-ethereum-node-data/2710 status: Draft type: Standards Track @@ -21,6 +21,10 @@ Similarly, transaction receipts in go-ethereum are stored on disk as a single bi Some of these issues could be fixed with changes to the existing JSON-RPC interface, at the cost of complicating the interface somewhat. Instead, we propose adopting a standard query language, GraphQL, which facilitates more efficient API implementations, while also increasing flexibility. +## Prior Art + +Nick Johnson and [EthQL](https://github.com/ConsenSys/ethql) independently developed a GraphQL schema for node data. Once the parties were made aware of the shared effort, they made efforts to bring their schemas into alignment. The current schema proposed in this EIP is derived primarily from the EthQL schema. + ## Specification ### Node API