Alex, could you clarify more? From initial glance of it and the blog it looks like either<p>(A) We have to go through your service, which clearly isn't decentralized.<p>or<p>(B) This somehow converts GraphQL queries to Ethereum lookups, somehow, all in the client? But the article says to use your endpoint, which suggests (A).<p>Could you explain how this is decentralized at all? I ask because I run one of the most popular P2P/decentralized projects and we have a GraphQL query layer on top ( <a href="https://github.com/brysgo/graphql-gun" rel="nofollow">https://github.com/brysgo/graphql-gun</a> ) which happens all end-to-end on the peers.<p>I'd love to see more GraphQL dApp options out there, but I also want to make sure it doesn't lock people into a centralized service, when there are P2P alternatives.<p>Please let me know if I'm misunderstanding the API. If I'm not, maybe we could help you guys make it fully P2P? Cause this would be a really cool system.
Author here: we noticed consistent sources of duplicated code when designing cross-platform dApps and built Cleargraph out of necessity. We thought it would be broadly useful as a generic dApp back-end, so we polished it up and open sourced it!<p>Right now we're working on some dApp/smart contract templates that use Cleargraph, and want to know what y'all would think is useful. Maybe something along the lines of a CryptoKitties clone, a token monitor, a todo-list with staking, or a graphical transaction explorer. Open to any ideas! :)
Is there any documentation at all? I couldn't find any. The playground[1] isn't useful without the schema.<p>1. <a href="https://api.cleargraph.com/" rel="nofollow">https://api.cleargraph.com/</a>