Skip to content

Commit 8da33d5

Browse files
authored
Update IPFS URL --> https://ipfs.thegraph.com/ (#978)
1 parent 2ea9cb8 commit 8da33d5

File tree

132 files changed

+176
-176
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

132 files changed

+176
-176
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
6363

6464
> Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
6565
66-
3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
66+
3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
6767

6868
## Substreams-powered Subgraphs
6969

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
131131

132132
- **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.
133133

134-
- **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.
134+
- **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.
135135

136136
- **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.
137137

@@ -331,7 +331,7 @@ createdb graph-node
331331
cargo run -p graph-node --release -- \
332332
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
333333
--ethereum-rpc [NETWORK_NAME]:[URL] \
334-
--ipfs https://ipfs.network.thegraph.com
334+
--ipfs https://ipfs.thegraph.com
335335
```
336336

337337
#### Getting started using Docker

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
2626

2727
### IPFS Nodes
2828

29-
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.
29+
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.
3030

3131
### Prometheus metrics server
3232

@@ -66,7 +66,7 @@ createdb graph-node
6666
cargo run -p graph-node --release -- \
6767
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
6868
--ethereum-rpc [NETWORK_NAME]:[URL] \
69-
--ipfs https://ipfs.network.thegraph.com
69+
--ipfs https://ipfs.thegraph.com
7070
```
7171

7272
### Getting started with Kubernetes

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ USAGE
5353
5454
FLAGS
5555
-h, --help Show CLI help.
56-
-i, --ipfs=<value> [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
56+
-i, --ipfs=<value> [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
5757
--ipfs-hash=<value> IPFS hash of the subgraph manifest to deploy.
5858
--protocol-network=<option> [default: arbitrum-one] The network to use for the subgraph deployment.
5959
<options: arbitrum-one|arbitrum-sepolia>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
186186

187187
```sh
188188
$ 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)
189-
$ 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
189+
$ 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
190190
```
191191

192192
The node configuration will depend on where the Subgraph is being deployed.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
1010

1111
## Deployment ID
1212

13-
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).
13+
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).
1414

1515
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.
1616

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
6363

6464
> Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
6565
66-
3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
66+
3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
6767

6868
## Substreams-powered Subgraphs
6969

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
131131

132132
- **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.
133133

134-
- **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.
134+
- **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.
135135

136136
- **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.
137137

@@ -331,7 +331,7 @@ createdb graph-node
331331
cargo run -p graph-node --release -- \
332332
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
333333
--ethereum-rpc [NETWORK_NAME]:[URL] \
334-
--ipfs https://ipfs.network.thegraph.com
334+
--ipfs https://ipfs.thegraph.com
335335
```
336336

337337
#### Getting started using Docker

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
2626

2727
### IPFS uzly
2828

29-
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.
29+
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.
3030

3131
### Metrický server Prometheus
3232

@@ -66,7 +66,7 @@ createdb graph-node
6666
cargo run -p graph-node --release -- \
6767
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
6868
--ethereum-rpc [NETWORK_NAME]:[URL] \
69-
--ipfs https://ipfs.network.thegraph.com
69+
--ipfs https://ipfs.thegraph.com
7070
```
7171

7272
### Začínáme s Kubernetes

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ USAGE
5353
5454
FLAGS
5555
-h, --help Show CLI help.
56-
-i, --ipfs=<value> [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
56+
-i, --ipfs=<value> [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
5757
--ipfs-hash=<value> IPFS hash of the subgraph manifest to deploy.
5858
--protocol-network=<option> [default: arbitrum-one] The network to use for the subgraph deployment.
5959
<options: arbitrum-one|arbitrum-sepolia>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
186186

187187
```sh
188188
$ 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)
189-
$ 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
189+
$ 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
190190
```
191191

192192
The node configuration will depend on where the Subgraph is being deployed.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
1010

1111
## ID nasazení
1212

13-
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).
13+
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).
1414

1515
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.
1616

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Die Konfiguration von Graph Node ist so einfach wie die Vorbereitung Ihrer lokal
6363

6464
> Ändern Sie nicht den Namen der Env-Variable selbst. Er muss `ethereum` bleiben, auch wenn der Netzwerkname anders lautet.
6565
66-
3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://api.thegraph.com/ipfs/
66+
3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://ipfs.thegraph.com
6767

6868
## Substreams-getriebene Subgraphen
6969

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ Im Zentrum der Infrastruktur eines Indexierers steht der Graph Node, der die ind
131131

132132
- **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.
133133

134-
- **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.
134+
- **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.
135135

136136
- **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.
137137

@@ -331,7 +331,7 @@ createdb graph-node
331331
cargo run -p graph-node --release -- \
332332
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
333333
--ethereum-rpc [NETWORK_NAME]:[URL] \
334-
--ipfs https://ipfs.network.thegraph.com
334+
--ipfs https://ipfs.thegraph.com
335335
```
336336

337337
#### Erste Schritte mit Docker

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Während einige Subgraphen nur einen vollständigen Knoten benötigen, können e
2626

2727
### IPFS-Knoten
2828

29-
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.
29+
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.
3030

3131
### Prometheus-Metrikserver
3232

@@ -66,7 +66,7 @@ createdb graph-node
6666
cargo run -p graph-node --release -- \
6767
--postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
6868
--ethereum-rpc [NETWORK_NAME]:[URL] \
69-
--ipfs https://ipfs.network.thegraph.com
69+
--ipfs https://ipfs.thegraph.com
7070
```
7171

7272
### Erste Schritte mit Kubernetes

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ USAGE
5353
5454
FLAGS
5555
-h, --help Show CLI help.
56-
-i, --ipfs=<value> [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
56+
-i, --ipfs=<value> [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
5757
--ipfs-hash=<value> IPFS hash of the subgraph manifest to deploy.
5858
--protocol-network=<option> [default: arbitrum-one] The network to use for the subgraph deployment.
5959
<options: arbitrum-one|arbitrum-sepolia>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ Sobald Ihr Subgraph erstellt wurde, können Sie ihn mit dem CLI-Befehl `graph de
186186

187187
```sh
188188
$ 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)
189-
$ 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
189+
$ 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
190190
```
191191

192192
Die Knotenkonfiguration hängt davon ab, wo der Subgraph eingesetzt werden soll.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Hier sind einige wichtige Unterschiede zwischen den beiden IDs: ![](/img/subgrap
1010

1111
## Einsatz-ID
1212

13-
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.
13+
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.
1414

1515
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.
1616

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
6262

6363
> Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
6464
65-
3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
65+
3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
6666

6767
## Substreams-powered Subgraphs
6868

0 commit comments

Comments
 (0)