privacy-scaling-explorations / ideas

4 stars 2 forks source link

Run a Graph Node #10

Open sripwoud opened 1 year ago

sripwoud commented 1 year ago

Graph Node

Project Description and Details

Having the PSE run a The Graph indexing Node(s). Maybe 1 for our own internal use. Another as a public good.

Problem Statement

Several PSE projects use the graph subgraphs. Either wrote and deployed their own (semaphore, taz), or are querying already deployed subgraphs (e2e-zk-ecdsa).

Unless a deployed subgraph is "signalled" enough (costs GRT), indexers are unlikely to index it and consumers can't query it. By deciding to run an more altruistic indexer node, we could decide to index these subgraphs that don't give much rewards and that no one else is indexing.

Solution

Buy 100k GRT (staking requirement). At current price ~$16k. Setup indexer. Find out how to configure the node: I don't know myself how the node behaves and how to configure it. Does it automatically pick and index the most juicy subgraphs (that give the most rewards)? Or is it possible to hardcode the subgraphs to index, etc...

Benefits

Project Planning

TBD

Project MVP

A running the graph indexer node.

Timeline

TBD

Key Stakeholders

TBD

Nice to haves

List of nice to haves features for the project or features that would be developed after the MVP.

Tech Stack

Graph Node is an open source Rust implementation that event sources the Ethereum blockchain to deterministically update a data store that can be queried via the GraphQL endpoint.

sripwoud commented 1 year ago

@AtHeartEngineer @cedoor @wanseob @AronisAt79 @ntampakas

AtHeartEngineer commented 1 year ago

We should talk to the larger EF DevOps folks and see what they think.