Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add developer role to decentralized network #177

Merged
merged 15 commits into from
Sep 29, 2022
Merged
3 changes: 3 additions & 0 deletions navigation/navigation.ts
Original file line number Diff line number Diff line change
@@ -27,6 +27,9 @@ export const navigation = (locale: AppLocale): NavItemDefinition[] => [
{
slug: 'curating',
},
{
slug: 'developing',
},
{
slug: 'explorer',
},
46 changes: 46 additions & 0 deletions pages/en/network/developing.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: Developing
---

Developers are a core part of The Graph ecosystem. They are responsible for both building and querying subgraphs, unlocking data for the web3 ecosystem.

## Building Subgraphs

Developers can build subgraphs, open APIs, and deploy them locally or in the [Subgraph Studio](https://thegraph.com/studio/).

Once published and indexed to the The Graph Network, anyone can query the subgraph with [GraphQL](https://graphql.org/learn/schema-language/) and use it in their protocol or applications.
MichaelMacaulay marked this conversation as resolved.
Show resolved Hide resolved

### Curation

Subgraph developers often curate their own subgraph. This proves to Indexers that they've published a high-quality subgraph to the network and attracts additional Curators.
MichaelMacaulay marked this conversation as resolved.
Show resolved Hide resolved

Curators stake GRT with the subgraph and receive curation shares, which guarantee a percentage of future query fees. The curation signal increases as more Curators signal on the subgraph.

A strong curation signal is crucial because Indexers use the curation signal to determine which subgraphs to index to the network, making it available for querying.

### Publishing on the Network

By deploying your subgraph to The Graph Network, you're making that data available to developers and users across the web3 ecosystem. Anyone will be able to query it.
MichaelMacaulay marked this conversation as resolved.
Show resolved Hide resolved

Data from your subgraph can be used to improve user experience, build new features, or even create entirely new applications.

## Querying Subgraphs

Developers that query subgraphs serve it to users through a simple interface. They can use the GraphQL API to query data from the subgraph's processed database. Developers can manipulate, sort, or aggregate the data any way they want.
MichaelMacaulay marked this conversation as resolved.
Show resolved Hide resolved

When you query a subgraph on The Graph Network, it will be served by one of the Indexers who has chosen to index that subgraph. Queries incur query fees, which are paid in GRT. These fees are managed and deducted via a Gateway, which matches consumers and Indexers, and keeps track of consumer spending via API keys.


### How Billing Works

> IMPORTANT: When an account reaches a 0 GRT balance and the billing invoice is not paid in a timely manner, Indexers will stop serving queries for all API keys associated with the account. Indexers will automatically start serving queries again once the billing balance is paid in full and GRT is added to the account for future query fees.

Developers that query a subgraph can use GRT to pay the query fees. This fee is split between different network participants, including the Indexers, Curators, and Delegators.

Your account on [Subgraph Studio](https://thegraph.com/studio/) must have a positive balance of GRT, which will be used to pay for query fees to the network. Maintaining a positive balance for an account is the responsibility of the user or dapp.
MichaelMacaulay marked this conversation as resolved.
Show resolved Hide resolved

There are two ways to be notified of your query fee balance. The first is to set up a billing alert that will be sent to an [email address](https://thegraph.com/studio/settings/). Another way is by querying the [billing subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/billing?query=Nena%20account) API directly.

Learn how to prioritize price, speed, data freshness (among other factors) for your queries by watching this video.

<VideoEmbed src="https://www.loom.com/embed/b5fc533e48584cb694017392c80c75e0" />