Update deploying-a-subgraph-to-hosted.mdx (#189)

Web3Slimchance · web-flow · commit 5ed8c71f5ba2 · 2022-09-05T12:10:24.000+02:00
* Update deploying-a-subgraph-to-hosted.mdx Removed Rinkeby from supported networks and added information about Ropsten, Rinkeby and Kovan being deprecated. * Update developer-faqs.mdx Changed #14 from Rinkeby to Goerli. Since many developers are migrating from Rinkeby to Goerli, I believe it is worth keeping this question. * Update creating-a-subgraph.mdx Removed Rinkeby. Call handlers are now supported on Goerli. Added a note that block handlers with a call filter depend on the Parity tracing API. * Update subgraph-studio.mdx Rinkeby -> Goerli * Update deploying-a-subgraph-to-studio.mdx The graph mainnet currently only supports subgraphs indexing (The studio allows you to create subgraphs for mainnet, rinkeby and goerli, but you are only able to deploy mainnet subgraphs to "The Graph Network" * Update hosted-service.mdx Updated and added link. * Update publishing-a-subgraph.mdx Changed from Rinkeby to Goerli * Update migrating-a-subgraph.mdx Rinkeby to Goerli
diff --git a/pages/en/cookbook/migrating-a-subgraph.mdx b/pages/en/cookbook/migrating-a-subgraph.mdx
@@ -68,7 +68,7 @@ graph codegen && graph build
 8. Publish the subgraph on The Graph's Network by hitting the "Publish" button.
 
 - Remember that publishing is an on-chain action and will require gas to be paid for in Ethereum - see an example transaction [here](https://etherscan.io/tx/0xd0c3fa0bc035703c9ba1ce40c1862559b9c5b6ea1198b3320871d535aa0de87b). Prices are roughly around 0.0425 ETH at 100 gwei.
-- Any time you need to upgrade your subgraph, you will be charged an upgrade fee. Remember, upgrading is just publishing another version of your existing subgraph on-chain. Because this incurs a cost, it is highly recommended to deploy and test your subgraph on Rinkeby before deploying to mainnet. It can, in some cases, also require some GRT if there is no signal on that subgraph. In the case there is signal/curation on that subgraph version (using auto-migrate), the taxes will be split.
+- Any time you need to upgrade your subgraph, you will be charged an upgrade fee. Remember, upgrading is just publishing another version of your existing subgraph on-chain. Because this incurs a cost, it is highly recommended to deploy and test your subgraph on Goerli before deploying to mainnet. It can, in some cases, also require some GRT if there is no signal on that subgraph. In the case there is signal/curation on that subgraph version (using auto-migrate), the taxes will be split.
 
 And that's it! After you are done publishing, you'll be able to view your subgraphs live on the network via [The Graph Explorer](https://thegraph.com/explorer).
 
@@ -78,7 +78,7 @@ Feel free to leverage the [#Curators channel](https://discord.gg/rC8rBuRtbH) on
 
 If you would like to upgrade an existing subgraph on the network, you can do this by deploying a new version of your subgraph to the Subgraph Studio using the Graph CLI.
 
-1. Make changes to your current subgraph. A good idea is to test small fixes on the Subgraph Studio by publishing to Rinkeby.
+1. Make changes to your current subgraph. A good idea is to test small fixes on the Subgraph Studio by publishing to Goerli.
 2. Deploy the following and specify the new version in the command (eg. v0.0.1, v0.0.2, etc):
 
 ```sh
diff --git a/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx b/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx
@@ -11,7 +11,6 @@ The following networks are supported in beta on the Hosted Service:
 ### Ethereum
 
 - `mainnet`
-- `rinkeby`
 - `goerli`
 - `poa-core`
 - `poa-sokol`
@@ -38,7 +37,10 @@ The following networks are supported in beta on the Hosted Service:
 - `boba`
 - `harmony`
 
-> Note that if an EVM compatible chain is not supported on the Hosted Service, you can run your own graph-node to index it.
+
+> Ropsten, Rinkeby and Kovan are being deprecated, and are no longer supported by the Hosted Service. Read more on the [Ethereum Foundation Blog](https://blog.ethereum.org/2022/06/21/testnet-deprecation). Goerli will be maintained by client developers post-merge, and is also supported by the Hosted Service. Developers who currently use Ropsten, Rinkeby or Kovan as their staging/testing environment are encouraged to migrate to Goerli.
+
+> Note that if an EVM compatible chain is not supported on the Hosted Service, you can run your own [graph-node](https://github.com/graphprotocol/graph-node) to index it.
 
 ### Near
 
diff --git a/pages/en/deploying/deploying-a-subgraph-to-studio.mdx b/pages/en/deploying/deploying-a-subgraph-to-studio.mdx
@@ -4,12 +4,11 @@ title: Deploying a Subgraph to the Subgraph Studio
 
 ## Supported Networks
 
-The Graph Network supports subgraphs indexing the following chains:
+The Graph Network supports subgraphs indexing the following chain:
 
 ### Ethereum
 
 - `mainnet`
-- `rinkeby`
 
 Deploying a Subgraph to the Subgraph Studio is quite simple. This will take you through the steps to:
 
diff --git a/pages/en/deploying/hosted-service.mdx b/pages/en/deploying/hosted-service.mdx
@@ -2,11 +2,11 @@
 title: What is the Hosted Service?
 ---
 
-> Please note, the Hosted Service will begin sunsetting in Q1 2023, but it will remain available to chains that are not supported on the decentralized network. Developers are encouraged to [migrate their subgraphs](https://thegraph.com/blog/how-to-migrate-ethereum-subgraph) as more chains are supported. Each chain will have their hosted service equivalents gradually sunset to ensure developers have enough time to migrate subgraphs to the decentralized network. Read more about the sunsetting of the Hosted Service [here](https://thegraph.com/blog/sunsetting-hosted-service).
+> Please note, the Hosted Service will begin sunsetting in Q1 2023, but it will remain available to chains that are not supported on the decentralized network. Developers are encouraged to [migrate their subgraphs](https://thegraph.com/blog/how-to-migrate-ethereum-subgraph) as more chains are supported. Each chain will have their hosted service equivalents gradually sunset to ensure developers have enough time to migrate subgraphs to the decentralized network. Read more about the sunsetting of the Hosted Service [here](https://thegraph.com/blog/sunsetting-hosted-service). 
 
 This section will walk you through deploying a subgraph to the [Hosted Service](https://thegraph.com/hosted-service/).
 
-If you don't have an account on the Hosted Service, you can sign up with your Github account. Once you authenticate, you can start creating subgraphs through the UI and deploying them from your terminal. Graph Node supports a number of Ethereum testnets (Rinkeby, Goerli) in addition to mainnet.
+If you don't have an account on the Hosted Service, you can sign up with your Github account. Once you authenticate, you can start creating subgraphs through the UI and deploying them from your terminal. The Hosted Service supports a number of evm-compatible networks, such as Polygon, Gnosis Chain, BNB Chain, Optimism and Arbitrum. For a comprehensive list see [Supported Networks](https://thegraph.com/docs/en/deploying/deploying-a-subgraph-to-hosted/)
 
 ## Create a Subgraph
 
diff --git a/pages/en/deploying/subgraph-studio.mdx b/pages/en/deploying/subgraph-studio.mdx
@@ -68,7 +68,7 @@ You’ve made it this far - congrats! Publishing your subgraph means that an IPF
 
 <VideoEmbed youtube="HfDgC2oNnwo" />
 
-Remember, while you’re going through your publishing flow, you’ll be able to push to either mainnet or Rinkeby, the testnet we support. If you’re a first-time subgraph developer, we highly suggest you start with publishing to Rinkeby, which is free to do. This will allow you to see how the subgraph will work in The Graph Explorer and will allow you to test curation elements.
+Remember, while you’re going through your publishing flow, you’ll be able to push to either mainnet or Goerli, the testnet we support. If you’re a first-time subgraph developer, we highly suggest you start with publishing to Goerli, which is free to do. This will allow you to see how the subgraph will work in The Graph Explorer and will allow you to test curation elements.
 
 You’ll only be able to index data from mainnet (even if your subgraph was published to a testnet) because only subgraphs that are indexing mainnet data can be published to the network. This is because indexers need to submit mandatory Proof of Indexing records as of a specific block hash. Because publishing a subgraph is an action taken on-chain, remember that the transaction can take up to a few minutes to go through. Any address you use to publish the contract will be the only one able to publish future versions. Choose wisely!
 
diff --git a/pages/en/developing/creating-a-subgraph.mdx b/pages/en/developing/creating-a-subgraph.mdx
@@ -710,7 +710,7 @@ While events provide an effective way to collect relevant changes to the state o
 
 Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
 
-> **Note:** Call handlers are not supported on Rinkeby, Goerli, or Ganache. Call handlers currently depend on the Parity tracing API and these networks do not support it.
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.  
 
 ### Defining a Call Handler
 
@@ -773,6 +773,8 @@ filter:
 
 _The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
 
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
 The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
 
 ```yaml
diff --git a/pages/en/developing/developer-faqs.mdx b/pages/en/developing/developer-faqs.mdx
@@ -73,9 +73,9 @@ dataSource.network()
 dataSource.address()
 ```
 
-### 14. Do you support block and call handlers on Rinkeby?
+### 14. Do you support block and call handlers on Goerli?
 
-On Rinkeby we support block handlers, but without `filter: call`. Call handlers are not supported for the time being.
+Yes. Goerli supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM network.
 
 ### 15. Can I import ethers.js or other JS libraries into my subgraph mappings?
 
diff --git a/pages/en/publishing/publishing-a-subgraph.mdx b/pages/en/publishing/publishing-a-subgraph.mdx
@@ -16,7 +16,7 @@ You can find the list of the supported networks [Here](/developing/supported-net
 
 Subgraphs can be published to the decentralized network directly from the Subgraph Studio dashboard by clicking on the **Publish** button. Once a subgraph is published, it will be available to view in the [Graph Explorer](https://thegraph.com/explorer/).
 
-- Subgraphs published to Rinkeby can index and query data from either the Rinkeby network or Ethereum Mainnet.
+- Subgraphs published to Goerli can index and query data from either the Goerli network or Ethereum Mainnet.
 
 - Subgraphs published to Ethereum Mainnet can only index and query data from Ethereum Mainnet, meaning that you cannot publish subgraphs to the main decentralized network that index and query testnet data.
 
