Update IPFS URL --> https://ipfs.thegraph.com/ (#978)

Author: fordN

website/src/pages/ar/indexing/new-chain-integration.mdx

@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 

website/src/pages/ar/indexing/overview.mdx

@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker

website/src/pages/ar/indexing/tooling/graph-node.mdx

@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes

website/src/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx

@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>

website/src/pages/ar/subgraphs/guides/near.mdx

@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.

website/src/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx

@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 

website/src/pages/cs/indexing/new-chain-integration.mdx

@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 

website/src/pages/cs/indexing/overview.mdx

@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker

website/src/pages/cs/indexing/tooling/graph-node.mdx

@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS uzly
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Metrický server Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Začínáme s Kubernetes

website/src/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx

@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>

website/src/pages/cs/subgraphs/guides/near.mdx

@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.

website/src/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx

@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## ID nasazení
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 

website/src/pages/de/indexing/new-chain-integration.mdx

@@ -63,7 +63,7 @@ Die Konfiguration von Graph Node ist so einfach wie die Vorbereitung Ihrer lokal
 
    > Ändern Sie nicht den Namen der Env-Variable selbst. Er muss `ethereum` bleiben, auch wenn der Netzwerkname anders lautet.
 
-3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://api.thegraph.com/ipfs/
+3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://ipfs.thegraph.com
 
 ## Substreams-getriebene Subgraphen
 

website/src/pages/de/indexing/overview.mdx

@@ -131,7 +131,7 @@ Im Zentrum der Infrastruktur eines Indexierers steht der Graph Node, der die ind
 
 - **Datenendpunkt** - Bei EVM-kompatiblen Netzwerken muss der Graph Node mit einem Endpunkt verbunden sein, der eine EVM-kompatible JSON-RPC-API bereitstellt. Dabei kann es sich um einen einzelnen Client handeln oder um ein komplexeres Setup, das die Last auf mehrere Clients verteilt. Es ist wichtig, sich darüber im Klaren zu sein, dass bestimmte Subgraphen besondere Client-Fähigkeiten erfordern, wie z. B. den Archivmodus und/oder die Paritätsverfolgungs-API.
 
-- **IPFS-Knoten (Version kleiner als 5)** - Die Metadaten für die Subgraph-Bereitstellung werden im IPFS-Netzwerk gespeichert. Der Graph Node greift in erster Linie auf den IPFS-Knoten während der Bereitstellung des Subgraphen zu, um das Subgraphen-Manifest und alle verknüpften Dateien zu holen. Netzwerk-Indizierer müssen keinen eigenen IPFS-Knoten hosten, ein IPFS-Knoten für das Netzwerk wird unter https://ipfs.network.thegraph.com gehostet.
+- **IPFS-Knoten (Version kleiner als 5)** - Die Metadaten für die Subgraph-Bereitstellung werden im IPFS-Netzwerk gespeichert. Der Graph Node greift in erster Linie auf den IPFS-Knoten während der Bereitstellung des Subgraphen zu, um das Subgraphen-Manifest und alle verknüpften Dateien zu holen. Netzwerk-Indizierer müssen keinen eigenen IPFS-Knoten hosten, ein IPFS-Knoten für das Netzwerk wird unter https://ipfs.thegraph.com gehostet.
 
 - **Indexierer-Dienst** - Erledigt alle erforderlichen externen Kommunikationen mit dem Netz. Teilt Kostenmodelle und Indizierungsstatus, leitet Abfrageanfragen von Gateways an einen Graph Node weiter und verwaltet die Abfragezahlungen über Statuskanäle mit dem Gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Erste Schritte mit Docker

website/src/pages/de/indexing/tooling/graph-node.mdx

@@ -26,7 +26,7 @@ Während einige Subgraphen nur einen vollständigen Knoten benötigen, können e
 
 ### IPFS-Knoten
 
