How to curate Subgraph: Tellor Dispute V2

A Curator’s journey in The Graph Network

I decided to share a page from my journal where I often jot down my journey as an indexer, and curator in The Graph Network.

I trust you’re familiar with the The Graph protocol and project, if not check out the appropriate links in the reference section and come back to reading the remainder of this post.

The mental model for this post is broken into 4 components — Context, Expedition, Discovery, and Reference.

Context:

As one of the curator in The Graph’s Network, we are currently going through an exercise to evaluate the currently deployed subgraph(s) for its completeness, accuracy, and complexity.

I was given give 5 subgraphs, and in this post we shall cover: Tellor Dispute V2

Expedition:

Before we dive into the details, at a macro level we look for 3 things for any given subgraph

1. The Subgraph Manifest: normally found as subgraph.yaml defines the smart contracts the subgraph indexes, identifies which events are necessary, and map the required data from those events to entities a Graph Node stores, indexes, and allows to query.
2. GraphQL Schema: is found as schema.graphql and is defined using the GraphQL interface definition language.
3. Defining Entities: is found in schema.graphql and prior to defining them, it is important to understand which DApp(s) will be using this subgraph and their specific needs, as in how they will query the data.

b

Discovery:

This Subgraph is built for the tellor protocol (a decentralised oracle network). The protocol website is here https://www.tellor.io/ and their github is here https://github.com/tellor-io

The subgraph developer goes by this github handle https://github.com/themandalore

After a lot of research, it seems the above subgraph is powering the following DApp — Tellor Dispute Center

Reference:

The Graph Website

Tellor Dispute Center Subgraph

Tellor Dispute Center DApp

Tellor Dispute Center Github