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
This commit is contained in:
Nick Johnson 2019-02-24 09:37:10 +13:00 committed by EIP Automerge Bot
parent 13104c6666
commit 9854104efb

View File

@ -1,7 +1,7 @@
--- ---
eip: 1767 eip: 1767
title: GraphQL interface to Ethereum node data 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 discussions-to: https://ethereum-magicians.org/t/graphql-interface-to-ethereum-node-data/2710
status: Draft status: Draft
type: Standards Track 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. 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 ## Specification
### Node API ### Node API