Updating suggested curation amount (#621)

* Updating suggested curation * BK's feedback
graphprotocol · Mar 25, 2024 · a5756f4 · a5756f4
1 parent 86f23f8
commit a5756f4
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/website/pages/en/cookbook/upgrading-a-subgraph.mdx b/website/pages/en/cookbook/upgrading-a-subgraph.mdx
@@ -13,7 +13,7 @@ The process of upgrading is quick and your subgraphs will forever benefit from t
 - You have already deployed a subgraph on the hosted service.
 - The subgraph is indexing a chain available on The Graph Network.
 - You have a wallet with ETH to publish your subgraph on-chain.
-- You have ~10,000 GRT to curate your subgraph so Indexers can begin indexing it.
+- You have ~3,000 GRT to curate your subgraph so Indexers can begin indexing it.
 
 ## Upgrading an Existing Subgraph to The Graph Network
 
@@ -76,7 +76,7 @@ graph deploy --studio <SUBGRAPH_SLUG>
 
 7. Publish the subgraph on The Graph's decentralized network by hitting the "Publish" button.
 
-You should curate your subgraph with GRT to ensure that it is indexed by Indexers. To save on gas costs, you can curate your subgraph in the same transaction that you publish it to the network. It is recommended to curate your subgraph with at least 10,000 GRT for high quality of service.
+You should curate your subgraph with GRT to ensure that it is indexed by Indexers. To save on gas costs, you can curate your subgraph in the same transaction that you publish it to the network. It is recommended to curate your subgraph with at least 3,000 GRT to attract 2-3 Indexers for higher quality of service.
 
 And that's it! After you are done publishing, you'll be able to view your subgraphs live on the decentralized network via [The Graph Explorer](https://thegraph.com/explorer).
 

diff --git a/website/pages/en/developing/creating-a-subgraph.mdx b/website/pages/en/developing/creating-a-subgraph.mdx
@@ -14,7 +14,7 @@ The subgraph definition consists of a few files:
 
 - `AssemblyScript Mappings`: [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) code that translates from the event data to the entities defined in your schema (e.g. `mapping.ts` in this tutorial)
 
-> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key). It is recommended that you [add signal](/network/curating/#how-to-signal) to your subgraph with at least [10,000 GRT](/network-transition-faq/#how-can-i-ensure-that-my-subgraph-will-be-picked-up-by-indexer-on-the-graph-network).
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key). It is recommended that you [add signal](/network/curating/#how-to-signal) to your subgraph with at least [3,000 GRT](/network-transition-faq/#how-can-i-ensure-that-my-subgraph-will-be-picked-up-by-indexer-on-the-graph-network).
 
 Before you go into detail about the contents of the manifest file, you need to install the [Graph CLI](https://github.com/graphprotocol/graph-cli) which you will need to build and deploy a subgraph.
 

diff --git a/website/pages/en/publishing/publishing-a-subgraph.mdx b/website/pages/en/publishing/publishing-a-subgraph.mdx
@@ -22,7 +22,7 @@ Subgraphs can be published to the decentralized network directly from the Subgra
 
 ## Curating your subgraph
 
-> It is recommended that you curate your own subgraph with 10,000 GRT to ensure that it is indexed and available for querying as soon as possible.
+> It is recommended that you curate your own subgraph with at least 3,000 GRT to ensure that it is indexed and available for querying as soon as possible.
 
 Subgraph Studio enables you to be the first to curate your subgraph by adding GRT to your subgraph's curation pool in the same transaction. When publishing your subgraph, make sure to check the button that says, "Be the first to signal on this subgraph."
 

diff --git a/website/pages/en/quick-start.mdx b/website/pages/en/quick-start.mdx
@@ -153,7 +153,7 @@ Select the network you would like to publish your subgraph to. It is recommended
 
 Before you can query your subgraph, Indexers need to begin serving queries on it. In order to streamline this process, you can curate your own subgraph using GRT.
 
-At the time of writing, it is recommended that you curate your own subgraph with 10,000 GRT to ensure that it is indexed and available for querying as soon as possible.
+At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure that it is indexed and available for querying as soon as possible.
 
 To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
 

diff --git a/website/pages/en/tokenomics.mdx b/website/pages/en/tokenomics.mdx
@@ -47,7 +47,7 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of December 2022, subgraph developers are encouraged to curate their subgraph with at least 10,000 GRT. However, this number may be impacted by network activity and community participation.
+As of December 2022, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.