-Die Metadaten für den Einsatz von Subgraphen werden im IPFS-Netzwerk gespeichert. Der Graph Node greift während des Einsatzes von Subgraphen primär auf den IPFS-Knoten zu, um das Subgraphen-Manifest und alle verknüpften Dateien abzurufen. Netzwerkindizierer müssen keinen eigenen IPFS-Knoten hosten. Ein IPFS-Knoten für das Netzwerk wird auf https://ipfs.network.thegraph.com gehostet.
+Die Metadaten für den Einsatz von Subgraphen werden im IPFS-Netzwerk gespeichert. Der Graph Node greift während des Einsatzes von Subgraphen primär auf den IPFS-Knoten zu, um das Subgraphen-Manifest und alle verknüpften Dateien abzurufen. Netzwerkindizierer müssen keinen eigenen IPFS-Knoten hosten. Ein IPFS-Knoten für das Netzwerk wird auf https://ipfs.thegraph.com gehostet.
 
 ### Prometheus-Metrikserver
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Erste Schritte mit Kubernetes

website/src/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx

@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>

website/src/pages/de/subgraphs/guides/near.mdx

@@ -186,7 +186,7 @@ Sobald Ihr Subgraph erstellt wurde, können Sie ihn mit dem CLI-Befehl `graph de
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # erstellt einen Subgraph auf einem lokalen Graph-Knoten (bei Subgraph Studio wird dies über die Benutzeroberfläche erledigt)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # lädt die Build-Dateien auf einen angegebenen IPFS-Endpunkt hoch und stellt den Subgraphen dann auf der Grundlage des manifestierten IPFS-Hashs auf einem angegebenen Graph-Knoten bereit
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # lädt die Build-Dateien auf einen angegebenen IPFS-Endpunkt hoch und stellt den Subgraphen dann auf der Grundlage des manifestierten IPFS-Hashs auf einem angegebenen Graph-Knoten bereit
 ```
 
 Die Knotenkonfiguration hängt davon ab, wo der Subgraph eingesetzt werden soll.

website/src/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx

@@ -10,7 +10,7 @@ Hier sind einige wichtige Unterschiede zwischen den beiden IDs: ![](/img/subgrap
 
 ## Einsatz-ID
 
-Die Bereitstellungs-ID ist der IPFS-Hash der kompilierten Manifestdatei, der auf andere Dateien im IPFS statt auf relative URLs auf dem Computer verweist. Auf das kompilierte Manifest kann zum Beispiel zugegriffen werden über: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Um die Bereitstellungs-ID zu ändern, kann man einfach die Manifestdatei aktualisieren, z. B. durch Ändern des Beschreibungsfeldes, wie in der [Subgraph manifest documentation] (https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api) beschrieben.
+Die Bereitstellungs-ID ist der IPFS-Hash der kompilierten Manifestdatei, der auf andere Dateien im IPFS statt auf relative URLs auf dem Computer verweist. Auf das kompilierte Manifest kann zum Beispiel zugegriffen werden über: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Um die Bereitstellungs-ID zu ändern, kann man einfach die Manifestdatei aktualisieren, z. B. durch Ändern des Beschreibungsfeldes, wie in der [Subgraph manifest documentation] (https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api) beschrieben.
 
 Wenn Abfragen unter Verwendung der Einsatz-ID eines Subgraphen durchgeführt werden, geben wir eine Version dieses Subgraphen zur Abfrage an. Die Verwendung der Bereitstellungs-ID zur Abfrage einer bestimmten Subgraphenversion führt zu einer ausgefeilteren und robusteren Einrichtung, da die volle Kontrolle über die abgefragte Subgraphenversion besteht. Dies hat jedoch zur Folge, dass der Abfragecode jedes Mal manuell aktualisiert werden muss, wenn eine neue Version des Subgraphen veröffentlicht wird.
 

website/src/pages/en/indexing/new-chain-integration.mdx

@@ -62,7 +62,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs