You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/pages/en/subgraphs/quick-start.mdx
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ The following command initializes your subgraph from an existing contract:
49
49
graph init
50
50
```
51
51
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.
53
53
54
54
When you initialize your subgraph, the CLI will ask you for the following information:
55
55
@@ -82,11 +82,9 @@ For a detailed breakdown on how to write your subgraph, check out [Creating a Su
82
82
83
83
### 5. Deploy your subgraph
84
84
85
-
Remember, deploying is not the same as publishing.
85
+
> Remember, deploying is not the same as publishing.
86
86
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.
90
88
91
89
Once your subgraph is written, run the following commands:
92
90
@@ -119,7 +117,13 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap
119
117
120
118
### 7. Publish your subgraph to The Graph Network
121
119
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.
0 commit comments