Skip to content

Commit cd4630a

Browse files
marcusreinbenfaceidalithb
authored
Subgraph quickstart updates (#851)
* quickstart updates * small edits * Update subgraphs/quick-start.mdx: Improve clarity. Referenced PR comments. * Update website/pages/en/subgraphs/quick-start.mdx Co-authored-by: Idalith <[email protected]> * Update website/pages/en/subgraphs/quick-start.mdx * Update website/pages/en/subgraphs/quick-start.mdx * Update website/pages/en/subgraphs/quick-start.mdx --------- Co-authored-by: Benoît Rouleau <[email protected]> Co-authored-by: Idalith <[email protected]>
1 parent 3b3fc9e commit cd4630a

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

website/pages/en/subgraphs/quick-start.mdx

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ The following command initializes your subgraph from an existing contract:
4949
graph init
5050
```
5151

52-
If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
52+
If your contract is verified on the respective blockscanner where it is deployed (such as [Etherscan](https://etherscan.io/)), then the ABI will automatically be created in the CLI.
5353

5454
When you initialize your subgraph, the CLI will ask you for the following information:
5555

@@ -82,11 +82,9 @@ For a detailed breakdown on how to write your subgraph, check out [Creating a Su
8282

8383
### 5. Deploy your subgraph
8484

85-
Remember, deploying is not the same as publishing.
85+
> Remember, deploying is not the same as publishing.
8686
87-
When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
88-
89-
When you publish a subgraph, you are publishing it onchain to the decentralized network.
87+
When you **deploy** a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it. A deployed subgraph's indexing is performed by the [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/), which is a single Indexer owned and operated by Edge & Node, rather than by the many decentralized Indexers in The Graph Network. A **deployed** subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes.
9088

9189
Once your subgraph is written, run the following commands:
9290

@@ -119,7 +117,13 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap
119117

120118
### 7. Publish your subgraph to The Graph Network
121119

122-
Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it.
120+
When your subgraph is ready for a production environment, you can publish it to the decentralized network. Publishing is an onchain action that does the following:
121+
122+
- It makes your subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network.
123+
- It removes rate limits and makes your subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/).
124+
- It makes your subgraph available for [Curators](/resources/roles/curating/) to curate it.
125+
126+
> The greater the amount of GRT you and others curate on your subgraph, the more Indexers will be incentivized to index your subgraph, improving the quality of service, reducing latency, and enhancing network redundancy for your subgraph.
123127
124128
#### Publishing with Subgraph Studio
125129

0 commit comments

Comments
 (0)