From e333e5ac98bfc02384de74a5a8a95f0287dbc537 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:35 -0400 Subject: [PATCH 001/290] New translations graph-node.mdx (German) --- .../src/pages/de/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/de/indexing/tooling/graph-node.mdx b/website/src/pages/de/indexing/tooling/graph-node.mdx index 3c4cb903b165..81b54b23959c 100644 --- a/website/src/pages/de/indexing/tooling/graph-node.mdx +++ b/website/src/pages/de/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ Eine vollständige Datenbeispiel-Konfiguration für Kubernetes ist im [indexer r Wenn es ausgeführt wird, stellt Graph Node die folgenden Ports zur Verfügung: -| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP Server
(für Subgraph-Abfragen) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(für Subgraphen-Abonnements) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(zum Verwalten von Deployments) | / | \--admin-port | - | -| 8030 | Status der Indizierung von Subgraphen API | /graphql | \--index-node-port | - | -| 8040 | Prometheus-Metriken | /metrics | \--metrics-port | - | +| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | +| ---- | ------------------------------------------------ | ---------------------------------------------- | ------------------ | ----------------- | +| 8000 | GraphQL HTTP Server
(für Subgraph-Abfragen) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(für Subgraphen-Abonnements) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(zum Verwalten von Deployments) | / | \--admin-port | - | +| 8030 | Status der Indizierung von Subgraphen API | /graphql | \--index-node-port | - | +| 8040 | Prometheus-Metriken | /metrics | \--metrics-port | - | > **Wichtig**: Seien Sie vorsichtig damit, Ports öffentlich zugänglich zu machen - **Verwaltungsports** sollten unter Verschluss gehalten werden. Dies gilt auch für den Graph Node JSON-RPC Endpunkt. @@ -330,7 +330,7 @@ Datenbanktabellen, die Entitäten speichern, scheinen im Allgemeinen in zwei Var Für kontoähnliche Tabellen kann `graph-node` Abfragen generieren, die sich die Details zunutze machen, wie Postgres Daten mit einer so hohen Änderungsrate speichert, nämlich dass alle Versionen für die jüngsten Blöcke in einem kleinen Teil des Gesamtspeichers für eine solche Tabelle liegen. -Der Befehl `graphman stats show ` zeigt für jeden Entitätstyp/jede Tabelle in einem Einsatz an, wie viele unterschiedliche Entitäten und wie viele Entitätsversionen jede Tabelle enthält. Diese Daten beruhen auf Postgres-internen Schätzungen und sind daher notwendigerweise ungenau und können um eine Größenordnung abweichen. Ein `-1` in der Spalte `entities` bedeutet, dass Postgres davon ausgeht, dass alle Zeilen eine eindeutige Entität enthalten. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. Im Allgemeinen sind Tabellen, bei denen die Anzahl der unterschiedlichen Entitäten weniger als 1 % der Gesamtzahl der Zeilen/Entitätsversionen beträgt, gute Kandidaten für die kontoähnliche Optimierung. Wenn die Ausgabe von `graphman stats show` darauf hindeutet, dass eine Tabelle von dieser Optimierung profitieren könnte, führt `graphman stats show ` eine vollständige Zählung der Tabelle durch - das kann langsam sein, liefert aber ein genaues Maß für das Verhältnis von eindeutigen Entitäten zu den gesamten Entitätsversionen. From 5578f90b4d65137dc2ff7f19b6edb6e09a3a0e9d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:37 -0400 Subject: [PATCH 002/290] New translations graph-node.mdx (Portuguese) --- .../src/pages/pt/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/pt/indexing/tooling/graph-node.mdx b/website/src/pages/pt/indexing/tooling/graph-node.mdx index 3d8d68eca293..8d85735d60bf 100644 --- a/website/src/pages/pt/indexing/tooling/graph-node.mdx +++ b/website/src/pages/pt/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ Veja um exemplo completo de configuração do Kubernetes no [repositório do ind Durante a execução, o Graph Node expõe as seguintes portas: -| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | -| --- | --- | --- | --- | --- | -| 8000 | Servidor HTTP GraphQL
(para queries de subgraph) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | WS GraphQL
(para inscrições a subgraphs) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(para gerir implantações) | / | \--admin-port | - | -| 8030 | API de estado de indexação do subgraph | /graphql | \--index-node-port | - | -| 8040 | Métricas Prometheus | /metrics | \--metrics-port | - | +| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | +| ----- | ----------------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | Servidor HTTP GraphQL
(para queries de subgraph) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | WS GraphQL
(para inscrições a subgraphs) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(para gerir implantações) | / | \--admin-port | - | +| 8030 | API de estado de indexação do subgraph | /graphql | \--index-node-port | - | +| 8040 | Métricas Prometheus | /metrics | \--metrics-port | - | > **Importante**: Cuidado ao expor portas publicamente — **portas de administração** devem ser trancadas a sete chaves. Isto inclui o endpoint JSON-RPC do Graph Node. @@ -330,7 +330,7 @@ Tábuas de base de dados que armazenam entidades geralmente vêm em duas varieda Para tábuas tipo-conta, o `graph-node` pode gerar consultas que aproveitam detalhes de como o Postgres armazena dados tão frequentemente alterados — em particular, que todas as versões para blocos recentes estão numa pequena subsecção do armazenamento total para uma tábua do tipo. -O comando `graphman stats show mostra, para cada tipo/tábua de entidade em um lançamento, quantas entidades distintas e versões de entidades estão em cada tábua. Esses dados são baseados em estimativas internas do Postgres e são necessariamente imprecisos, com uma grande margem de erro. Um `-1` na coluna `entities` significa que o Postgres acredita que todas as linhas contém uma entidade distinta. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. Em geral, tábuas em que o número de entidades distintas é menos de 1% do total de linhas/versões de entidade são boas candidatas para a otimização tipo-conta. Quando o resultado do `graphman stats show` indica que uma tábua pode se beneficiar desta otimização, ativar o `graphman stats show
` fará uma contagem completa da tábua - que pode ser lenta, mas dá uma medida precisa da proporção entre entidades distintas e total de versões. From 8f0efe51e4ce8bb858d618288ff7be74dac5c71c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:38 -0400 Subject: [PATCH 003/290] New translations graph-node.mdx (Hindi) --- .../pages/hi/indexing/tooling/graph-node.mdx | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/website/src/pages/hi/indexing/tooling/graph-node.mdx b/website/src/pages/hi/indexing/tooling/graph-node.mdx index fad29c77e35e..4b6911f0c5cf 100644 --- a/website/src/pages/hi/indexing/tooling/graph-node.mdx +++ b/website/src/pages/hi/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ Kubernetes का एक पूर्ण उदाहरण कॉन्फ़ जब यह चल रहा होता है तो Graph Node following port को expose करता है: -| पोर्ट | उद्देश्य | रूट्स | आर्गुमेंट्स | पर्यावरण वेरिएबल्स | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for सबग्राफ subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | +| पोर्ट | उद्देश्य | रूट्स | आर्गुमेंट्स | पर्यावरण वेरिएबल्स | +| ----- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | ------------------ | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for सबग्राफ subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | > **प्रमुख बात**: सार्वजनिक रूप से पोर्ट्स को एक्सपोज़ करने में सावधानी बरतें - \*\*प्रशासनिक पोर्ट्स को लॉक रखना चाहिए। इसमें ग्राफ नोड JSON-RPC एंडपॉइंट भी शामिल है। @@ -225,7 +225,7 @@ provider = [ { label = "kovan", url = "http://..", features = [] } ] ### Managing Graph Node -एक चालू Graph Node (या कई Graph Nodes!) को चलाने के बाद, अगली चुनौती उन Graph Nodes पर तैनात किए गए सबग्राफ को प्रबंधित करने की होती है। ग्राफ-नोड विभिन्न टूल्स प्रदान करता है जो सबग्राफ के प्रबंधन में मदद करते हैं। +एक चालू Graph Node (या कई Graph Nodes!) को चलाने के बाद, अगली चुनौती उन Graph Nodes पर तैनात किए गए सबग्राफ को प्रबंधित करने की होती है। ग्राफ-नोड विभिन्न टूल्स प्रदान करता है जो सबग्राफ के प्रबंधन में मदद करते हैं। #### लॉगिंग @@ -245,7 +245,7 @@ Indexer रिपॉजिटरी एक [example Grafana configuration](https The graphman कमांड आधिकारिक कंटेनरों में शामिल है, और आप अपने ग्राफ-नोड कंटेनर में docker exec कमांड का उपयोग करके इसे चला सकते हैं। इसके लिए एक `config.toml` फ़ाइल की आवश्यकता होती है। -`graphman` कमांड्स का पूरा दस्तावेज़ ग्राफ नोड रिपॉजिटरी में उपलब्ध है। ग्राफ नोड `/docs` में [/docs/graphman.md](https://github.com/graphprotocol/ग्राफ-नोड/blob/master/docs/graphman.md) देखें। +`graphman` कमांड्स का पूरा दस्तावेज़ ग्राफ नोड रिपॉजिटरी में उपलब्ध है। ग्राफ नोड `/docs` में [/docs/graphman.md](https://github.com/graphprotocol/ग्राफ-नोड/blob/master/docs/graphman.md) देखें। ### Subgraph के साथ कार्य करना @@ -263,7 +263,7 @@ Indexing process के तीन अलग-अलग भाग हैं: - उपयुक्त संचालकों के साथ घटनाओं को संसाधित करना (इसमें राज्य के लिए श्रृंखला को कॉल करना और स्टोर से डेटा प्राप्त करना शामिल हो सकता है) - Resulting data को store पर लिखना -ये चरण पाइपलाइन किए गए हैं (अर्थात वे समानांतर रूप से निष्पादित किए जा सकते हैं), लेकिन वे एक-दूसरे पर निर्भर हैं। जहाँ सबग्राफ को इंडेक्स करने में धीमापन होता है, वहाँ इसकी मूल वजह विशिष्ट सबग्राफ पर निर्भर करेगी। +ये चरण पाइपलाइन किए गए हैं (अर्थात वे समानांतर रूप से निष्पादित किए जा सकते हैं), लेकिन वे एक-दूसरे पर निर्भर हैं। जहाँ सबग्राफ को इंडेक्स करने में धीमापन होता है, वहाँ इसकी मूल वजह विशिष्ट सबग्राफ पर निर्भर करेगी। Common causes of indexing slowness: @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr अकाउंट-जैसी तालिकाओं के लिए, `ग्राफ-नोड` ऐसे queries जनरेट कर सकता है जो इस विवरण का लाभ उठाते हैं कि Postgres इतनी तेज़ दर पर डेटा स्टोर करते समय इसे कैसे प्रबंधित करता है। खासतौर पर, हाल के ब्लॉक्स के सभी संस्करण ऐसी तालिका के कुल स्टोरेज के एक छोटे से हिस्से में होते हैं। -कमांड `graphman stats show प्रत्येक डिप्लॉयमेंट में मौजूद entities प्रकार/टेबल के लिए यह दिखाता है कि प्रत्येक टेबल में कितनी अलग-अलग entities और कितने entities वर्ज़न हैं। यह डेटा Postgres के आंतरिक अनुमानों पर आधारित होता है, और इसलिए यह अनिवार्य रूप से सटीक नहीं होता है और इसमें एक ऑर्डर ऑफ मैग्निट्यूड तक का अंतर हो सकता है। `entities` कॉलम में `-1` का मतलब है कि Postgres मानता है कि सभी पंक्तियां एक अलग entities को शामिल करती हैं। +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. सामान्यतः, वे तालिकाएँ जहाँ विशिष्ट entities की संख्या कुल पंक्तियों/entities संस्करणों की संख्या का 1% से कम हो, वे खाता-जैसा अनुकूलन के लिए अच्छे उम्मीदवार होती हैं। जब `graphman stats show` का आउटपुट यह दर्शाता है कि कोई तालिका इस optimization से लाभ उठा सकती है, तो `graphman stats show
` चलाने पर तालिका की पूरी गणना की जाती है - यह धीमा हो सकता है, लेकिन विशिष्ट entities और कुल entities संस्करणों के अनुपात का सटीक माप प्रदान करता है। From eddd55d7fec6c2fdbb05decc12768ec141f34603 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:39 -0400 Subject: [PATCH 004/290] New translations graph-node.mdx (Romanian) --- .../src/pages/ro/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ro/indexing/tooling/graph-node.mdx b/website/src/pages/ro/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/ro/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ro/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From b5c3f86d40cdc1e7c5791d3a51a1c8f973e59754 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:40 -0400 Subject: [PATCH 005/290] New translations graph-node.mdx (French) --- .../src/pages/fr/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/fr/indexing/tooling/graph-node.mdx b/website/src/pages/fr/indexing/tooling/graph-node.mdx index ea35e2fb9680..dbed55fcd2d6 100644 --- a/website/src/pages/fr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/fr/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ Un exemple complet de configuration Kubernetes se trouve dans le [dépôt d'Inde Lorsqu'il est en cours d'exécution, Graph Node expose les ports suivants : -| Port | Objectif | Routes | Argument CLI | Variable d'Environment | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(pour gérer les déploiements) | / | \--admin-port | - | -| 8030 | API du statut de l'indexation des subgraphs | /graphql | \--index-node-port | - | -| 8040 | Métriques Prometheus | /metrics | \--metrics-port | - | +| Port | Objectif | Routes | Argument CLI | Variable d'Environment | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | ---------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(pour gérer les déploiements) | / | \--admin-port | - | +| 8030 | API du statut de l'indexation des subgraphs | /graphql | \--index-node-port | - | +| 8040 | Métriques Prometheus | /metrics | \--metrics-port | - | > **Important** : Soyez prudent lorsque vous exposez des ports publiquement - les **ports d'administration** doivent être verrouillés. Ceci inclut l'endpoint JSON-RPC de Graph Node. @@ -330,7 +330,7 @@ Les tables de base de données qui stockent les entités semblent généralement Pour les tables de type compte, `graph-node` peut générer des requêtes qui tirent parti des détails de la façon dont Postgres stocke les données avec un taux de changement aussi élevé, à savoir que toutes les versions des blocs récents se trouvent dans une petite sous-section du stockage global d'une telle table. -La commande `graphman stats show montre, pour chaque type/table d'entité dans un déploiement, combien d'entités distinctes, et combien de versions d'entités chaque table contient. Ces données sont basées sur des estimations internes à Postgres, et sont donc nécessairement imprécises, et peuvent être erronées d'un ordre de grandeur. Un `-1` dans la colonne `entités` signifie que Postgres pense que toutes les lignes contiennent une entité distincte. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. En général, les tables où le nombre d'entités distinctes est inférieur à 1% du nombre total de versions de lignes/d'entités sont de bons candidats pour l'optimisation de type compte. Lorsque la sortie de `graphman stats show` indique qu'une table pourrait bénéficier de cette optimisation, l'exécution de `graphman stats show
` effectuera un comptage complet de la table - ce qui peut être lent, mais donne une mesure précise du ratio d'entités distinctes par rapport au nombre total de versions d'entités. From cc2d6a371ae22033f6c1227261c54caaf503429b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:42 -0400 Subject: [PATCH 006/290] New translations graph-node.mdx (Spanish) --- .../src/pages/es/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/es/indexing/tooling/graph-node.mdx b/website/src/pages/es/indexing/tooling/graph-node.mdx index 4563bd8444bb..3e87e3a58908 100644 --- a/website/src/pages/es/indexing/tooling/graph-node.mdx +++ b/website/src/pages/es/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit Cuando está funcionando, Graph Node muestra los siguientes puertos: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Las tablas de bases de datos que almacenan entidades suelen ser de dos tipos: La For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 40bbfb70111b3c4643fda0ff8faf7292dbade735 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:43 -0400 Subject: [PATCH 007/290] New translations graph-node.mdx (Arabic) --- .../src/pages/ar/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ar/indexing/tooling/graph-node.mdx b/website/src/pages/ar/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/ar/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ar/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From ce4200f23116bc1b051f3cb09889a8bf56ec9cb8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:44 -0400 Subject: [PATCH 008/290] New translations graph-node.mdx (Czech) --- .../src/pages/cs/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/cs/indexing/tooling/graph-node.mdx b/website/src/pages/cs/indexing/tooling/graph-node.mdx index 9257902fe247..b6335d705be8 100644 --- a/website/src/pages/cs/indexing/tooling/graph-node.mdx +++ b/website/src/pages/cs/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit Když je Graf Uzel spuštěn, zpřístupňuje následující ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Zdá se, že databázové tabulky, které uchovávají entity, se obecně vyskyt For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From c1ed815af665cbf4f6f370a8bf7c520bbd01af78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:45 -0400 Subject: [PATCH 009/290] New translations graph-node.mdx (Italian) --- .../src/pages/it/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/it/indexing/tooling/graph-node.mdx b/website/src/pages/it/indexing/tooling/graph-node.mdx index 32015adbd8fd..29d3066cb2ae 100644 --- a/website/src/pages/it/indexing/tooling/graph-node.mdx +++ b/website/src/pages/it/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit Quando è in funzione, Graph Node espone le seguenti porte: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Le tabelle di database che memorizzano le entità sembrano essere generalmente d For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 5eb17a4f70305ffa70f135918612fd419688c4b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:46 -0400 Subject: [PATCH 010/290] New translations graph-node.mdx (Japanese) --- .../src/pages/ja/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ja/indexing/tooling/graph-node.mdx b/website/src/pages/ja/indexing/tooling/graph-node.mdx index dfbb9aeea657..93a57db23e2e 100644 --- a/website/src/pages/ja/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ja/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit グラフノードは起動時に以下のポートを公開します。 -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Indexers can use [qlog](https://github.com/graphprotocol/qlog/) to process and s For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 5281e1c33968a45626c64b4daa71b2f6b645512c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:47 -0400 Subject: [PATCH 011/290] New translations graph-node.mdx (Korean) --- .../src/pages/ko/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ko/indexing/tooling/graph-node.mdx b/website/src/pages/ko/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/ko/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ko/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From db239f52977f7607c0216496f5197ece9d23974c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:48 -0400 Subject: [PATCH 012/290] New translations graph-node.mdx (Dutch) --- .../src/pages/nl/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/nl/indexing/tooling/graph-node.mdx b/website/src/pages/nl/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/nl/indexing/tooling/graph-node.mdx +++ b/website/src/pages/nl/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 0f9d12821032ce9fae120eeef313b961c0d8e1a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:49 -0400 Subject: [PATCH 013/290] New translations graph-node.mdx (Polish) --- .../src/pages/pl/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/pl/indexing/tooling/graph-node.mdx b/website/src/pages/pl/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/pl/indexing/tooling/graph-node.mdx +++ b/website/src/pages/pl/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From bc885bbfa5e7efd8f9d628ab20a2f11fb8ff75e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:50 -0400 Subject: [PATCH 014/290] New translations graph-node.mdx (Russian) --- .../src/pages/ru/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ru/indexing/tooling/graph-node.mdx b/website/src/pages/ru/indexing/tooling/graph-node.mdx index 27f730d64966..05fabb843b74 100644 --- a/website/src/pages/ru/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ru/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \ Во время работы Graph Node предоставляет следующие порты: -| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP-сервер
(для запросов к Субграфу) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(для подписок на Субграф) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(для управления развертываниями) | / | \--admin-port | - | -| 8030 | API статуса индексирования Субграфа | /graphql | \--index-node-port | - | -| 8040 | Метрики Prometheus | /metrics | \--metrics-port | - | +| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | +| ---- | -------------------------------------------------- | ---------------------------------------------- | ------------------ | ---------------- | +| 8000 | GraphQL HTTP-сервер
(для запросов к Субграфу) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(для подписок на Субграф) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(для управления развертываниями) | / | \--admin-port | - | +| 8030 | API статуса индексирования Субграфа | /graphql | \--index-node-port | - | +| 8040 | Метрики Prometheus | /metrics | \--metrics-port | - | > **Важно**. Будьте осторожны, открывая порты для общего доступа — **порты администрирования** должны оставаться закрытыми. Это касается конечных точек Graph Node JSON-RPC. @@ -330,7 +330,7 @@ Problematic queries most often surface in one of two ways. In some cases, users Для таблиц, подобных учетным записям, `graph-node` может генерировать запросы, в которых используются детали того, как Postgres в конечном итоге сохраняет данные с такой высокой скоростью изменения, а именно, что все версии последних блоков находятся в небольшом подразделе общего хранилища для такой таблицы. -Команда `graphman stats show ` показывает для каждого типа/таблицы объектов в развертывании, сколько различных объектов и сколько версий объектов содержит каждая таблица. Эти данные основаны на внутренних оценках Postgres и, следовательно, неточны и могут отличаться на порядок. `-1` в столбце `entities` означает, что Postgres считает, что все строки содержат отдельный объект. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. В общем, таблицы, в которых количество отдельных объектов составляет менее 1 % от общего количества версий строк/объектов, являются хорошими кандидатами на оптимизацию по аналогии с учетными записями. Если выходные данные `graphman stats show` указывают на то, что эта оптимизация может принести пользу таблице, запуск `graphman stats show
` произведёт полный расчет таблицы. Этот процесс может быть медленным, но обеспечит точную степень соотношения отдельных объектов к общему количеству версий объекта. From 82adb968ae3dfcc5066cecee9cd51b450dad91a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:51 -0400 Subject: [PATCH 015/290] New translations graph-node.mdx (Swedish) --- .../src/pages/sv/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/sv/indexing/tooling/graph-node.mdx b/website/src/pages/sv/indexing/tooling/graph-node.mdx index e3d030167389..3e624ab52527 100644 --- a/website/src/pages/sv/indexing/tooling/graph-node.mdx +++ b/website/src/pages/sv/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit När Graph Node är igång exponerar den följande portar: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Databastabeller som lagrar enheter verkar generellt komma i två varianter: 'tra For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From c7b120e70460dda8153ae5753ab04d6c5bce0408 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:52 -0400 Subject: [PATCH 016/290] New translations graph-node.mdx (Turkish) --- .../src/pages/tr/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/tr/indexing/tooling/graph-node.mdx b/website/src/pages/tr/indexing/tooling/graph-node.mdx index 5f8d0267d3e0..da782fe0afdc 100644 --- a/website/src/pages/tr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/tr/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ Kubernetes örnek yapılandırmasının bütüncül bir örneği [endeksleyici G Graph Düğümü çalışırken aşağıdaki portları açar: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Önemli**: Bağlantı noktalarını herkese açık olarak dışarıya sunarken dikkatli olun. **Yönetim portları** kilitli tutulmalıdır. Bu gereklilik Graph Düğümü JSON-RPC uç noktası için de geçerlidir. @@ -330,7 +330,7 @@ Varlıkları depolayan veritabanı tablolarının genellikle iki çeşit olduğu Hesap benzeri (account-like) tablolar, sık sık güncellenen veriler içerdiğinden, PostgreSQL bu tür değişiklikleri depolarken eski satır sürümlerini de bir süre saklar. Ancak, en yeni bloklara ait sürümler genellikle tablonun küçük bir bölümünde bulunur. `graph-node`, bu yapıyı dikkate alarak sorgular oluşturur ve böylece veriye daha verimli bir şekilde erişilmesini sağlar. -`graphman stats show komutu, bir dağıtımda her bir varlık türü/tablosu için, kaç farklı varlık olduğunu ve her tablonun kaç varlık sürümü içerdiğini gösterir. Bu veri, Postgres'in içsel tahminlerine dayalıdır ve bu nedenle zorunlu olarak kesin değildir. Ayrıca bu veri, bir büyüklük derecesi kadar hatalı olabilir. `entities` sütunundaki bir `-1` değeri, Postgres'in tüm satırların farklı bir varlık içerdiğine inandığını gösterir. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. Genel olarak, farklı varlıkların sayısının, toplam satır/varlık sürümleri sayısının %1'inden daha az olduğu tablolar, hesap benzeri optimizasyon için iyi adaylardır. `graphman stats show` çıktısı bir tablonun bu optimizasyondan faydalanabileceğini gösterdiğinde, `graphman stats show
` komutunu çalıştırmak tablonun tam bir sayımını yapacaktır. Bu sayım yavaş olabilir ama farklı varlıkların genel varlık sürümlerine oranını tam olarak ölçer. From 286333f8aef385bf5f9e12d10395e8885492459a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:53 -0400 Subject: [PATCH 017/290] New translations graph-node.mdx (Ukrainian) --- .../src/pages/uk/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/uk/indexing/tooling/graph-node.mdx b/website/src/pages/uk/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/uk/indexing/tooling/graph-node.mdx +++ b/website/src/pages/uk/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 54ed44df906988a5eee46270cbba6dadc2675885 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:55 -0400 Subject: [PATCH 018/290] New translations graph-node.mdx (Chinese Simplified) --- .../src/pages/zh/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/zh/indexing/tooling/graph-node.mdx b/website/src/pages/zh/indexing/tooling/graph-node.mdx index b151102f4324..ee1e0df027d4 100644 --- a/website/src/pages/zh/indexing/tooling/graph-node.mdx +++ b/website/src/pages/zh/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \ 当运行Graph Node时，会暴露以下端口： -| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
（用于管理部署） | / | \--admin-port | - | -| 8030 | 子图索引状态 API | /graphql | \--index-node-port | - | -| 8040 | Prometheus 指标 | /metrics | \--metrics-port | - | +| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | +| ---- | ----------------------------------------------- | ------------------------------------------------ | ------------------ | ----- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
（用于管理部署） | / | \--admin-port | - | +| 8030 | 子图索引状态 API | /graphql | \--index-node-port | - | +| 8040 | Prometheus 指标 | /metrics | \--metrics-port | - | > **重要**: 公开暴露端口时要小心 - **管理端口** 应保持锁定。 这包括下面详述的 Graph节点 JSON-RPC。 @@ -330,7 +330,7 @@ Graph节点默认缓存GraphQL查询，这可以显著减少数据库负载。 对于类似账户的表，`graph-node` 可以生成查询，利用Postgres如何以如此高的变化率存储数据的细节，即最近块的所有版本都在这样一个表的整体存储的一小部分中。 -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. 一般来说，不同实体的数量小于行/实体版本总数的1%的表是类似帐户优化的良好候选者。当`graphman统计显示`的输出表明某个表可能会从这种优化中受益时，运行`graphman统计显示
`；将执行表的完整计数-这可能很慢，但可以精确衡量不同实体与整体实体版本的比率。 From 2f7189e31f76f61eb36ada7354170ebe9be20241 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:56 -0400 Subject: [PATCH 019/290] New translations graph-node.mdx (Urdu (Pakistan)) --- .../src/pages/ur/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/ur/indexing/tooling/graph-node.mdx b/website/src/pages/ur/indexing/tooling/graph-node.mdx index ca1535e89a01..9d4206086f59 100644 --- a/website/src/pages/ur/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ur/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit جب یہ چل رہا ہوتا ہے گراف نوڈ مندرجہ ذیل پورٹس کو بے نقاب کرتا ہے: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Indexers can use [qlog](https://github.com/graphprotocol/qlog/) to process and s For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 079cee57996571b76d78026be1d8d09e94d4740f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:57 -0400 Subject: [PATCH 020/290] New translations graph-node.mdx (Vietnamese) --- .../src/pages/vi/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/vi/indexing/tooling/graph-node.mdx b/website/src/pages/vi/indexing/tooling/graph-node.mdx index edde8a157fd3..b3317ca9716f 100644 --- a/website/src/pages/vi/indexing/tooling/graph-node.mdx +++ b/website/src/pages/vi/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 198d95254266b284f138d92f60842986c0dfc001 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Sat, 5 Apr 2025 16:14:58 -0400 Subject: [PATCH 021/290] New translations graph-node.mdx (Marathi) --- .../src/pages/mr/indexing/tooling/graph-node.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/mr/indexing/tooling/graph-node.mdx b/website/src/pages/mr/indexing/tooling/graph-node.mdx index 687f1ea42338..10e682be7f67 100644 --- a/website/src/pages/mr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/mr/indexing/tooling/graph-node.mdx @@ -77,13 +77,13 @@ A complete Kubernetes example configuration can be found in the [indexer reposit When it is running Graph Node exposes the following ports: -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | > **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC endpoint. @@ -330,7 +330,7 @@ Database tables that store entities seem to generally come in two varieties: 'tr For account-like tables, `graph-node` can generate queries that take advantage of details of how Postgres ends up storing data with such a high rate of change, namely that all of the versions for recent blocks are in a small subsection of the overall storage for such a table. -The command `graphman stats show shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. +The command `graphman stats show ` shows, for each entity type/table in a deployment, how many distinct entities, and how many entity versions each table contains. That data is based on Postgres-internal estimates, and is therefore necessarily imprecise, and can be off by an order of magnitude. A `-1` in the `entities` column means that Postgres believes that all rows contain a distinct entity. In general, tables where the number of distinct entities are less than 1% of the total number of rows/entity versions are good candidates for the account-like optimization. When the output of `graphman stats show` indicates that a table might benefit from this optimization, running `graphman stats show
` will perform a full count of the table - that can be slow, but gives a precise measure of the ratio of distinct entities to overall entity versions. From 92172ece4eeaf7afda65730e6b61c6f7b4f24587 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 04:06:30 -0400 Subject: [PATCH 022/290] New translations tap.mdx (Chinese Simplified) --- website/src/pages/zh/indexing/tap.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/zh/indexing/tap.mdx b/website/src/pages/zh/indexing/tap.mdx index 8a3aa1a43d1a..c3fcfa0d27cf 100644 --- a/website/src/pages/zh/indexing/tap.mdx +++ b/website/src/pages/zh/indexing/tap.mdx @@ -11,7 +11,7 @@ GraphTally is a drop-in replacement to the Scalar payment system currently in pl - 高效处理小额支付。 - 为链上交易和成本添加一层整合。 - 允许索引人控制收款和付款，保证查询付款。 -- 支持去中心化、去信任的网关，并提高了多个发送者的`索引人服务`性能。 +- 支持去中心化、去信任的网关，并提高了多个发送人的`索引人服务`性能。 ### 详情 @@ -45,7 +45,7 @@ TAP允许发送方向接收方进行多次付款，**TAP收据**将这些付款 ### 合约 -| 合约 | Arbitrum 主网 (42161) | Arbitrum Sepolia (421614) | +| 合约 | Arbitrum 主网 (42161) | Arbitrum Sepolia (421614) | | ------------------- | -------------------------------------------- | -------------------------------------------- | | TAPVerifier | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | | AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | @@ -53,11 +53,11 @@ TAP允许发送方向接收方进行多次付款，**TAP收据**将这些付款 ### 网关 -| 组件 | Edge and Node主网(Arbitrum 主网) | Edge and Node测试网(Arbitrum Sepolia) | -| ------ | --------------------------------------------- | --------------------------------------------- | -| 发送人 | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| 签字人 | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| 聚合器 | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| 组件 | Edge and Node主网(Arbitrum 主网) | Edge and Node测试网(Arbitrum Sepolia) | +| ------- | --------------------------------------------- | --------------------------------------------- | +| 发送人 | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| 签字人 | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| 聚合器 | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### 先决条件 @@ -88,7 +88,7 @@ TAP允许发送方向接收方进行多次付款，**TAP收据**将这些付款 3. **TAP代理** - - 运行 _一个_ [TAP代理](https://github.com/graphprotocol/indexer-rs)实例。建议您使用[容器映像](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs)。 + - 运行 _一个_ [TAP代理](https://github.com/graphprotocol/indexer-rs)实例。建议您使用[容器映像](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs)。 4. **配置索引人服务和TAP代理** From 3cbb5a5f142803acf65b22f4e5c7c7a74bb79f63 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 06:15:08 -0400 Subject: [PATCH 023/290] New translations cursor.mdx (Chinese Simplified) --- website/src/pages/zh/token-api/mcp/cursor.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/zh/token-api/mcp/cursor.mdx b/website/src/pages/zh/token-api/mcp/cursor.mdx index b9295d7cb315..6a62bdddf023 100644 --- a/website/src/pages/zh/token-api/mcp/cursor.mdx +++ b/website/src/pages/zh/token-api/mcp/cursor.mdx @@ -6,7 +6,7 @@ sidebarTitle: Cursor ## 先决条件 - [Cursor](https://www.cursor.com/) installed. -- 一个来自[The Graph市场]的[JWT 代币](/token-api/quick-start) (https://thegraph.market/)。 +- 一个来自[The Graph市场](https://thegraph.market/)的[JWT 代币](/token-api/quick-start) 。 - [`npx`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) 或 [`bunx`](https://bun.sh/) 已安装并在您的路径中可用。 - `@pinax/mcp`软件包需要 Node 18+，因为它依赖于内置的`fetch()` / `Headers`，这些软件包在Node 17或更高版本中不可用。 您可能需要指定一个到最新节点版本的确切路径， 或卸载以前版本的节点以确保`@pinax/mcp`使用正确版本。 From ab3f3640da9beaacbae8be6ea043a8717ed87a67 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 17:59:15 -0400 Subject: [PATCH 024/290] New translations index.json (Chinese Simplified) --- website/src/pages/zh/index.json | 74 ++++++++++++++++----------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/website/src/pages/zh/index.json b/website/src/pages/zh/index.json index 73a3a54b8106..e82bc7f27a27 100644 --- a/website/src/pages/zh/index.json +++ b/website/src/pages/zh/index.json @@ -7,7 +7,7 @@ "cta2": "创建你的第一个子图" }, "products": { - "title": "The Graph's Products", + "title": "The Graph的产品", "description": "选择一个适合您需要的解决方案—与您的路由区块链数据交互。", "subgraphs": { "title": "子图", @@ -21,7 +21,7 @@ }, "sps": { "title": "Substreams驱动的子图", - "description": "Boost your subgraph's efficiency and scalability by using Substreams.", + "description": "使用子流提高子图的效率和可扩展性。", "cta": "设置一个Substreams驱动的子图" }, "graphNode": { @@ -37,32 +37,32 @@ }, "supportedNetworks": { "title": "支持的网络", - "details": "Network Details", - "services": "Services", + "details": "网络详情", + "services": "服务", "type": "类型", - "protocol": "Protocol", - "identifier": "Identifier", - "chainId": "Chain ID", - "nativeCurrency": "Native Currency", + "protocol": "协议", + "identifier": "标识符", + "chainId": "链id", + "nativeCurrency": "本地货币", "docs": "相关文档", - "shortName": "Short Name", + "shortName": "缩略名", "guides": "指南", - "search": "Search networks", - "showTestnets": "Show Testnets", - "loading": "Loading...", - "infoTitle": "Info", - "infoText": "Boost your developer experience by enabling The Graph's indexing network.", - "infoLink": "Integrate new network", + "search": "搜索网络", + "showTestnets": "显示测试网", + "loading": "加载...", + "infoTitle": "信息", + "infoText": "启用The Graph索引网络以提升您的开发者体验。", + "infoLink": "集成新网络", "description": { "base": "The Graph支持 {0}。要添加一个新网络， {1}", "networks": "网络", "completeThisForm": "完成此表单" }, "emptySearch": { - "title": "No networks found", - "description": "No networks match your search for \"{0}\"", - "clearSearch": "Clear search", - "showTestnets": "Show testnets" + "title": "未发现网络", + "description": "没有符合您搜索的 \"{0} \" 的网络", + "clearSearch": "清空搜索内容", + "showTestnets": "显示测试网" }, "tableHeaders": { "name": "名称", @@ -76,46 +76,46 @@ "networkGuides": { "evm": { "subgraphQuickStart": { - "title": "Subgraph quick start", - "description": "Kickstart your journey into subgraph development." + "title": "子图快速入门", + "description": "开始你的旅程进入子图开发。" }, "substreams": { "title": "子流", - "description": "Stream high-speed data for real-time indexing." + "description": "用于实时索引的流高速数据。" }, "timeseries": { - "title": "Timeseries & Aggregations", - "description": "Learn to track metrics like daily volumes or user growth." + "title": "时间序列和聚合", + "description": "学习跟踪每日量或用户增长等计量。" }, "advancedFeatures": { - "title": "Advanced subgraph features", - "description": "Leverage features like custom data sources, event handlers, and topic filters." + "title": "高级子图功能", + "description": "利用自定义数据源、事件处理器和主题过滤器等功能。" }, "billing": { "title": "计费", - "description": "Optimize costs and manage billing efficiently." + "description": "优化成本和有效管理账单。" } }, "nonEvm": { "officialDocs": { - "title": "Official Substreams docs", - "description": "Stream high-speed data for real-time indexing." + "title": "官方子流文档", + "description": "用于实时索引的流高速数据。" }, "spsIntro": { - "title": "Substreams-powered Subgraphs Intro", - "description": "Supercharge your subgraph's efficiency with Substreams." + "title": "Substreams驱动的子图的常见问题", + "description": "通过子流提高您的子图的效率。" }, "substreamsDev": { "title": "Substreams.dev", - "description": "Access tutorials, templates, and documentation to build custom data modules." + "description": "访问教程、模板和文档以建立自定义数据模块。" }, "substreamsStarter": { - "title": "Substreams starter", - "description": "Leverage this boilerplate to create your first Substreams module." + "title": "子流启动器", + "description": "利用这个锅炉板来创建您的第一个子流模块。" }, "substreamsRepo": { - "title": "Substreams repo", - "description": "Study, contribute to, or customize the core Substreams framework." + "title": "子流仓库", + "description": "研究、促进或定制核心子流框架。" } } }, @@ -164,7 +164,7 @@ }, "howToIndexSolana": { "title": "如何用子流驱动子图索引Solana", - "description": "If you're familiar with Subgraphs, discover how Substreams offer a different approach for key use cases." + "description": "如果您熟悉子图，发现子流如何为关键用途案例提供不同的方法。" } }, "time": { From aa59145ea8dc3e897f3c9b8c55bbe32546e7e407 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 17:59:16 -0400 Subject: [PATCH 025/290] New translations tap.mdx (Chinese Simplified) --- website/src/pages/zh/indexing/tap.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/src/pages/zh/indexing/tap.mdx b/website/src/pages/zh/indexing/tap.mdx index c3fcfa0d27cf..a182b1dc63ad 100644 --- a/website/src/pages/zh/indexing/tap.mdx +++ b/website/src/pages/zh/indexing/tap.mdx @@ -1,12 +1,12 @@ --- -title: GraphTally Guide +title: GraphTally 指南 --- 了解图表的新支付系统，**GraphTally** [(先前的时间线聚合协议)](https://docs.rs/tap_core/latest/tap_core/index.html)。这个系统提供了快速、高效的微交易，并最大限度地减少了信任。 ## 概述 -GraphTally is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features: +GraphTally是目前实行的Scalar支付系统的退货替代。它提供以下关键功能： - 高效处理小额支付。 - 为链上交易和成本添加一层整合。 @@ -79,7 +79,7 @@ TAP允许发送方向接收方进行多次付款，**TAP收据**将这些付款 1. **索引人代理** - 遵循[相同的过程](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components)。 - - Give the new argument `--tap-subgraph-endpoint` to activate the new GraphTally codepaths and enable redeeming of RAVs. + - 给出新的参数`--tap-subgraph-endpoint`以激活新的TAP代码路径并启用RAV的兑换。 2. **索引人服务** From e9f4f2c62dae4aa8937d59342bb67dd88593ab51 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 17:59:18 -0400 Subject: [PATCH 026/290] New translations cursor.mdx (Chinese Simplified) --- website/src/pages/zh/token-api/mcp/cursor.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/src/pages/zh/token-api/mcp/cursor.mdx b/website/src/pages/zh/token-api/mcp/cursor.mdx index 6a62bdddf023..f13c51902e49 100644 --- a/website/src/pages/zh/token-api/mcp/cursor.mdx +++ b/website/src/pages/zh/token-api/mcp/cursor.mdx @@ -1,20 +1,20 @@ --- -title: Using Cursor to Access the Token API via MCP +title: 通过 MCP 使用 Cursor 访问代币API sidebarTitle: Cursor --- ## 先决条件 -- [Cursor](https://www.cursor.com/) installed. +- [Cursor](https://www.cursor.com/) 已安装。 - 一个来自[The Graph市场](https://thegraph.market/)的[JWT 代币](/token-api/quick-start) 。 - [`npx`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) 或 [`bunx`](https://bun.sh/) 已安装并在您的路径中可用。 - `@pinax/mcp`软件包需要 Node 18+，因为它依赖于内置的`fetch()` / `Headers`，这些软件包在Node 17或更高版本中不可用。 您可能需要指定一个到最新节点版本的确切路径， 或卸载以前版本的节点以确保`@pinax/mcp`使用正确版本。 -![Screenshot of Cursor's MCP configuration panel.](/img/cursor-preview-token-api.png) +![Cursor的 MCP 配置面板的屏幕截图。](/img/cursor-preview-token-api.png) ## 配置 -Create or edit your `~/.cursor/mcp.json` file. +创建或编辑您的`~/.cursor/mcp.json`文件。 > **Cursor Settings** > **MCP** > **Add new global MCP Server** From 364d3ff1725a6330bdda0e19ae7500c57629d3d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 17:59:19 -0400 Subject: [PATCH 027/290] New translations faq.mdx (Chinese Simplified) --- website/src/pages/zh/token-api/faq.mdx | 106 ++++++++++++------------- 1 file changed, 53 insertions(+), 53 deletions(-) diff --git a/website/src/pages/zh/token-api/faq.mdx b/website/src/pages/zh/token-api/faq.mdx index 99e1466c9952..dae4068e2aaa 100644 --- a/website/src/pages/zh/token-api/faq.mdx +++ b/website/src/pages/zh/token-api/faq.mdx @@ -1,109 +1,109 @@ --- -title: Token API FAQ +title: 代币 API 常见问题 --- -Get fast answers to easily integrate and scale with The Graph's high-performance Token API. +获取快速答案以便轻松地与The Graph的高性能代币API进行整合和缩放。 ## 通用 -### What blockchains does the Token API support? +### 代币 API 支持什么区块链？ -Currently, the Token API supports Ethereum, Binance Smart Chain (BSC), Polygon, Optimism, Base, and Arbitrum One. +目前，代币API支持Etherum, Binance Smart Chain(BSC), Polygon, Optimism, Base, and Arbitrum One。 -### Why isn't my API key from The Graph Market working? +### 为什么我的 API 密钥无法从The Graph市场运行？ -Be sure to use the Access Token generated from the API key, not the API key itself. An access token can be generated from the dashboard on The Graph Market using the dropdown menu next to each API key. +请务必使用 API 密钥生成的 Access Token ，而不是 API 密钥本身。 在每个API密钥旁边的下拉菜单可以从The Graph市场上的控制板生成访问代币。 -### How current is the data provided by the API relative to the blockchain? +### API提供的数据相对于区块链的最新程度如何？ -The API provides data up to the latest finalized block. +API提供最新最终块的数据。 -### How do I authenticate requests to the Token API? +### 如何验证对代币API的请求？ -Authentication is managed via JWT tokens obtained through The Graph Market. JWT tokens issued by [Pinax](https://pinax.network/en), a core developer of The Graph, are also supported. +身份验证是通过 JWT 代币通过The Graph市场获得的。 由 [Pinax](https://pinax.network/en)发布的 JWT代币，The Graph的核心开发者也获得了支持。 -### Does the Token API provide a client SDK? +### Token API 提供客户端SDK吗？ -While a client SDK is not currently available, please share feedback on any SDKs or integrations you would like to see on [Discord](https://discord.gg/graphprotocol). +虽然客户端SDK目前不可用。 请分享您想要在 [Discord](https://discord.gg/graphprotocol)上看到的 SDK 或集成的反馈。 -### Are there plans to support additional blockchains in the future? +### 未来是否有计划支持更多的区块链？ -Yes, more blockchains will be supported in the future. Please share feedback on desired chains on [Discord](https://discord.gg/graphprotocol). +是的，将来会支持更多的区块链。请分享关于在[Discord](https://discord.gg/graphprotocol)上所需的的反馈。 -### Are there plans to offer data closer to the chain head? +### 是否有计划提供更接近链头的数据？ -Yes, improvements to provide data closer to the chain head are planned. Feedback is welcome on [Discord](https://discord.gg/graphprotocol). +是的，正在计划进行改进以提供更接近链头的数据。欢迎反馈到 [Discord](https://discord.gg/graphprotocol)。 -### Are there plans to support additional use cases such as NFTs? +### 是否计划支持诸如NFT等其他用途案例？ -The Graph ecosystem is actively determining the [roadmap](https://thegraph.com/blog/token-api-the-graph/) for additional use cases, including NFTs. Please provide feedback on specific features you would like prioritized on [Discord](https://discord.gg/graphprotocol). +The Graph生态系统正在积极确定包括NFT在内的额外使用案例的 [roadmap](https://thegraph.com/blog/token-api-the-graph/)。 请提供您想要在 [Discord](https://discord.gg/graphprotocol)上优先级的特定功能的反馈。 -## MCP / LLM / AI Topics +## MCP / LLM / AI 主题 -### Is there a time limit for LLM queries? +### LLM查询是否有时限？ -Yes. The maximum time limit for LLM queries is 10 seconds. +是的。LLM查询的最大时间限制为10秒。 -### Is there a known list of LLMs that work with the API? +### 是否有已知的与API共用的 LLM清单？ -Yes, Cline, Cursor, and Claude Desktop integrate successfully with The Graph's Token API + MCP server. +是的，Cline，Cursor，Claude Desktop 已成功整合到 The Graph 的Token API + MCP 服务器。 -Beyond that, whether an LLM "works" depends on whether it supports the MCP protocol directly (or has a compatible plugin/adapter). +除此之外，LLM “工作”是否取决于它是否直接支持 MCP 协议(或拥有兼容的插件/适配器)。 -### Where can I find the MCP client? +### 我在哪里可以找到MCP客户端？ -You can find the code for the MCP client in [The Graph's repo](https://github.com/graphprotocol/mcp-client). +您可以在 [The Graph的仓库](https://github.com/graphprotocol/mcp-client) 中找到MCP客户端的代码。 -## Advanced Topics +## 高级主题 -### I'm getting 403/401 errors. What's wrong? +### 我有403/401错误。是怎么回事？ -Check that you included the `Authorization: Bearer ` header with the correct, non-expired token. Common issues include using the API key instead of generating a new JWT, forgetting the "Bearer" prefix, using an incorrect token, or omitting the header entirely. Ensure you copied the JWT exactly as provided by The Graph Market. +检查您是否包含了 `Authorization: Bearer ` 页眉和正确且未过期的代币。 常见问题包括使用 API 密钥而不是生成一个新的 JWT， 忘记“Bearer”前缀，使用不正确的代币，或完全省略标题。 请确保您复制JWT，正好像The Graph市场提供的。 -### Are there rate limits or usage costs?\*\* +### 是否有费率限制或使用成本？\*\* -During Beta, the Token API is free for authorized developers. While specific rate limits aren't documented, reasonable throttling exists to prevent abuse. High request volumes may trigger HTTP 429 errors. Monitor official announcements for future pricing changes after Beta. +Beta期间，Token API 对授权的开发者是免费的。虽然特定的费率限制没有记录，但存在着合理的节奏来防止滥用。 高请求卷可能会触发HTTP 429 错误。请监视官方公告，以了解Beta以后未来的定价变化。 -### What networks are supported, and how do I specify them? +### 支持哪些网络，以及我如何指定这些网络？ -You can query available networks with [this link](https://token-api.thegraph.com/#tag/monitoring/GET/networks). A full list of network IDs accepted by The Graph can be found on [The Graph's Networks](https://thegraph.com/docs/en/supported-networks/). The API supports Ethereum mainnet, Binance Smart Chain, Base, Arbitrum One, Optimism, and Polygon/Matic. Use the optional `network_id` parameter (e.g., `mainnet`, `bsc`, `base`, `arbitrum-one`, `optimism`, `matic`) to target a specific chain. Without this parameter, the API defaults to Ethereum mainnet. +您可以通过 [此链接](https://token-api.thegraph.com/#tag/monitoring/GET/networks)查询可用网络。 完整的网络ID列表被该图接受，可在 [The Graph的网络](https://thegraph.com/docs/en/supported-networks/)上找到。 API支持Ethereum 主机、 Binance Smart Chain、 Base 、 Arbitrum One 、 Optimism 和 Polygon/Matic 。 使用可选的 `net_id` 参数(如：`mainnet`、`bsc`、`base`、`arbitrum-one`、`optim`) 来针对特定的链。 没有此参数，API默认为Ethereum 主网。 -### Why do I only see 10 results? How can I get more data? +### 为什么我只看到10个结果？我怎么能够获得更多的数据？ -Endpoints cap output at 10 items by default. Use pagination parameters: `limit` (up to 500) and `page` (1-indexed). For example, set `limit=50` to get 50 results, and increment `page` for subsequent batches (e.g., `page=2` for items 51-100). +默认情况下，终点上限输出为10个项目。使用分页参数：`limit` (最多500个)和`page` (1-index)。 例如，设置`limit=50` 以获得50个结果，并为以后的批次增加`page` (例如项目51-100的`page=2`)。 -### How do I fetch older transfer history? +### 如何获取较早的转账历史？ -The Transfers endpoint defaults to 30 days of history. To retrieve older events, increase the `age` parameter up to 180 days maximum (e.g., `age=180` for 6 months of transfers). Transfers older than 180 days cannot be fetched in a single call. +传输端点默认为30天历史记录。要检索更早的事件，请最多增加180天的`年龄`参数(如，`age=180`可以调用六个月转账记录)。超过180 天的转账记录不能在一次调用中获取。 -### What does an empty `"data": []` array mean? +### 空的`数据'：[]`数组是什么意思？ -An empty data array means no records were found matching the query – not an error. This occurs when querying wallets with no tokens/transfers or token contracts with no holders. Verify you've used the correct address and parameters. An invalid address format will trigger a 4xx error. +空数据组意味着没有找到匹配查询的记录——不是错误。 当查询钱包时没有任何代币/转账或与没有持有人的代币合约时发生。 验证您使用了正确的地址和参数。无效的地址格式将触发一个 4xx 错误。 -### Why is the JSON response wrapped in a `"data"` array? +### 为什么JSON响应被包装在一个“data”数组中？ -All Token API responses consistently wrap results in a top-level `data` array, even for single items. This uniform design handles the common case where addresses have multiple balances or transfers. When parsing, be sure to index into the `data` array (e.g., `const results = response.data`). +所有 Token API 响应始终都会在顶级`data`数组中产生结果，即使是单个项目。 这种统一设计，处理地址有多个余额或传输的常见情况。 解析时，肯定要索引到 `data` 数组(例如`const results = response.data`)。 -### Why are token amounts returned as strings? +### 为什么作为字符串退回代币数量？ -Large numeric values (like token amounts or supplies) are returned as strings to avoid precision loss, as they often exceed JavaScript's safe integer range. Convert these to big number types for arithmetic operations. Fields like `decimals` are provided as normal numbers to help derive human-readable values. +作为字符串返回大的数值(例如代币数量或供应品)，以避免精度损失，因为它们常常超过JavaScript的安全整数范围。 将这些类型转换为大型算术操作。像`十进制`这样的字段作为正常数字提供，以帮助得出可读值。 -### What format should addresses be in? +### 地址应该包含什么格式？ -The API accepts 40-character hex addresses with or without the `0x` prefix. The endpoint is case-insensitive, so both lower and uppercase hex characters work. Ensure addresses are exactly 40 hex digits (20 bytes) if you remove the prefix. For contract queries, use the token's contract address; for balance/transfer queries, use the wallet address. +API 接受带有或不带`0x`前缀的40个字符十六进制地址。端点是大小写不敏感的，所以下级和上级十六进制字符都可以工作。 如果您删除前缀，请确保地址正好是40个十六进制数字(20个字节)。 对于合约查询，使用代币的合约地址；对于余额/转账查询，请使用钱包地址。 -### Do I need special headers besides authentication? +### 除了身份验证外，我是否需要特殊的块头？ -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +虽然建议使用`Accept:application/json`，但这并不是严格要求的，因为API默认返回json。关键标头是`Authorization：Bearer`。确保你对正确的URL发出GET请求，没有尾随斜线或路径拼写错误（例如，使用`/bances/evm/{address}`而不是`/bancel`）。 -### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? +### MCP 集成与 Claude/Cline/Cursor 显示了诸如"ENOENT" 或 "服务器断开连接"等错误。我如何解决这个问题？ -For "ENOENT" errors, ensure Node.js 18+ is installed and the path to `npx`/`bunx` is correct (consider using full paths in config). "Server disconnected" usually indicates authentication or connectivity issues – verify your `ACCESS_TOKEN` is set correctly and your network allows access to `https://token-api.thegraph.com/sse`. +关于“ENOENT”错误，请确保Node.js 18+ 已安装，并且`npx`/`bunx` 的路径是正确的(请考虑使用配置中的全部路径)。 "服务器断开连接"通常表示身份验证或连接问题——验证您的`ACCESS_TOKEN`设置正确，您的网络允许访问 `https://token-api.thegraph.com/sse`。 -### Is the Token API part of The Graph's GraphQL service? +### Token API 是否是The Graph的 GraphQL 服务的一部分？ -No, the Token API is a separate RESTful service. Unlike traditional subgraphs, it provides ready-to-use REST endpoints (HTTP GET) for common token data. You don't need to write GraphQL queries or deploy subgraphs. Under the hood, it uses The Graph's infrastructure and MCP with AI for enrichment, but you simply interact with REST endpoints. +不，Token API 是一个单独的RESTify服务。 不同于传统子图，它提供现成的REST 端点(HTTP GET) 以获取通用代币数据。 您无需写入 GraphQL 查询或部署子图。 在这个场景下，它使用 The Graph的基础设施和MCP 与 AI 进行丰富，但你只是与REST 端点交互。 -### Do I need to use MCP or tools like Claude, Cline, or Cursor? +### 我是否需要使用 MCP 或工具，如Claude、Cline或Cursor？ -No, these are optional. MCP is an advanced feature allowing AI assistants to interface with the API via streaming. For standard usage, simply call the REST endpoints with any HTTP client using your JWT. Claude Desktop, Cline bot, and Cursor IDE integrations are provided for convenience but aren't required. +不，它们是可选的。MCP 是一个高级功能，允许AI 助手通过子流与 API 接口。 对于标准用法，只需使用您的JWT来调用 REST 端点和任意HTTP客户端。 为方便起见，提供了Claude Desktop、Cline bot 和光标IDE集成，但不需要。 From 3158d000bb127a5cda05fbd2f69131b84ec2c563 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 7 Apr 2025 17:59:21 -0400 Subject: [PATCH 028/290] New translations subgraph-composition.mdx (Chinese Simplified) --- .../subgraphs/guides/subgraph-composition.mdx | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx index 7fbb93375ad8..8b6eca6cfc16 100644 --- a/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx @@ -5,11 +5,11 @@ sidebarTitle: 用多个子图生成可编译子图 利用子图构成来加快开发时间。创建基础子图，带有基本数据，然后在它上方构建附加子图。 -Optimize your Subgraph by merging data from independent, source Subgraphs into a single composable Subgraph to enhance data aggregation. +通过将三个独立的源子图数据合并成一个单一的可合成子图来优化您的子图，以加强数据集成。 ## 介绍 -Composable Subgraphs enable you to combine multiple Subgraphs' data sources into a new Subgraph, facilitating faster and more flexible Subgraph development. Subgraph composition empowers you to create and maintain smaller, focused Subgraphs that collectively form a larger, interconnected dataset. +合成子图使您能够将多个子图数据源合并为一个新子图，方便更快和更灵活的开发子图。 子图的合成增强了创建和保持较小的、重点突出的子图的能力，这些子图集合在一起形成了一个更大的、相互关联的数据集。 ### 合成的好处 @@ -37,28 +37,28 @@ Composable Subgraphs enable you to combine multiple Subgraphs' data sources into ## 先决条件 -### Source Subgraphs +### 源子图 -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) -- See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- 所有子图都需要发布一个 **specversion 1.3.0 或更高版本** (使用最新的 graph-cli 版本才能部署可合成的子图) +- 见此注释：https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 +- 仅限不可变实体：所有子图都必须有[不可变实体](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) 当布置子图时 +- 打印可以在源子图中使用，但只有不可变的实体可以在源子图顶部组成 +- 源子图不能在现有实体顶部使用图形 +- 合成实体可用于组成，但由聚合实体组成的实体不能直接进行额外聚合 -### Composed Subgraphs +### 合成子图 -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- 您只能创建合成 \*_最多5 个源子图_ +- 合成子图只能使用 **来自同一链的数据源** +- **嵌套的合成尚不支持**：此时不允许在另一个合成子图上面撰写 +- 聚合实体可用于合成，但其合成实体也不能直接使用聚合 +- 开发者无法使用子图数据源创建在线数据源 (例如，您不能在合成子图中做正常的事件处理器，以及调用处理器和区块处理器) -Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs +此外，您还可以探索 [示例-合成-子图](https://github.com/graphprotocol/example-composable-subgraph) 存储库，用于可编译子图的工作实现。 ## 开始 -The following guide provides examples for defining 3 source Subgraphs to create one powerful composed Subgraph. +以下指南提供了用于定义三个源子图以创建一个强大子图的示例。 ### 详情 @@ -106,7 +106,7 @@ npm run deploy-local ### 第 4 步：合并进区块统计子图 -This composed Subgraph combines and aggregates the information from the source Subgraphs above, providing a unified view of block statistics. To deploy this Subgraph locally, run the same commands as above. +这个合成子图将上述三个源子图的信息合并和汇总，为区块统计提供了统一的视图。 要在本地部署此子图，请执行与上面相同的命令。 > 注意： > @@ -117,16 +117,16 @@ This composed Subgraph combines and aggregates the information from the source S #### 关键函数 - 它提供了一个综合数据模型，其中包括所有相关的区块计量。 -- It combines data from 3 source Subgraphs, and provides a comprehensive view of block statistics, enabling more complex queries and analyses. +- 它综合了三个源子图中的数据，并提供了对区块统计的全面看法，从而能够进行更复杂的查询和分析。 ## 要点前瞻 - 这个强大的工具将缩放子图的开发，并允许您合并多个子图。 -- The setup includes the deployment of 3 source Subgraphs and one final deployment of the composed Subgraph. +- 设置包括部署三个源子图以及最终部署一个合成子图。 - 这个功能解锁了可扩展性，简化了开发和维护效率。 ## 其他资源 -- Check out all the code for this example in [this GitHub repo](https://github.com/graphprotocol/example-composable-subgraph). +- 在[此GitHub仓库](https://github.com/graphprotocol/example-composable-subgraph)中查看此示例的所有代码。 - 若要将高级功能添加到您的子图，请参阅[子图高级功能](/developing/creating/advanced/)。 - 要了解更多关于聚合的信息，请查看 [Timeseries and Aggreg](/subgraphs/developing/creating/advanced/#timeseries-and-aggregations)。 From abe81ae5d29211353365a906cf6f96b3b5fa90a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:38 -0400 Subject: [PATCH 029/290] New translations subgraph-composition.mdx (Romanian) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ro/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ro/subgraphs/guides/subgraph-composition.mdx index 09f1939c1fde..1d6ab12958b4 100644 --- a/website/src/pages/ro/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ro/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 98fa75bec761ff085c4f73333a553409633ac34b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:40 -0400 Subject: [PATCH 030/290] New translations subgraph-composition.mdx (French) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/fr/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/fr/subgraphs/guides/subgraph-composition.mdx index ccf1f043fcb1..00c4238f168a 100644 --- a/website/src/pages/fr/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/fr/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ Alors que le subgraph source est un subgraph standard, le subgraph dépendant ut ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From f6e37a1d5621198f385934f00c2995d8aa8ef9ef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:41 -0400 Subject: [PATCH 031/290] New translations subgraph-composition.mdx (Spanish) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/es/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/es/subgraphs/guides/subgraph-composition.mdx index 3f5fc5e44cca..6fa236b8b7e4 100644 --- a/website/src/pages/es/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/es/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 19b105350f092b5ccc8fbd0023d29754374f1e69 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:42 -0400 Subject: [PATCH 032/290] New translations subgraph-composition.mdx (Arabic) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ar/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ar/subgraphs/guides/subgraph-composition.mdx index 080de99b5ba1..35cdef554157 100644 --- a/website/src/pages/ar/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ar/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 26bdbfb050002bba3666c4292610dcf17ea630b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:43 -0400 Subject: [PATCH 033/290] New translations subgraph-composition.mdx (Czech) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/cs/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/cs/subgraphs/guides/subgraph-composition.mdx index f5480ab15a48..aef8badbe0e1 100644 --- a/website/src/pages/cs/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/cs/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 317da639e306768fc5c9dec718efdcf1c75458de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:44 -0400 Subject: [PATCH 034/290] New translations subgraph-composition.mdx (German) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/de/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/de/subgraphs/guides/subgraph-composition.mdx index 900ecb8e636d..07c4381f7cda 100644 --- a/website/src/pages/de/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/de/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ Während der Ausgangs-Subgraph ein Standard-Subgraph ist, verwendet der abhängi ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From ed8786d000272683adae14ed9726f0f6a89594c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:45 -0400 Subject: [PATCH 035/290] New translations subgraph-composition.mdx (Italian) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/it/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/it/subgraphs/guides/subgraph-composition.mdx index 51d882cda5e9..08112a03ca4d 100644 --- a/website/src/pages/it/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/it/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 981a8351d324c13b8c5b991debf44db5979f1e33 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:47 -0400 Subject: [PATCH 036/290] New translations subgraph-composition.mdx (Japanese) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ja/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ja/subgraphs/guides/subgraph-composition.mdx index 62b2d8eb4657..f781231fe623 100644 --- a/website/src/pages/ja/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ja/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 97c25d3a21bc582f7c9563667812519ab49a2044 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:48 -0400 Subject: [PATCH 037/290] New translations subgraph-composition.mdx (Korean) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ko/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ko/subgraphs/guides/subgraph-composition.mdx index 09f1939c1fde..1d6ab12958b4 100644 --- a/website/src/pages/ko/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ko/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From cb662c8b79d8101fddea861ea5688bc65cb847b8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:49 -0400 Subject: [PATCH 038/290] New translations subgraph-composition.mdx (Dutch) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/nl/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/nl/subgraphs/guides/subgraph-composition.mdx index bf62dc4dde30..995dde415867 100644 --- a/website/src/pages/nl/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/nl/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 169087ae53ef74e5f4a6a9544243c080b55d963f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:50 -0400 Subject: [PATCH 039/290] New translations subgraph-composition.mdx (Polish) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/pl/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/pl/subgraphs/guides/subgraph-composition.mdx index fb8427b04be9..bc440454d326 100644 --- a/website/src/pages/pl/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/pl/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From bb64e9ad40904f8629ce340f99a50f210b19f148 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:51 -0400 Subject: [PATCH 040/290] New translations subgraph-composition.mdx (Portuguese) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/pt/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/pt/subgraphs/guides/subgraph-composition.mdx index 8996bfaf909f..b923f027b2a8 100644 --- a/website/src/pages/pt/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/pt/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ Embora o subgraph de origem seja um Subgraph padrão, o dependente usa o recurso ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 32ace24b62409ab8fab1848b7dcdf227041e1b2e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:52 -0400 Subject: [PATCH 041/290] New translations subgraph-composition.mdx (Russian) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ru/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ru/subgraphs/guides/subgraph-composition.mdx index 5c3b634a5620..ac52b2d5d6f2 100644 --- a/website/src/pages/ru/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ru/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ Composable Subgraphs enable you to combine multiple Subgraphs' data sources into ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 7d177eb4de3a71fb48752453822f0d6baf272c4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:53 -0400 Subject: [PATCH 042/290] New translations subgraph-composition.mdx (Swedish) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/sv/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/sv/subgraphs/guides/subgraph-composition.mdx index 805a904c7ba9..8b00714ad8ad 100644 --- a/website/src/pages/sv/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/sv/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 8cb7934e4a60bb269821a588cad410f72c7313e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:55 -0400 Subject: [PATCH 043/290] New translations subgraph-composition.mdx (Turkish) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/tr/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/tr/subgraphs/guides/subgraph-composition.mdx index 51bf15b4ecd9..0247c0ad6f96 100644 --- a/website/src/pages/tr/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/tr/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 689db200dfe388ec24573e453a0421880c278005 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:56 -0400 Subject: [PATCH 044/290] New translations subgraph-composition.mdx (Ukrainian) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/uk/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/uk/subgraphs/guides/subgraph-composition.mdx index 044af23870e6..dea76080a9ff 100644 --- a/website/src/pages/uk/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/uk/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 3f44e6c7f4d15cd39093a8fcfa23c9d310bc19c0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:57 -0400 Subject: [PATCH 045/290] New translations subgraph-composition.mdx (Chinese Simplified) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx index 8b6eca6cfc16..c2cfe24212ef 100644 --- a/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/zh/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ sidebarTitle: 用多个子图生成可编译子图 ### 源子图 -- 所有子图都需要发布一个 **specversion 1.3.0 或更高版本** (使用最新的 graph-cli 版本才能部署可合成的子图) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - 见此注释：https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- 仅限不可变实体：所有子图都必须有[不可变实体](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) 当布置子图时 -- 打印可以在源子图中使用，但只有不可变的实体可以在源子图顶部组成 -- 源子图不能在现有实体顶部使用图形 -- 合成实体可用于组成，但由聚合实体组成的实体不能直接进行额外聚合 +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### 合成子图 -- 您只能创建合成 \*_最多5 个源子图_ -- 合成子图只能使用 **来自同一链的数据源** -- **嵌套的合成尚不支持**：此时不允许在另一个合成子图上面撰写 -- 聚合实体可用于合成，但其合成实体也不能直接使用聚合 -- 开发者无法使用子图数据源创建在线数据源 (例如，您不能在合成子图中做正常的事件处理器，以及调用处理器和区块处理器) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). 此外，您还可以探索 [示例-合成-子图](https://github.com/graphprotocol/example-composable-subgraph) 存储库，用于可编译子图的工作实现。 From 18fbb1f1b8f049065e29ae4ffd9a56510e333b47 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:58 -0400 Subject: [PATCH 046/290] New translations subgraph-composition.mdx (Urdu (Pakistan)) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ur/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/ur/subgraphs/guides/subgraph-composition.mdx index c8b09c0c30fc..1a8f98cc5afa 100644 --- a/website/src/pages/ur/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/ur/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 2785f8bac4d5311b0402e256e1b343d9d874f529 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:52:59 -0400 Subject: [PATCH 047/290] New translations subgraph-composition.mdx (Vietnamese) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/vi/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/vi/subgraphs/guides/subgraph-composition.mdx index 65aeb9f4ac09..6ed5ad3ec639 100644 --- a/website/src/pages/vi/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/vi/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 3ea0e971a05e17b0984352edf5259f0a16b10829 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:53:00 -0400 Subject: [PATCH 048/290] New translations subgraph-composition.mdx (Marathi) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/mr/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/mr/subgraphs/guides/subgraph-composition.mdx index 52da13032a9c..5ffaa92e22e8 100644 --- a/website/src/pages/mr/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/mr/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 08acc756fabd0e6775587eaeff1fd8125584c6ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 8 Apr 2025 17:53:01 -0400 Subject: [PATCH 049/290] New translations subgraph-composition.mdx (Hindi) --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/hi/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/hi/subgraphs/guides/subgraph-composition.mdx index be71b8199574..3083a342ddc7 100644 --- a/website/src/pages/hi/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/hi/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ Subgraph संयोजन एक शक्तिशाली विशेष ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs From 5c54549daaa388f3f204dcfaaca55e4190108672 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:04 -0400 Subject: [PATCH 050/290] New translations index.json (Romanian) --- website/src/pages/ro/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ro/index.json b/website/src/pages/ro/index.json index fe31bcb97070..8893031ab220 100644 --- a/website/src/pages/ro/index.json +++ b/website/src/pages/ro/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 0e5dfa9f93c02d50a0a6607f0a545e50e270dfd7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:06 -0400 Subject: [PATCH 051/290] New translations index.json (French) --- website/src/pages/fr/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/fr/index.json b/website/src/pages/fr/index.json index ee19877c78e6..9a02e3d03d6f 100644 --- a/website/src/pages/fr/index.json +++ b/website/src/pages/fr/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 2182edf2ded86edaf5307c4038e22899f1928820 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:07 -0400 Subject: [PATCH 052/290] New translations index.json (Spanish) --- website/src/pages/es/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/es/index.json b/website/src/pages/es/index.json index 2c1eeb105f26..921acbc3d2a5 100644 --- a/website/src/pages/es/index.json +++ b/website/src/pages/es/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Corrientes secundarias", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From f63d23f87117d45afcb7d45d2f97766f37206c79 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:08 -0400 Subject: [PATCH 053/290] New translations index.json (Arabic) --- website/src/pages/ar/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ar/index.json b/website/src/pages/ar/index.json index 2443372843a8..e26aa5f61165 100644 --- a/website/src/pages/ar/index.json +++ b/website/src/pages/ar/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "متعدد-السلاسل", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From c4ae2137b59cb7e3c4b8d39c59323ea69ebc0166 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:09 -0400 Subject: [PATCH 054/290] New translations index.json (Czech) --- website/src/pages/cs/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/cs/index.json b/website/src/pages/cs/index.json index 545b2b717b56..c2b98123b2f8 100644 --- a/website/src/pages/cs/index.json +++ b/website/src/pages/cs/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Průzkumník grafů", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 6ce98d1d79efb51e07c9f90f568b2d3011c01978 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:10 -0400 Subject: [PATCH 055/290] New translations index.json (German) --- website/src/pages/de/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/de/index.json b/website/src/pages/de/index.json index b56ea56c5897..2bc35f433737 100644 --- a/website/src/pages/de/index.json +++ b/website/src/pages/de/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 9a66da928bf87cce54efd1338ce0848b583c0acf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:11 -0400 Subject: [PATCH 056/290] New translations index.json (Italian) --- website/src/pages/it/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/it/index.json b/website/src/pages/it/index.json index f243894b47b5..a3e1f199da24 100644 --- a/website/src/pages/it/index.json +++ b/website/src/pages/it/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From e00db0876460962d10e3f6e3ad9bb8558702eafd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:12 -0400 Subject: [PATCH 057/290] New translations index.json (Japanese) --- website/src/pages/ja/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ja/index.json b/website/src/pages/ja/index.json index 2034192e0089..589057c828e9 100644 --- a/website/src/pages/ja/index.json +++ b/website/src/pages/ja/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "サブストリーム", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "グラフエクスプローラ", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From f86ea140d2dcad68aeaf0e1184d33f38a9b86e97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:14 -0400 Subject: [PATCH 058/290] New translations index.json (Korean) --- website/src/pages/ko/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ko/index.json b/website/src/pages/ko/index.json index 95bf30d1752a..59e8e3dc4c44 100644 --- a/website/src/pages/ko/index.json +++ b/website/src/pages/ko/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 29d2f5d45c91fe8fd97863b5f48fa9e7d2466596 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:15 -0400 Subject: [PATCH 059/290] New translations index.json (Dutch) --- website/src/pages/nl/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/nl/index.json b/website/src/pages/nl/index.json index 200a19192e1c..2abb81fe6aac 100644 --- a/website/src/pages/nl/index.json +++ b/website/src/pages/nl/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Verkenner", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From a7c00289e15e5ce0159defbc4a56d2ba99bcd5c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:16 -0400 Subject: [PATCH 060/290] New translations index.json (Polish) --- website/src/pages/pl/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/pl/index.json b/website/src/pages/pl/index.json index ca9ba66107b7..fe69cac3c6b7 100644 --- a/website/src/pages/pl/index.json +++ b/website/src/pages/pl/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 0b498e7d56fdf3eb7598603444dcd917efd4666b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:18 -0400 Subject: [PATCH 061/290] New translations index.json (Portuguese) --- website/src/pages/pt/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/pt/index.json b/website/src/pages/pt/index.json index 0fe9ac551a34..19e12670e0bf 100644 --- a/website/src/pages/pt/index.json +++ b/website/src/pages/pt/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 16bd8637b55b2c1af1733323f7ad7d2682c3ba7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:19 -0400 Subject: [PATCH 062/290] New translations index.json (Russian) --- website/src/pages/ru/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ru/index.json b/website/src/pages/ru/index.json index 28d369ba865d..41a841b6be9a 100644 --- a/website/src/pages/ru/index.json +++ b/website/src/pages/ru/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Субпотоки", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 3d39b630af9b6a3b0c15eccb2e5eb428435c5555 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:20 -0400 Subject: [PATCH 063/290] New translations index.json (Swedish) --- website/src/pages/sv/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/sv/index.json b/website/src/pages/sv/index.json index 23a97080ffc1..3f84b3b849b4 100644 --- a/website/src/pages/sv/index.json +++ b/website/src/pages/sv/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Underströmmar", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graf Utforskaren", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From ba3b44c5f448b18b443ab691419e8fc00ad8bb00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:22 -0400 Subject: [PATCH 064/290] New translations index.json (Turkish) --- website/src/pages/tr/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/tr/index.json b/website/src/pages/tr/index.json index 7a721a844042..b4ccaa3a9195 100644 --- a/website/src/pages/tr/index.json +++ b/website/src/pages/tr/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substream'ler", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Gezgini", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 29b44b21cda3b9dc0c2f726e2d77cc7bfd721865 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:23 -0400 Subject: [PATCH 065/290] New translations index.json (Ukrainian) --- website/src/pages/uk/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/uk/index.json b/website/src/pages/uk/index.json index 2e98e3092a7e..9835101379a4 100644 --- a/website/src/pages/uk/index.json +++ b/website/src/pages/uk/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From f179d3e93f4c5400e0dd4e33c1811d2de976f133 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:24 -0400 Subject: [PATCH 066/290] New translations index.json (Chinese Simplified) --- website/src/pages/zh/index.json | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/website/src/pages/zh/index.json b/website/src/pages/zh/index.json index e82bc7f27a27..4bcbbdc1fce9 100644 --- a/website/src/pages/zh/index.json +++ b/website/src/pages/zh/index.json @@ -79,9 +79,21 @@ "title": "子图快速入门", "description": "开始你的旅程进入子图开发。" }, - "substreams": { - "title": "子流", - "description": "用于实时索引的流高速数据。" + "substreamsQuickStart": { + "title": "Substreams quick start", + "description": "Stream high-speed data for real-time indexing." + }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph 浏览器", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "访问教程、模板和文档以建立自定义数据模块。" }, "timeseries": { "title": "时间序列和聚合", @@ -99,7 +111,7 @@ "nonEvm": { "officialDocs": { "title": "官方子流文档", - "description": "用于实时索引的流高速数据。" + "description": "Stream high-speed data for real-time indexing." }, "spsIntro": { "title": "Substreams驱动的子图的常见问题", @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "访问教程、模板和文档以建立自定义数据模块。" }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "子流启动器", "description": "利用这个锅炉板来创建您的第一个子流模块。" }, "substreamsRepo": { - "title": "子流仓库", + "title": "Substreams GitHub repository", "description": "研究、促进或定制核心子流框架。" } } From ebfe96d876e7c3ddff6c2f7aad4da0448acb3142 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:25 -0400 Subject: [PATCH 067/290] New translations index.json (Urdu (Pakistan)) --- website/src/pages/ur/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/ur/index.json b/website/src/pages/ur/index.json index ba4e9527fa53..16ad53e143ff 100644 --- a/website/src/pages/ur/index.json +++ b/website/src/pages/ur/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "سب سٹریمز", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "گراف ایکسپلورر", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From cfe18f2526ae1e1b8c28d31d1f1974cb7892a4b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:26 -0400 Subject: [PATCH 068/290] New translations index.json (Vietnamese) --- website/src/pages/vi/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/vi/index.json b/website/src/pages/vi/index.json index 2793483b60d9..e9cddd69d9ef 100644 --- a/website/src/pages/vi/index.json +++ b/website/src/pages/vi/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "Substreams", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Trình khám phá Graph", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 4038e66efff282db07ead96434cd92cecc9e03dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:27 -0400 Subject: [PATCH 069/290] New translations index.json (Marathi) --- website/src/pages/mr/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/mr/index.json b/website/src/pages/mr/index.json index add2f95c68b0..ab39f74bbdf9 100644 --- a/website/src/pages/mr/index.json +++ b/website/src/pages/mr/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "उपप्रवाह", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 1c85051e64111ed74951bd7176c287b0321fbc85 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 03:27:29 -0400 Subject: [PATCH 070/290] New translations index.json (Hindi) --- website/src/pages/hi/index.json | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/website/src/pages/hi/index.json b/website/src/pages/hi/index.json index 006af907dc33..14a53be3ec2c 100644 --- a/website/src/pages/hi/index.json +++ b/website/src/pages/hi/index.json @@ -79,10 +79,22 @@ "title": "Subgraph quick start", "description": "Kickstart your journey into subgraph development." }, - "substreams": { - "title": "सबस्ट्रीम", + "substreamsQuickStart": { + "title": "Substreams quick start", "description": "Stream high-speed data for real-time indexing." }, + "tokenapi": { + "title": "The Graph's Token API", + "description": "Query token data and leverage native MCP support." + }, + "graphExplorer": { + "title": "Graph Explorer", + "description": "Find and query existing blockchain data." + }, + "substreamsDev": { + "title": "Substreams.dev", + "description": "Access tutorials, templates, and documentation to build custom data modules." + }, "timeseries": { "title": "Timeseries & Aggregations", "description": "Learn to track metrics like daily volumes or user growth." @@ -109,12 +121,16 @@ "title": "Substreams.dev", "description": "Access tutorials, templates, and documentation to build custom data modules." }, + "customSubstreamsSinks": { + "title": "Custom Substreams Sinks", + "description": "Leverage existing Substreams sinks to access data." + }, "substreamsStarter": { "title": "Substreams starter", "description": "Leverage this boilerplate to create your first Substreams module." }, "substreamsRepo": { - "title": "Substreams repo", + "title": "Substreams GitHub repository", "description": "Study, contribute to, or customize the core Substreams framework." } } From 08f91591f43957ef44054de025a301a60b935d2d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:19 -0400 Subject: [PATCH 071/290] New translations quick-start.mdx (Romanian) --- website/src/pages/ro/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ro/token-api/quick-start.mdx b/website/src/pages/ro/token-api/quick-start.mdx index 4653c3d41ac6..ef67bed88a5d 100644 --- a/website/src/pages/ro/token-api/quick-start.mdx +++ b/website/src/pages/ro/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 7282ed2f1ce264dc3425226b96635cea9a149c1a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:20 -0400 Subject: [PATCH 072/290] New translations quick-start.mdx (French) --- website/src/pages/fr/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/fr/token-api/quick-start.mdx b/website/src/pages/fr/token-api/quick-start.mdx index 4a38a878fd7c..40452d9f419a 100644 --- a/website/src/pages/fr/token-api/quick-start.mdx +++ b/website/src/pages/fr/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prérequis -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 86ff34be4e4b94a3ce4d8c525351cd0006080f1a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:21 -0400 Subject: [PATCH 073/290] New translations quick-start.mdx (Spanish) --- website/src/pages/es/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/es/token-api/quick-start.mdx b/website/src/pages/es/token-api/quick-start.mdx index 8488268e1356..1af940b5b68f 100644 --- a/website/src/pages/es/token-api/quick-start.mdx +++ b/website/src/pages/es/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From b5c48f4bcf160150223a4b60b98c5b423b358505 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:22 -0400 Subject: [PATCH 074/290] New translations quick-start.mdx (Arabic) --- website/src/pages/ar/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ar/token-api/quick-start.mdx b/website/src/pages/ar/token-api/quick-start.mdx index c5fa07fa9371..ff1a58015fc0 100644 --- a/website/src/pages/ar/token-api/quick-start.mdx +++ b/website/src/pages/ar/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 31ac9207850b64106cd92019104013576e9e4d53 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:23 -0400 Subject: [PATCH 075/290] New translations quick-start.mdx (Czech) --- website/src/pages/cs/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/cs/token-api/quick-start.mdx b/website/src/pages/cs/token-api/quick-start.mdx index 4083154b5a8b..454ffd30b02f 100644 --- a/website/src/pages/cs/token-api/quick-start.mdx +++ b/website/src/pages/cs/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From df07511741711d983df7f2209ee39451718e8c4e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:25 -0400 Subject: [PATCH 076/290] New translations quick-start.mdx (German) --- website/src/pages/de/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/de/token-api/quick-start.mdx b/website/src/pages/de/token-api/quick-start.mdx index b84fad5f665a..b4074258c581 100644 --- a/website/src/pages/de/token-api/quick-start.mdx +++ b/website/src/pages/de/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Voraussetzungen -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 4ed90a574b247a1a162fc657c9ab3e19fb28b9fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:26 -0400 Subject: [PATCH 077/290] New translations quick-start.mdx (Italian) --- website/src/pages/it/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/it/token-api/quick-start.mdx b/website/src/pages/it/token-api/quick-start.mdx index 4653c3d41ac6..ef67bed88a5d 100644 --- a/website/src/pages/it/token-api/quick-start.mdx +++ b/website/src/pages/it/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 1b4f6be39aa05409eb7c5e9ca7cd12626ca64a0f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:27 -0400 Subject: [PATCH 078/290] New translations quick-start.mdx (Japanese) --- website/src/pages/ja/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ja/token-api/quick-start.mdx b/website/src/pages/ja/token-api/quick-start.mdx index 0b64515243cb..059a2f43984d 100644 --- a/website/src/pages/ja/token-api/quick-start.mdx +++ b/website/src/pages/ja/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 2228e308b1e1e38726762c71364c57c1c41d64cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:28 -0400 Subject: [PATCH 079/290] New translations quick-start.mdx (Korean) --- website/src/pages/ko/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ko/token-api/quick-start.mdx b/website/src/pages/ko/token-api/quick-start.mdx index 4653c3d41ac6..ef67bed88a5d 100644 --- a/website/src/pages/ko/token-api/quick-start.mdx +++ b/website/src/pages/ko/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 46ebf545bb44bcad7a8602e2d52b51b24d6f8ab1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:30 -0400 Subject: [PATCH 080/290] New translations quick-start.mdx (Dutch) --- website/src/pages/nl/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/nl/token-api/quick-start.mdx b/website/src/pages/nl/token-api/quick-start.mdx index b1b07812ba97..b2c498a85f80 100644 --- a/website/src/pages/nl/token-api/quick-start.mdx +++ b/website/src/pages/nl/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 5b180afd8dd3d2d2f3b6e73c52077a827ec857e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:31 -0400 Subject: [PATCH 081/290] New translations quick-start.mdx (Polish) --- website/src/pages/pl/token-api/quick-start.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/src/pages/pl/token-api/quick-start.mdx b/website/src/pages/pl/token-api/quick-start.mdx index 05884b06caab..20663af633f4 100644 --- a/website/src/pages/pl/token-api/quick-start.mdx +++ b/website/src/pages/pl/token-api/quick-start.mdx @@ -1,6 +1,6 @@ --- title: Token API Quick Start -sidebarTitle: ' Na start' +sidebarTitle: " Na start" --- ![The Graph Token API Quick Start banner](/img/token-api-quickstart-banner.jpg) @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From e685c583124ceaab013ae86f3f23001b5fb8b0eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:32 -0400 Subject: [PATCH 082/290] New translations quick-start.mdx (Portuguese) --- website/src/pages/pt/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/pt/token-api/quick-start.mdx b/website/src/pages/pt/token-api/quick-start.mdx index 32882f96458c..6ffc93937703 100644 --- a/website/src/pages/pt/token-api/quick-start.mdx +++ b/website/src/pages/pt/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Pré-requisitos -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 833aa617fcf343e7b9fd84b568ef8d9bfc42d43e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:33 -0400 Subject: [PATCH 083/290] New translations quick-start.mdx (Russian) --- website/src/pages/ru/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ru/token-api/quick-start.mdx b/website/src/pages/ru/token-api/quick-start.mdx index a878bea36a20..59d60750c989 100644 --- a/website/src/pages/ru/token-api/quick-start.mdx +++ b/website/src/pages/ru/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Предварительные требования -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From b74b8f7c7be2b8f96bdbecb5f7f9791ecd90c6f4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:34 -0400 Subject: [PATCH 084/290] New translations quick-start.mdx (Swedish) --- website/src/pages/sv/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/sv/token-api/quick-start.mdx b/website/src/pages/sv/token-api/quick-start.mdx index db512ba0d7f8..4fabbaccb36e 100644 --- a/website/src/pages/sv/token-api/quick-start.mdx +++ b/website/src/pages/sv/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From b82aaa58c1461f0ff1a848c2dc0bf59723f5540a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:36 -0400 Subject: [PATCH 085/290] New translations quick-start.mdx (Turkish) --- website/src/pages/tr/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/tr/token-api/quick-start.mdx b/website/src/pages/tr/token-api/quick-start.mdx index 18629312033a..b321575025e9 100644 --- a/website/src/pages/tr/token-api/quick-start.mdx +++ b/website/src/pages/tr/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From a96cd39ee0e4d6a7caec9421a28ab5e1b170f243 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:37 -0400 Subject: [PATCH 086/290] New translations quick-start.mdx (Ukrainian) --- website/src/pages/uk/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/uk/token-api/quick-start.mdx b/website/src/pages/uk/token-api/quick-start.mdx index 69a5a4d298d3..ea80878a9a0d 100644 --- a/website/src/pages/uk/token-api/quick-start.mdx +++ b/website/src/pages/uk/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 3a8e0077196a107f0287866fc32966b7ad7c527a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:38 -0400 Subject: [PATCH 087/290] New translations quick-start.mdx (Chinese Simplified) --- website/src/pages/zh/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/zh/token-api/quick-start.mdx b/website/src/pages/zh/token-api/quick-start.mdx index f55201103dc4..314459353ca6 100644 --- a/website/src/pages/zh/token-api/quick-start.mdx +++ b/website/src/pages/zh/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Graph的 代币API允许您通过 GET 请求访问区块链代币信息。 ## 先决条件 -在您开始之前，通过注册[The Graph市场](https://thegraph.market/)，获得一个 JWT 代币。 您可以使用下拉菜单为您的API密钥生成一个 JWT 代币。 +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## 认证 -所有API端点都使用插入头中的JWT代币进行身份验证，该代币名为`Authorization: Bearer `。 +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 29e92b05fb9a1e7915ee9deba1fe5a1d17140e80 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:39 -0400 Subject: [PATCH 088/290] New translations quick-start.mdx (Urdu (Pakistan)) --- website/src/pages/ur/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/ur/token-api/quick-start.mdx b/website/src/pages/ur/token-api/quick-start.mdx index 0efd314e3281..d3e0152a21b7 100644 --- a/website/src/pages/ur/token-api/quick-start.mdx +++ b/website/src/pages/ur/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From e08b337a8df32151c4ffe4d9f567075c58c65385 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:40 -0400 Subject: [PATCH 089/290] New translations quick-start.mdx (Vietnamese) --- website/src/pages/vi/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/vi/token-api/quick-start.mdx b/website/src/pages/vi/token-api/quick-start.mdx index 4a426052097d..93a5eae55597 100644 --- a/website/src/pages/vi/token-api/quick-start.mdx +++ b/website/src/pages/vi/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From f59ca8ead4d497a98110b58faeb04cdbfba291d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:41 -0400 Subject: [PATCH 090/290] New translations quick-start.mdx (Marathi) --- website/src/pages/mr/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/mr/token-api/quick-start.mdx b/website/src/pages/mr/token-api/quick-start.mdx index 427bd0f2a59b..9b6f9bb125a6 100644 --- a/website/src/pages/mr/token-api/quick-start.mdx +++ b/website/src/pages/mr/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## Prerequisites -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From bfaf8c3093e46cf75b0f72124af119039400b557 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 9 Apr 2025 20:19:42 -0400 Subject: [PATCH 091/290] New translations quick-start.mdx (Hindi) --- website/src/pages/hi/token-api/quick-start.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/pages/hi/token-api/quick-start.mdx b/website/src/pages/hi/token-api/quick-start.mdx index a381a3c8565c..494416568dc4 100644 --- a/website/src/pages/hi/token-api/quick-start.mdx +++ b/website/src/pages/hi/token-api/quick-start.mdx @@ -13,11 +13,11 @@ The Token API provides access to onchain token data, including balances, holders ## आवश्यक शर्तें -Before you begin, get a JWT token by signing up on [The Graph Market](https://thegraph.market/). You can generate a JWT token for each of your API keys using the dropdown menu. +Before you begin, get a JWT API token by signing up on [The Graph Market](https://thegraph.market/). Make sure to use the JWT API Token, not the API key. Each API key can generate a new JWT API Token at any time. ## Authentication -All API endpoints are authenticated using a JWT token inserted in the header as `Authorization: Bearer `. +All API endpoints are authenticated using a JWT API token inserted in the header as `Authorization: Bearer `. ```json { From 1bc112654625a648540b3f4785ba78da8beefeb9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:31 -0400 Subject: [PATCH 092/290] New translations quick-start.mdx (German) --- .../src/pages/de/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/de/subgraphs/quick-start.mdx b/website/src/pages/de/subgraphs/quick-start.mdx index 4608dc407ca7..120831ea9ab2 100644 --- a/website/src/pages/de/subgraphs/quick-start.mdx +++ b/website/src/pages/de/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Schnellstart --- -Erfahren Sie, wie Sie auf einfache Weise einen [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) auf The Graph erstellen, veröffentlichen und abfragen können. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Voraussetzungen - Eine Krypto-Wallet -- Eine Smart-Contract-Adresse in einem [unterstützten Netzwerk](/supported-networks/ -- [Node.js](https://nodejs.org/) installiert -- Ein Paketmanager Ihrer Wahl (`npm`, `yarn` oder `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## Wie man einen Subgraphen erstellt ### 1. Erstellen Sie einen Subgraphen in Subgraph Studio -Gehen Sie zu [Subgraph Studio] (https://thegraph.com/studio/) und verbinden Sie Ihre Wallet. - -Mit Subgraph Studio können Sie Subgraphen erstellen, verwalten, bereitstellen und veröffentlichen sowie API-Schlüssel erstellen und verwalten. - -Klicken Sie auf „Einen Subgraphen erstellen“. Es wird empfohlen, den Subgraph in Title Case zu benennen: „Subgraph Name Chain Name“. +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Installieren der Graph-CLI @@ -37,20 +41,22 @@ Verwendung von [yarn] (https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialisieren Sie Ihren Subgraphen +Verify install: -> Sie finden die Befehle für Ihren spezifischen Subgraphen auf der Subgraphen-Seite in [Subgraph Studio] (https://thegraph.com/studio/). +```sh +graph --version +``` -Der Befehl `graph init` erstellt automatisch ein Gerüst eines Subgraphen auf der Grundlage der Ereignisse Ihres Vertrags. +### 3. Initialisieren Sie Ihren Subgraphen -Der folgende Befehl initialisiert Ihren Subgraphen anhand eines bestehenden Vertrags: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -Wenn Ihr Vertrag auf dem jeweiligen Blockscanner, auf dem er eingesetzt wird (z. B. [Etherscan](https://etherscan.io/)), verifiziert wird, wird die ABI automatisch im CLI erstellt. - Wenn Sie Ihren Subgraphen initialisieren, werden Sie von der CLI nach den folgenden Informationen gefragt: - **Protokoll**: Wählen Sie das Protokoll, mit dem Ihr Subgraph Daten indizieren soll. @@ -59,19 +65,17 @@ Wenn Sie Ihren Subgraphen initialisieren, werden Sie von der CLI nach den folgen - **Ethereum-Netzwerk** (optional): Möglicherweise müssen Sie angeben, von welchem EVM-kompatiblen Netzwerk Ihr Subgraph Daten indizieren soll. - **Vertragsadresse**: Suchen Sie die Adresse des Smart Contracts, von dem Sie Daten abfragen möchten. - **ABI**: Wenn die ABI nicht automatisch ausgefüllt wird, müssen Sie sie manuell in eine JSON-Datei eingeben. -- **Startblock**: Sie sollten den Startblock eingeben, um die Subgraph-Indizierung von Blockchain-Daten zu optimieren. Ermitteln Sie den Startblock, indem Sie den Block suchen, in dem Ihr Vertrag bereitgestellt wurde. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Vertragsname**: Geben Sie den Namen Ihres Vertrags ein. - **Vertragsereignisse als Entitäten indizieren**: Es wird empfohlen, dies auf „true“ zu setzen, da es automatisch Mappings zu Ihrem Subgraph für jedes emittierte Ereignis hinzufügt. - **Einen weiteren Vertrag hinzufügen** (optional): Sie können einen weiteren Vertrag hinzufügen. -Der folgende Screenshot zeigt ein Beispiel dafür, was Sie bei der Initialisierung Ihres Subgraphen erwarten können: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph-Befehl](/img/CLI-Example.png) ### 4. Bearbeiten Sie Ihren Subgraphen -Der `init`-Befehl im vorherigen Schritt erzeugt einen Gerüst-Subgraphen, den Sie als Ausgangspunkt für den Aufbau Ihres Subgraphen verwenden können. - Wenn Sie Änderungen am Subgraphen vornehmen, werden Sie hauptsächlich mit drei Dateien arbeiten: - Manifest (`subgraph.yaml`) - definiert, welche Datenquellen Ihr Subgraph indizieren wird. @@ -82,9 +86,7 @@ Eine detaillierte Aufschlüsselung, wie Sie Ihren Subgraphen schreiben, finden S ### 5. Verteilen Sie Ihren Subgraphen -> Denken Sie daran, dass die Bereitstellung nicht dasselbe ist wie die Veröffentlichung. - -Wenn Sie einen Subgraphen **breitstellen**, schieben Sie ihn in das [Subgraph Studio] (https://thegraph.com/studio/), wo Sie ihn testen, einstellen und überprüfen können. Die Indizierung eines bereitgestellten Subgraphen wird vom [Upgrade Indexierer](https://thegraph.com/blog/upgrade-indexer/) durchgeführt, der ein einzelner Indexierer ist, der von Edge & Node betrieben wird, und nicht von den vielen dezentralen Indexierern im Graph Network. Ein **eingesetzter** Subgraph ist frei nutzbar, ratenbegrenzt, für die Öffentlichkeit nicht sichtbar und für Entwicklungs-, Staging- und Testzwecke gedacht. +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. 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. Sobald Ihr Subgraph geschrieben ist, führen Sie die folgenden Befehle aus: @@ -107,8 +109,6 @@ graph deploy ``` ```` -Die CLI fragt nach einer Versionsbezeichnung. Es wird dringend empfohlen, [semantische Versionierung](https://semver.org/) zu verwenden, z.B. `0.0.1`. - ### 6. Überprüfen Sie Ihren Subgraphen Wenn Sie Ihren Subgraph vor der Veröffentlichung testen möchten, können Sie mit [Subgraph Studio] (https://thegraph.com/studio/) Folgendes tun: @@ -125,55 +125,13 @@ Wenn Ihr Subgraph bereit für eine Produktionsumgebung ist, können Sie ihn im d - Es macht Ihren Subgraphen verfügbar, um von den dezentralisierten [Indexierers](/indexing/overview/) auf The Graph Network indiziert zu werden. - Sie hebt Ratenbeschränkungen auf und macht Ihren Subgraphen öffentlich durchsuchbar und abfragbar im [Graph Explorer] (https://thegraph.com/explorer/). -- Es macht Ihren Subgraphen für [Kuratoren](/resources/roles/curating/) verfügbar, um ihn zu kuratieren. - -> Je mehr GRT Sie und andere auf Ihrem Subgraph kuratieren, desto mehr Indexierer werden dazu angeregt, Ihren Subgraphen zu indizieren, was die Servicequalität verbessert, die Latenzzeit reduziert und die Netzwerkredundanz für Ihren Subgraphen erhöht. - -#### Veröffentlichung mit Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -Um Ihren Subgraphen zu veröffentlichen, klicken Sie auf die Schaltfläche "Veröffentlichen" im Dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Veröffentlichen eines Subgraphen auf Subgraph Studio](/img/publish-sub-transfer.png) -Wählen Sie das Netzwerk aus, in dem Sie Ihren Subgraphen veröffentlichen möchten. - -#### Veröffentlichen über die CLI - -Ab Version 0.73.0 können Sie Ihren Subgraphen auch mit dem Graph CLI veröffentlichen. - -Öffnen Sie den `graph-cli`. - -Verwenden Sie die folgenden Befehle: - -```` -```sh -graph codegen && graph build -``` - -Dann, - -```sh -graph publish -``` -```` - -3. Es öffnet sich ein Fenster, in dem Sie Ihre Wallet verbinden, Metadaten hinzufügen und Ihren fertigen Subgraphen in einem Netzwerk Ihrer Wahl bereitstellen können. - -![cli-ui](/img/cli-ui.png) - -Wie Sie Ihre Bereitstellung anpassen können, erfahren Sie unter [Veröffentlichen eines Subgraphen](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Hinzufügen von Signalen zu Ihrem Subgraphen - -1. Um Indexierer für die Abfrage Ihres Subgraphen zu gewinnen, sollten Sie ihn mit einem GRT-Kurationssignal versehen. - - - Diese Maßnahme verbessert die Servicequalität, verringert die Latenz und erhöht die Netzwerkredundanz und -verfügbarkeit für Ihren Subgraphen. - -2. Indexer erhalten GRT Rewards auf der Grundlage des signalisierten Betrags, wenn sie für Indexing Rewards in Frage kommen. - - - Es wird empfohlen, mindestens 3.000 GRT zu kuratieren, um 3 Indexierer zu gewinnen. Prüfen Sie die Berechtigung zur Belohnung anhand der Nutzung der Subgraph-Funktion und der unterstützten Netzwerke. - -Um mehr über das Kuratieren zu erfahren, lesen Sie [Kuratieren](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. Um Gaskosten zu sparen, können Sie Ihren Subgraphen in der gleichen Transaktion kuratieren, in der Sie ihn veröffentlichen, indem Sie diese Option wählen: From 210e4f2f4aed72582bda36775cc80fcc5440238c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:32 -0400 Subject: [PATCH 093/290] New translations quick-start.mdx (Portuguese) --- .../src/pages/pt/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/pt/subgraphs/quick-start.mdx b/website/src/pages/pt/subgraphs/quick-start.mdx index 9fda78533084..2868b76181d9 100644 --- a/website/src/pages/pt/subgraphs/quick-start.mdx +++ b/website/src/pages/pt/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Começo Rápido --- -Aprenda como construir, editar, e solicitar queries de um [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) do The Graph com facilidade. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Pré-requisitos - Uma carteira de criptomoedas -- Um endereço de contrato inteligente numa [rede apoiada](/supported-networks/) -- Ter o [Node.js](https://nodejs.org/) instalado -- Um gestor de pacotes da sua escolha (`npm`, `yarn` ou `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## Como Construir um Subgraph ### 1. Crie um subgraph no Subgraph Studio -Entre no [Subgraph Studio](https://thegraph.com/studio/) e conecte a sua carteira de criptomoedas. - -O Subgraph Studio permite a criação, gestão, implantação e edição de subgraphs, assim como a criação e a gestão de chaves de API. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Como instalar o Graph CLI @@ -37,20 +41,22 @@ Uso de [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Inicialize o seu Subgraph +Verify install: -> Veja comandos para o seu subgraph específico na página do subgraph no [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -O comando `graph init` criará automaticamente uma estrutura de subgraph com base nos eventos do seu contrato. +### 3. Inicialize o seu Subgraph -O comando a seguir inicializa o seu subgraph a partir de um contrato existente: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -Se o seu contrato for verificado no scanner de blocos respetivo onde foi implantado (por exemplo, [Etherscan](https://etherscan.io/)), a interface binária de aplicativo será criada na CLI. - Ao inicializar o seu subgraph, a CLI pedirá pelas seguintes informações: - **Protocolo:** Escolha o protocolo do qual o seu subgraph indexará dados. @@ -59,19 +65,17 @@ Ao inicializar o seu subgraph, a CLI pedirá pelas seguintes informações: - **Rede Ethereum** (opcional): é possível que tenha de especificar a rede compatível com EVM de onde o seu subgraph indexará dados. - **Endereço de contrato:** Localize o endereço do contrato inteligente do qual quer solicitar dados por queries. - **ABI (interface binária de aplicativo):** Se a ABI não estiver preenchida automaticamente, insira-a manualmente como um arquivo JSON. -- **Bloco Inicial:** Insira o bloco inicial para poupar tempo enquanto o seu subgraph indexa dados da blockchain. O bloco inicial pode ser localizado ao encontrar o bloco onde o seu contrato foi implantado. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Nome do Contrato:** Insira o nome do seu contrato. - **Indexar eventos de contrato como entidades:** Sugerimos configurar isto como `true`, já que ele automaticamente adicionará mapeamentos ao seu subgraph para cada evento emitido. - **Adicionar outro contrato** (opcional): também é possível adicionar outro contrato. -Veja a imagem a seguir para um exemplo do que esperar quando for inicializar o seu subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Comando do subgraph](/img/CLI-Example.png) ### 4. Revise o seu Subgraph -O comando `init` no passo anterior cria uma estrutura de subgraph que pode ser usada como ponto de início para construir o seu subgraph. - Enquanto faz mudanças ao subgraph, você trabalhará principalmente com três arquivos: - Manifest (`subgraph.yaml`) — define quais fontes de dados serão indexadas pelos seus subgraphs. @@ -82,9 +86,7 @@ Para mais informações sobre como escrever o seu subgraph, veja [Como Criar um ### 5. Implante o seu subgraph -> Lembre-se: implantar não é o mesmo que editar. - -Ao **implantar** um subgraph, você o envia para o [Subgraph Studio](https://thegraph.com/studio/), onde ele pode ser testado, preparado e revisto. A indexação de um subgraph implantado é realizada pelo [Indexador de Atualização](https://thegraph.com/blog/upgrade-indexer/), que é um único Indexador operado pela Edge & Node (que também é a proprietária do mesmo), em vez dos muitos indexadores descentralizados na The Graph Network. Um subgraph **implantado** é gratuito para uso, limitado por taxa, não visível ao público e destinado a fins de programação, preparação e teste. +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. 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. Quando o seu subgraph estiver pronto, execute os seguintes comandos: @@ -107,8 +109,6 @@ graph deploy ``` ```` -A CLI solicitará um rótulo de versão. Recomendamos fortemente que use [controle semântico de versão](https://semver.org/); por exemplo, `0.0.1`. - ### 6. Analise o seu subgraph Se quiser testar o seu subgraph antes de editá-lo, use o [Subgraph Studio](https://thegraph.com/studio/) para: @@ -125,55 +125,13 @@ Quando o seu subgraph estiver pronto para um ambiente de produção, ele pode se - Torna o seu subgraph disponível para indexação pelos [indexadores](/indexing/overview/) descentralizados na The Graph Network. - Remove limites de taxa, e torna o seu subgraph disponível a buscas e queries no [Graph Explorer](https://thegraph.com/explorer/). -- Disponibiliza o seu subgraph para curadoria por [Curadores](/resources/roles/curating/). - -> Quanto maior a quantia de GRT selecionada por você e outros no seu subgraph, mais os indexadores serão incentivados a indexar o seu subgraph, o que melhora a qualidade do serviço, reduz a latência, e aprimora a redundância de rede para o seu subgraph. - -#### Como Editar com o Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -Para editar o seu subgraph, clique no botão Publish ("Editar") no painel de controlo. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Edite um subgraph no Subgraph Studio](/img/publish-sub-transfer.png) -Selecione a rede onde deseja editar o seu subgraph. - -#### Publicação da CLI - -Desde a versão 0.73.0, é possível editar o seu subgraph com a Graph CLI. - -Abra a `graph-cli`. - -Use os seguintes comandos: - -```` -```sh -graph codegen && graph build -``` - -Depois, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -Para personalizar a sua implantação, veja [Como Editar um Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. Para atrair Indexadores de modo a fazer queries no seu subgraph, adicione um sinal de curadoria de GRT a ele. - - - Isto melhora a qualidade do serviço, reduz a latência, e aprimora a redundância e a disponibilidade da rede para o seu subgraph. - -2. Se tiverem direito a recompensas por indexação, os Indexadores recebem recompensas em GRT com base na quantia sinalizada. - - - Recomendamos curar pelo menos 3.000 GRT para atrair 3 Indexadores. Verifique a elegibilidade de recompensas com base no uso de funções do subgraph e nas redes apoiadas. - -Para saber mais sobre curadoria, clique [aqui](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. Para economizar gás, é possível selecionar o seu subgraph na mesma transação em que o edita através desta opção: From 5654982c0f5d775dffed4d90c7cb6874ee8193fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:33 -0400 Subject: [PATCH 094/290] New translations quick-start.mdx (Russian) --- .../src/pages/ru/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ru/subgraphs/quick-start.mdx b/website/src/pages/ru/subgraphs/quick-start.mdx index c676f1cf698d..0a60f184d203 100644 --- a/website/src/pages/ru/subgraphs/quick-start.mdx +++ b/website/src/pages/ru/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Быстрый старт --- -Узнайте, как легко создать, опубликовать и запросить [Субграф](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) на The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Предварительные требования - Криптовалютный кошелек -- Адрес смарт-контракта в [поддерживаемой сети](/supported-networks/) -- [Node.js](https://nodejs.org/) установлен -- Менеджер пакетов на Ваш выбор (`npm`, `yarn` или `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## Как создать субграф ### 1. Создайте Субграф в Subgraph Studio -Перейдите в [Subgraph Studio](https://thegraph.com/studio/) и подключите свой кошелек. - -Subgraph Studio позволяет создавать, управлять, развертывать и публиковать Субграфы, а также создавать и управлять API-ключами. - -Нажмите "Создать субграф". Рекомендуется называть субграф с использованием Заглавного регистра: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Установка Graph CLI @@ -37,20 +41,22 @@ npm install -g @graphprotocol/graph-cli@latest yarn global add @graphprotocol/graph-cli ``` -### 3. Инициализируйте ваш субграф +Verify install: -> Вы можете найти команды для вашего конкретного субграфа на странице субграфа в [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -Команда `graph init` автоматически создаст каркас субграфа на основе событий вашего контракта. +### 3. Инициализируйте ваш субграф -Следующая команда инициализирует ваш субграф на основе существующего контракта: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -Если Ваш контракт верифицирован на соответствующем блоксканере, где он развернут (например, [Etherscan](https://etherscan.io/)), то ABI будет автоматически создан в CLI. - Когда вы инициализируете свой субграф, CLI запросит у вас следующую информацию: - **Протокол**: Выберите протокол, данные из которого будет индексировать ваш субграф. @@ -59,19 +65,17 @@ graph init - **Сеть Ethereum** (необязательно): Вам может понадобиться указать, из какой совместимой с EVM сети ваш субграф будет индексировать данные. - **Адрес контракта**: Найдите адрес смарт-контракта, из которого Вы хотите запрашивать данные. - **ABI**: Если ABI не заполнен автоматически, Вам придется ввести его вручную в формате JSON. -- **Начальный блок**: Вы должны ввести начальный блок для оптимизации индексирования данных субграфа. Найдите начальный блок, определив блок, в котором был развернут ваш контракт. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Имя контракта**: Введите имя Вашего контракта. - **Индексирование событий контракта как объектов**: Рекомендуется установить это значение в "true", так как это автоматически добавит мэппинги для каждого сгенерированного события в ваш субграф. - **Добавление еще одного контракта (опционально)**: Вы можете добавить еще один контракт. -Вот скриншот, который демонстрирует, чего ожидать при инициализации вашего субграфа: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Команда субграфа](/img/CLI-Example.png) ### 4. Редактирование вашего субграфа -Команда `init` на предыдущем шаге создает скелет субграфа, который вы можете использовать в качестве отправной точки для создания вашего субграфа. - При внесении изменений в субграф вы будете в основном работать с тремя файлами: - Манифест (`subgraph.yaml`) — определяет, какие источники данных ваш субграф будет индексировать. @@ -82,9 +86,7 @@ graph init ### 5. Развертывание Вашего субграфа -> Помните, развертывание — это не то же самое, что публикация. - -Когда вы **разворачиваете** субграф, вы отправляете его в [Subgraph Studio](https://thegraph.com/studio/), где можете тестировать, настраивать и проверять его. Индексирование развернутого субграфа выполняется с помощью [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/), который является единственным Индексатором, принадлежащим и управляемым Edge & Node, а не многими децентрализованными Индексаторами в сети The Graph. **Развернутый** субграф бесплатен для использования, имеет ограничения по количеству запросов, не виден для общественности и предназначен для разработки, настройки и тестирования. +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. 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. Как только ваш субграф написан, выполните следующие команды: @@ -107,8 +109,6 @@ graph deploy ``` ```` -CLI запросит метку версии. Настоятельно рекомендуется использовать [семантическую версию](https://semver.org/), например, `0.0.1`. - ### 6. Просмотр Вашего субграфа Если вы хотите протестировать свой субграф перед его публикацией, вы можете использовать [Subgraph Studio](https://thegraph.com/studio/) для выполнения следующих действий: @@ -125,55 +125,13 @@ CLI запросит метку версии. Настоятельно реко - Это делает ваш субграф доступным для индексирования децентрализованными [Индексаторами](/indexing/overview/) в сети The Graph. - Это снимает ограничения по количеству запросов и делает ваш субграф общедоступным для поиска и запросов в [Graph Explorer](https://thegraph.com/explorer/). -- Это делает ваш субграф доступным для [Кураторов](/resources/roles/curating/), чтобы они могли его курировать. - -> Чем больше GRT вы и другие курируете на вашем субграфе, тем больше Индексаторов будут мотивированы индексировать ваш субграф, что улучшит качество обслуживания, уменьшит задержку и повысит избыточность сети для вашего субграфа. - -#### Публикация с помощью Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -Чтобы опубликовать ваш субграф, нажмите кнопку "Опубликовать" на панели управления. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Выберите сеть, в которую вы хотите опубликовать свой субграф. - -#### Публикация с помощью CLI - -Начиная с версии 0.73.0, вы также можете опубликовать свой субграф с помощью Graph CLI. - -Откройте `graph-cli`. - -Используйте следующие команды: - -```` -```sh -graph codegen && graph build -``` - -Затем, - -```sh -graph publish -``` -```` - -3. Откроется окно, где Вы сможете подключить свой кошелек, добавить метаданные и развернуть финализированный субграф в выбранной Вами сети. - -![cli-ui](/img/cli-ui.png) - -Чтобы настроить ваше развертывание, смотрите раздел [Публикация субграфа](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Добавление сигнала к Вашему субграфу - -1. Чтобы привлечь Индексаторов для запросов к вашему субграфу, вам следует добавить сигнал курирования GRT. - - - Это действие улучшает качество обслуживания, снижает задержку и повышает сетевую избыточность и доступность для вашего субграфа. - -2. Если индексаторы имеют право на получение вознаграждений за индексацию, они получат вознаграждения в GRT, в соответствии с количеством поданного сигнала. - - - Рекомендуется курировать как минимум 3,000 GRT, чтобы привлечь 3 Индексаторов. Проверьте право на вознаграждения в зависимости от использования функций субграфа и поддерживаемых сетей. - -Чтобы узнать больше о кураторстве, прочитайте статью [Курирование](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. Чтобы сэкономить на газовых расходах, вы можете закрепить свой субграф в той же транзакции, в которой его публикуете, выбрав эту опцию: From dfd4acc3b41e9469f18dc352892c66adc0a6549b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:34 -0400 Subject: [PATCH 095/290] New translations quick-start.mdx (Chinese Simplified) --- .../src/pages/zh/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/zh/subgraphs/quick-start.mdx b/website/src/pages/zh/subgraphs/quick-start.mdx index 01a0c5cbcfc5..f6392e4925bd 100644 --- a/website/src/pages/zh/subgraphs/quick-start.mdx +++ b/website/src/pages/zh/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: 快速开始 --- -学习如何轻松地构建、发布和查询The Graph上的 [子图](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph)。 +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## 先决条件 - 一个加密钱包 -- 智能合约在一个[支持网络](/supported-networks/)上的地址 -- [Node.js](https://nodejs.org/) 已安装 -- 您选择的软件包管理器 (`npm`, `yarn` 或 `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## 如何构建子图 ### 1. 在子图工作室中创建子图 -进入[Subgraph Studio](https://thegraph.com/studio/)并连接你的钱包。 - -子图工作室可以让您创建、管理、部署和发布子图，以及创建和管理 API 密钥。 - -点击“创建子图”。建议在标题大小写中为子图命名：“子图名称链名称”。 +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. 安装 Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. 初始化子图 +Verify install: -> 您可以在[Subgraph Studio](https://thegraph.com/studio/)的子图页面找到针对您特定子图的命令。 +```sh +graph --version +``` -`graph init`命令将根据你的合约事件自动创建一个子图的手写。 +### 3. 初始化子图 -以下命令从现有合约初始化你的子图： +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -如果您的合约已经在部署的相应拦截扫描仪上进行了验证(例如 [Etherscan](https://etherscan.io/))， 那么自动在 CLI 中创建 ABI 。 - 初始化子图时，CLI工具会要求您提供以下信息： - **协议**：选择子图将要索引数据的协议。 @@ -59,19 +65,17 @@ graph init - **Etherum网络** (可选)：您可能需要指定您的子图将索引数据来自哪个EVM兼容网络。 - **合约地址**：找到要查询数据的智能合约地址。 - **ABI**：如果ABI没有自动填充，您需要手动输入JSON文件。 -- **启动Block**：您应该输入起始区块以优化区块链数据的子图索引。 通过找到您的合约部署所在的区块来定位起始区块。 +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **合约名称**：输入合约名称。 - **将合约事件作为实体索引**：建议您将其设置为真。 因为它会自动将映射添加到你的子图中。 - **添加其他合约**（可选）：您可以添加其他合约。 -请参阅下面的屏幕截图，以获取初始化子图时所需的示例： +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. 编写子图 -上一步的 `init` 命令创建了一个可以用作构建Subgraph起点的 scaffold 子图。 - 在对子图进行修改时，你将主要与三个文件一起工作： - 清单（`subgraph.yaml`）--该清单定义了你的子图将索引哪些数据源。 @@ -82,9 +86,7 @@ graph init ### 5. 部署子图 -> 记住，部署与发布不同。 - -当你**部署**一个Subgraph时，你将它推送到[Subgraph Studio](https://thegraph.com/studio/)，在那里你可以测试、分段和查看它。 已部署的子图索引由 [升级索引人](https://thegraph.com/blog/upgrade-indexer/) 执行。 这是一个由Edge & Node拥有和操作的单一索引人，而不是由The Graph网络中许多去中心化的索引人拥有和操作的。 **部署** 子图可自由使用，频率限制，公众看不到，并可用于开发、分阶段和测试。 +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. 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. 一旦您的子图被编写好，请运行以下命令： @@ -107,8 +109,6 @@ graph deploy ``` ```` -CLI 将要求一个版本标签。强烈建议使用 [语义版本](https://semver.org/)，例如`0.0.1`。 - ### 6. 审查子图 如果你想在发布之前测试你的子图，你可以使用 [Subgraph Studio](https://thegraph.com/studio/) 来执行以下操作： @@ -125,55 +125,13 @@ CLI 将要求一个版本标签。强烈建议使用 [语义版本](https://semv - 使您的子图可以被去中心化的 [索引人](/indexing/overview/)索引到The Graph网络。 - 取消了费率限制，使你的子图可以公开搜索并可以在 [Graph Explorer](https://thegraph.com/explorer/) 中查询。 -- 使您的子图可供 [策展人](/resources/roles/curating/)进行策展。 - -> 您和其他人在您的子图上策展的GRT数量越多，索引人将会更多地被激励来索引您的子图， 提高服务质量，降低延迟性，并提高子图的网络冗余性。 - -#### 从子图工作室发布 +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -要发布您的子图，请单击仪表盘中的发布按钮。 +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -选择您想要发布子图的网络。 - -#### 从 CLI 发布 - -截止版本 0.73.0 ，您也可以使用 GraphCLI 发布您的子图。 - -打开 `graph-cli`。 - -使用以下命令： - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. 一个窗口将打开，允许您连接您的钱包，添加元数据，并将您的最终子图部署到您选择的网络。 - -![cli-ui](/img/cli-ui.png) - -要成功发布您的子图，请査阅[发布子图](/subgraphs/developing/publishing/publishing-a-subgraph/)。 - -#### 将信号添加到您的子图 - -1. 为了吸引索引人查询您的子图，您应该添加 GRT 策展信号。 - - - 此操作可以提高服务质量，减少延迟，提高网络冗余性和子图的可用性。 - -2. 如果符合索引奖励，索引人将根据信号金额获得GRT奖励。 - - - 建议策展至少 3 000GRT 来吸引3个索引人。根据子图功能的使用情况和支持的网络检查奖励资格。 - -要了解更多关于策展的信息，请访问 [Curating](/resources/roles/curating/)。 +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. 为了节省燃气费，您可以通过选择此选项来策展您的子图发布在相同的交易中： From a202326a3ec5aa53b6ab40bffe7bdb5bd1e34f4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:36 -0400 Subject: [PATCH 096/290] New translations quick-start.mdx (Spanish) --- .../src/pages/es/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/es/subgraphs/quick-start.mdx b/website/src/pages/es/subgraphs/quick-start.mdx index 57d13e479ba2..ae0d63e54b9e 100644 --- a/website/src/pages/es/subgraphs/quick-start.mdx +++ b/website/src/pages/es/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Comienzo Rapido --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - Una wallet crypto -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Instala the graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 0fa5d43a19f91618ee3a539688c23e30afb26662 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:37 -0400 Subject: [PATCH 097/290] New translations quick-start.mdx (French) --- .../src/pages/fr/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/fr/subgraphs/quick-start.mdx b/website/src/pages/fr/subgraphs/quick-start.mdx index c227ec40ccc7..23c88a13a305 100644 --- a/website/src/pages/fr/subgraphs/quick-start.mdx +++ b/website/src/pages/fr/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Démarrage rapide --- -Apprenez à construire, publier et interroger facilement un [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) sur The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prérequis - Un portefeuille crypto -- Une adresse de contrat intelligent sur un [réseau pris en charge](/supported-networks/) -- [Node.js](https://nodejs.org/) installé -- Un gestionnaire de package de votre choix (`npm`, `yarn` ou `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## Comment construire un subgraph ### 1. Créer un subgraph dans Subgraph Studio -Accédez à [Subgraph Studio](https://thegraph.com/studio/) et connectez votre portefeuille. - -Subgraph Studio vous permet de créer, de gérer, de déployer et de publier des subgraphs, ainsi que de créer et de gérer des clés API. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Installez la CLI Graph @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialiser votre subgraph +Verify install: -> Vous trouverez les commandes pour votre subgraph spécifique sur la page du subgraph dans [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -La commande `graph init` créera automatiquement un échafaudage d'un subgraph basé sur les événements de votre contrat. +### 3. Initialiser votre subgraph -La commande suivante initialise votre subgraph à partir d'un contrat existant : +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -Si votre contrat est vérifié sur le scanner de blocs où il est déployé (comme [Etherscan](https://etherscan.io/)), l'ABI sera automatiquement créé dans le CLI. - Lorsque vous initialisez votre subgraph, la CLI vous demande les informations suivantes : - **Protocole** : Choisissez le protocole à partir duquel votre subgraph indexera les données. @@ -59,19 +65,17 @@ Lorsque vous initialisez votre subgraph, la CLI vous demande les informations su - **Réseau Ethereum** (optionnel) : Vous pouvez avoir besoin de spécifier le réseau compatible EVM à partir duquel votre subgraph indexera les données. - **Adresse du contrat** : Localisez l'adresse du contrat intelligent dont vous souhaitez interroger les données. - **ABI** : Si l'ABI n'est pas renseigné automatiquement, vous devrez le saisir manuellement sous la forme d'un fichier JSON. -- **Bloc de départ** : Vous devez saisir le bloc de départ pour optimiser l'indexation du Subgraph des données de la blockchain. Localisez le bloc de départ en trouvant le bloc où votre contrat a été déployé. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Nom du contrat** : Saisissez le nom de votre contrat. - **Indexer les événements contractuels comme des entités** : Il est conseillé de mettre cette option à true, car elle ajoutera automatiquement des mappages à votre subgraph pour chaque événement émis. - **Ajouter un autre contrat** (facultatif) : Vous pouvez ajouter un autre contrat. -La capture d'écran suivante donne un exemple de ce à quoi on peut s'attendre lors de l'initialisation du subgraph : +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Commande de subgraph](/img/CLI-Example.png) ### 4. Modifiez votre subgraph -La commande `init` de l'étape précédente crée un Subgraph d'échafaudage que vous pouvez utiliser comme point de départ pour construire votre Subgraph. - Lorsque vous modifiez le Subgraph, vous travaillez principalement avec trois fichiers : - Manifest (`subgraph.yaml`) - définit les sources de données que votre Subgraph indexera. @@ -82,9 +86,7 @@ Pour une description détaillée de la manière d'écrire votre Subgraph, consul ### 5. Déployez votre Subgraph -> N'oubliez pas que le déploiement n'est pas la même chose que la publication. - -Lorsque vous **déployez** un Subgraph, vous l'envoyez au [Subgraph Studio](https://thegraph.com/studio/), où vous pouvez le tester, le mettre en scène et le réviser. L'indexation d'un Subgraph déployé est effectuée par l'[Indexeur de mise à niveau](https://thegraph.com/blog/upgrade-indexer/), qui est un indexeur unique détenu et exploité par Edge & Node, plutôt que par les nombreux Indexeurs décentralisés de The Graph Network. Un Subgraph **déployé** est libre d'utilisation, à taux limité, non visible par le public et destiné à être utilisé à des fins de développement, de mise en place et de test. +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. 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. Une fois que votre Subgraph est écrit, exécutez les commandes suivantes : @@ -107,8 +109,6 @@ graph deploy ``` ```` -La CLI demandera un label de version. Il est fortement recommandé d'utiliser [le versionnement sémantique](https://semver.org/), par exemple `0.0.1`. - ### 6. Examinez votre subgraph Si vous souhaitez tester votre subgraph avant de le publier, vous pouvez utiliser [Subgraph Studio](https://thegraph.com/studio/) pour effectuer les opérations suivantes : @@ -125,55 +125,13 @@ Lorsque votre subgraph est prêt pour un environnement de production, vous pouve - Il rend votre subgraph disponible pour être indexé par les [Indexeurs](/indexing/overview/) décentralisés sur The Graph Network. - Il supprime les limites de taux et rend votre subgraph publiquement consultable et interrogeable dans [Graph Explorer](https://thegraph.com/explorer/). -- Il met votre subgraph à la disposition des [Curateurs](/resources/roles/curating/) pour qu'ils le curent. - -> Plus la quantité de GRT que vous et d'autres personnes curez dans votre subgraph est importante, plus les Indexeurs seront incités à indexer votre subgraph, ce qui améliorera la qualité du service, réduira la latence et renforcera la redondance du réseau pour votre subgraph. - -#### Publier avec Subgraph Studio⁠ +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -Pour publier votre subgraph, cliquez sur le bouton Publier dans le tableau de bord. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publier un subgraph sur Subgraph Studio](/img/publish-sub-transfer.png) -Sélectionnez le réseau dans lequel vous souhaitez publier votre subgraph. - -#### Publication à partir de la CLI - -Depuis la version 0.73.0, vous pouvez également publier votre subgraph à l'aide de Graph CLI. - -Ouvrez le `graph-cli`. - -Utilisez les commandes suivantes : - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -Pour personnaliser votre déploiement, voir [Publier un subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. Pour inciter les Indexeurs à interroger votre subgraph, vous devez y ajouter un signal de curation GRT. - - - Cette action améliore la qualité de service, réduit la latence et améliore la redondance et la disponibilité du réseau pour votre Subgraph. - -2. Si éligibles aux récompenses d'indexation, les Indexeurs reçoivent des récompenses en GRT proportionnelles au montant signalé. - - - Il est recommandé de rassembler au moins 3 000 GRT pour attirer 3 Indexeurs. Vérifiez l'éligibilité des récompenses en fonction de l'utilisation des fonctions du subgraph et des réseaux pris en charge. - -Pour en savoir plus sur la curation, lisez [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. Pour économiser des frais de gas, vous pouvez créer votre subgraph dans la même transaction que vous le publiez en sélectionnant cette option : From 233d75cfe2c5d949bf3578b97591f179039e4565 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:38 -0400 Subject: [PATCH 098/290] New translations quick-start.mdx (Romanian) --- .../src/pages/ro/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ro/subgraphs/quick-start.mdx b/website/src/pages/ro/subgraphs/quick-start.mdx index a803ac8695fa..b5c4a0fdc09e 100644 --- a/website/src/pages/ro/subgraphs/quick-start.mdx +++ b/website/src/pages/ro/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Quick Start --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 648ba939aaa11bb23a2d29f1596517f7ccf25393 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:39 -0400 Subject: [PATCH 099/290] New translations quick-start.mdx (Arabic) --- .../src/pages/ar/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ar/subgraphs/quick-start.mdx b/website/src/pages/ar/subgraphs/quick-start.mdx index 9b7bf860e87d..05a51a6a9a02 100644 --- a/website/src/pages/ar/subgraphs/quick-start.mdx +++ b/website/src/pages/ar/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: بداية سريعة --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - محفظة عملات رقمية -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 110be7c8e6a4dd4374d1bf3f0e8180455d86a442 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:40 -0400 Subject: [PATCH 100/290] New translations quick-start.mdx (Czech) --- .../src/pages/cs/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/cs/subgraphs/quick-start.mdx b/website/src/pages/cs/subgraphs/quick-start.mdx index 7c52d4745a83..27325c2c7f08 100644 --- a/website/src/pages/cs/subgraphs/quick-start.mdx +++ b/website/src/pages/cs/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Rychlé spuštění --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - Kryptopeněženka -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Nainstalujte Graph CLI @@ -37,20 +41,22 @@ Použitím [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From e23e332adfa3b33db038dd579154b82228368398 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:42 -0400 Subject: [PATCH 101/290] New translations quick-start.mdx (Italian) --- .../src/pages/it/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/it/subgraphs/quick-start.mdx b/website/src/pages/it/subgraphs/quick-start.mdx index a803ac8695fa..b5c4a0fdc09e 100644 --- a/website/src/pages/it/subgraphs/quick-start.mdx +++ b/website/src/pages/it/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Quick Start --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From f535e3b744e41b651c05576d0bd20066d51fd6ce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:44 -0400 Subject: [PATCH 102/290] New translations quick-start.mdx (Japanese) --- .../src/pages/ja/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ja/subgraphs/quick-start.mdx b/website/src/pages/ja/subgraphs/quick-start.mdx index df410ba8ec9b..e900192305b4 100644 --- a/website/src/pages/ja/subgraphs/quick-start.mdx +++ b/website/src/pages/ja/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: クイックスタート --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - クリプトウォレット -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Graph CLI をインストールする @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 68857b6d1d0056d267920b7266250a96bc68aa76 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:45 -0400 Subject: [PATCH 103/290] New translations quick-start.mdx (Korean) --- .../src/pages/ko/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ko/subgraphs/quick-start.mdx b/website/src/pages/ko/subgraphs/quick-start.mdx index a803ac8695fa..b5c4a0fdc09e 100644 --- a/website/src/pages/ko/subgraphs/quick-start.mdx +++ b/website/src/pages/ko/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Quick Start --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From bc58049bcd0f34c9cf1f8d175c8e8ac7335eceff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:46 -0400 Subject: [PATCH 104/290] New translations quick-start.mdx (Dutch) --- .../src/pages/nl/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/nl/subgraphs/quick-start.mdx b/website/src/pages/nl/subgraphs/quick-start.mdx index 7efec0891fa6..4bd6674aaa12 100644 --- a/website/src/pages/nl/subgraphs/quick-start.mdx +++ b/website/src/pages/nl/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Snelle Start --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 9d6386b6a9a58590ebc48b532c4c766eea4c7ec2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:47 -0400 Subject: [PATCH 105/290] New translations quick-start.mdx (Polish) --- .../src/pages/pl/subgraphs/quick-start.mdx | 98 ++++++------------- 1 file changed, 28 insertions(+), 70 deletions(-) diff --git a/website/src/pages/pl/subgraphs/quick-start.mdx b/website/src/pages/pl/subgraphs/quick-start.mdx index 62c69977491f..6f20081817c9 100644 --- a/website/src/pages/pl/subgraphs/quick-start.mdx +++ b/website/src/pages/pl/subgraphs/quick-start.mdx @@ -1,25 +1,29 @@ --- -title: ' Na start' +title: " Na start" --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From f86519620cb54236bd4cc5175ea2ed6c68424145 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:48 -0400 Subject: [PATCH 106/290] New translations quick-start.mdx (Swedish) --- .../src/pages/sv/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/sv/subgraphs/quick-start.mdx b/website/src/pages/sv/subgraphs/quick-start.mdx index f3fba67ef0d7..b95ac213f7ba 100644 --- a/website/src/pages/sv/subgraphs/quick-start.mdx +++ b/website/src/pages/sv/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Snabbstart --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - En kryptoplånbok -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Installera Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 7bb758efea0e7eabda3f9f3b120bad2f15e50d81 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:50 -0400 Subject: [PATCH 107/290] New translations quick-start.mdx (Turkish) --- .../src/pages/tr/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/tr/subgraphs/quick-start.mdx b/website/src/pages/tr/subgraphs/quick-start.mdx index f0687717220f..8320065877da 100644 --- a/website/src/pages/tr/subgraphs/quick-start.mdx +++ b/website/src/pages/tr/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Hızlı Başlangıç --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - Bir kripto cüzdanı -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -[Subgraph Studio](https://thegraph.com/studio/)'ya gidin ve cüzdanınızı bağlayın. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Graph CLI'yi yükleyin @@ -37,20 +41,22 @@ npm install -g @graphprotocol/graph-cli@latest yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Subgraph Studio ile yayımlama +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### CLI'den Yayımlama - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -`graph-cli`yi açın. - -Şu komutları kullanın: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. Endeksleme ödüllerine hak kazanan Endeksleyiciler sinyal miktarına bağlı olarak GRT ödülü alırlar. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From a84f74dbd5985df8d846225eb53349080ee785dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:51 -0400 Subject: [PATCH 108/290] New translations quick-start.mdx (Ukrainian) --- .../src/pages/uk/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/uk/subgraphs/quick-start.mdx b/website/src/pages/uk/subgraphs/quick-start.mdx index 8ed3c12ffaa9..eea1f1d2b2de 100644 --- a/website/src/pages/uk/subgraphs/quick-start.mdx +++ b/website/src/pages/uk/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Швидкий старт --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - Криптогаманець -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Встановлення Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From a8b076edc58c91651e351ea3be701b3e70a296a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:52 -0400 Subject: [PATCH 109/290] New translations quick-start.mdx (Urdu (Pakistan)) --- .../src/pages/ur/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/ur/subgraphs/quick-start.mdx b/website/src/pages/ur/subgraphs/quick-start.mdx index 280a19a8a3d9..721c4a359c45 100644 --- a/website/src/pages/ur/subgraphs/quick-start.mdx +++ b/website/src/pages/ur/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: فورا شروع کریں --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - ایک کرپٹو والیٹ -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. گراف CLI انسٹال کریں @@ -37,20 +41,22 @@ npm install -g @graphprotocol/graph-cli@latest yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 7f1266abf92f5ac16b8aaf14d44b0acb0db2cf93 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:53 -0400 Subject: [PATCH 110/290] New translations quick-start.mdx (Vietnamese) --- .../src/pages/vi/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/vi/subgraphs/quick-start.mdx b/website/src/pages/vi/subgraphs/quick-start.mdx index 0af59e0b4c46..017be070511a 100644 --- a/website/src/pages/vi/subgraphs/quick-start.mdx +++ b/website/src/pages/vi/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Bắt đầu nhanh --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. Install the Graph CLI @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 43ef1b90ecc51187e4487c3139e1fae20a70626b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:54 -0400 Subject: [PATCH 111/290] New translations quick-start.mdx (Marathi) --- .../src/pages/mr/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/mr/subgraphs/quick-start.mdx b/website/src/pages/mr/subgraphs/quick-start.mdx index b14954bc11a4..83e790887315 100644 --- a/website/src/pages/mr/subgraphs/quick-start.mdx +++ b/website/src/pages/mr/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: क्विक स्टार्ट --- -Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## Prerequisites - एक क्रिप्टो वॉलेट -- A smart contract address on a [supported network](/supported-networks/) -- [Node.js](https://nodejs.org/) installed -- A package manager of your choice (`npm`, `yarn` or `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## How to Build a Subgraph ### 1. Create a Subgraph in Subgraph Studio -Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet. - -Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys. - -Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name". +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. आलेख CLI स्थापित करा @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### 3. Initialize your Subgraph +Verify install: -> You can find commands for your specific Subgraph on the Subgraph page in [Subgraph Studio](https://thegraph.com/studio/). +```sh +graph --version +``` -The `graph init` command will automatically create a scaffold of a Subgraph based on your contract's events. +### 3. Initialize your Subgraph -The following command initializes your Subgraph from an existing contract: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -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. - When you initialize your Subgraph, the CLI will ask you for the following information: - **Protocol**: Choose the protocol your Subgraph will be indexing data from. @@ -59,19 +65,17 @@ When you initialize your Subgraph, the CLI will ask you for the following inform - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. - **Contract address**: Locate the smart contract address you’d like to query data from. - **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. -- **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed. +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **Contract Name**: Input the name of your contract. - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. - **Add another contract** (optional): You can add another contract. -See the following screenshot for an example for what to expect when initializing your Subgraph: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![Subgraph command](/img/CLI-Example.png) ### 4. Edit your Subgraph -The `init` command in the previous step creates a scaffold Subgraph that you can use as a starting point to build your Subgraph. - When making changes to the Subgraph, you will mainly work with three files: - Manifest (`subgraph.yaml`) - defines what data sources your Subgraph will index. @@ -82,9 +86,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su ### 5. Deploy your Subgraph -> Remember, deploying is not the same as publishing. - -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. +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. 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. Once your Subgraph is written, run the following commands: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. - ### 6. Review your Subgraph If you’d like to test your Subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following: @@ -125,55 +125,13 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be to indexed by the decentralized [Indexers](/indexing/overview/) on The Graph Network. - It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). -- It makes your Subgraph available for [Curators](/resources/roles/curating/) to curate it. - -> 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. - -#### Publishing with Subgraph Studio +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -To publish your Subgraph, click the Publish button in the dashboard. +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -Select the network to which you would like to publish your Subgraph. - -#### Publishing from the CLI - -As of version 0.73.0, you can also publish your Subgraph with the Graph CLI. - -Open the `graph-cli`. - -Use the following commands: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice. - -![cli-ui](/img/cli-ui.png) - -To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). - -#### Adding signal to your Subgraph - -1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it. - - - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your Subgraph. - -2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount. - - - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks. - -To learn more about curation, read [Curating](/resources/roles/curating/). +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option: From 645450e6c60b718de010d31f51295ebe3100ceb4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 11:26:55 -0400 Subject: [PATCH 112/290] New translations quick-start.mdx (Hindi) --- .../src/pages/hi/subgraphs/quick-start.mdx | 96 ++++++------------- 1 file changed, 27 insertions(+), 69 deletions(-) diff --git a/website/src/pages/hi/subgraphs/quick-start.mdx b/website/src/pages/hi/subgraphs/quick-start.mdx index cbf3550a3170..d11eb2cc3d0e 100644 --- a/website/src/pages/hi/subgraphs/quick-start.mdx +++ b/website/src/pages/hi/subgraphs/quick-start.mdx @@ -2,24 +2,28 @@ title: Quick Start --- -The Graph पर आसानी से एक [सबग्राफ](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) को बनाना, प्रकाशित करना और क्वेरी करना सीखें। +Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. + +By the end, you'll have: + +- Initialized a Subgraph from a smart contract +- Deployed it to Subgraph Studio for testing +- Published to The Graph Network for decentralized indexing ## पूर्वावश्यकताएँ - एक क्रिप्टो वॉलेट -- एक स्मार्ट contract पता एक [supported network](/supported-networks/) पर। -- [Node.js](https://nodejs.org/) इंस्टॉल किया गया -- आपकी पसंद का एक पैकेज मैनेजर (`npm`, `yarn` या `pnpm`) +- A deployed smart contract on a [supported network](/supported-networks/) +- [Node.js](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) ## सबग्राफ कैसे बनाएं ### 1. सबग्राफ Studio में एक सबग्राफ बनाएँ - -[Subgraph Studio](https://thegraph.com/studio/) पर जाएँ और अपने वॉलेट को कनेक्ट करें। - -सबग्राफ Studio आपको Subgraphs बनाने, प्रबंधित करने, तैनात करने और प्रकाशित करने की सुविधा देता है, साथ ही API कुंजी बनाने और प्रबंधित करने की सुविधा भी प्रदान करता है। - -"Create a सबग्राफ" पर क्लिक करें। यह अनुशंसा की जाती है कि सबग्राफ का नाम टाइटल केस में रखा जाए: "सबग्राफ Name Chain Name"। +1. Go to [Subgraph Studio](https://thegraph.com/studio/) +2. Connect your wallet +3. Click "Create a Subgraph" +4. Name it in Title Case: "Subgraph Name Chain Name" ### 2. ग्राफ़ सीएलआई स्थापित करें @@ -37,20 +41,22 @@ Using [yarn](https://yarnpkg.com/): yarn global add @graphprotocol/graph-cli ``` -### अपने सबग्राफ को प्रारंभ करें +Verify install: -> आप अपने विशिष्ट Subgraph के लिए कमांड Subgraph Studio के Subgraph पेज पर पा सकते हैं। +```sh +graph --version +``` -`graph init` कमांड स्वचालित रूप से आपके contract की घटनाओं के आधार पर एक सबग्राफ का खाका तैयार करेगा। +### अपने सबग्राफ को प्रारंभ करें -निम्नलिखित कमांड एक मौजूदा contract से आपका सबग्राफ प्रारंभ करता है: +> You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/). + +The following command initializes your Subgraph from an existing contract and indexes events: ```sh graph init ``` -यदि आपका contract उस ब्लॉकस्कैनर पर वेरीफाई किया गया है जहाँ यह डिप्लॉय किया गया है (जैसे [Etherscan](https://etherscan.io/)), तो ABI अपने आप CLI में क्रिएट हो जाएगा। - जब आप अपने सबग्राफ को प्रारंभ करते हैं, तो CLI आपसे निम्नलिखित जानकारी मांगेगा: - **प्रोटोकॉल**: वह प्रोटोकॉल चुनें जिससे आपका सबग्राफ डेटा को indexing करेगा। @@ -59,19 +65,17 @@ graph init - \*\*Ethereum नेटवर्क (वैकल्पिक): आपको यह निर्दिष्ट करने की आवश्यकता हो सकती है कि आपका Subgraph किस EVM-संगत नेटवर्क से डेटा को इंडेक्स करेगा। - **contract एड्रेस**: उस स्मार्ट contract एड्रेस को खोजें जिससे आप डेटा क्वेरी करना चाहते हैं। - **ABI**: यदि ABI स्वतः नहीं भरा जाता है, तो आपको इसे JSON फ़ाइल के रूप में मैन्युअल रूप से इनपुट करना होगा। -- **Start Block**: आपको स्टार्ट ब्लॉक इनपुट करना चाहिए ताकि ब्लॉकचेन डेटा की सबग्राफ indexing को ऑप्टिमाइज़ किया जा सके। स्टार्ट ब्लॉक को खोजने के लिए उस ब्लॉक को ढूंढें जहां आपका contract डिप्लॉय किया गया था। +- **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. - **contract का नाम**: अपने contract का नाम दर्ज करें। - **contract इवेंट्स को entities के रूप में इंडेक्स करें**: इसे true पर सेट करने की सलाह दी जाती है, क्योंकि यह हर उत्सर्जित इवेंट के लिए स्वचालित रूप से आपके सबग्राफ में मैपिंग जोड़ देगा। - **एक और contract जोड़ें** (वैकल्पिक): आप एक और contract जोड़ सकते हैं। -इसका एक उदाहरण देखने के लिए निम्नलिखित स्क्रीनशॉट देखें कि जब आप अपना सबग्राफ इनिशियलाइज़ करते हैं तो क्या अपेक्षा करें: +See the following screenshot for an example of what to expect when initializing your Subgraph: ![सबग्राफ कमांड](/img/CLI-Example.png) ### अपना सबग्राफ संपादित करें -`init` कमांड पिछले चरण में एक प्रारंभिक सबग्राफ बनाता है जिसे आप अपने सबग्राफ को बनाने के लिए एक शुरुआती बिंदु के रूप में उपयोग कर सकते हैं। - सबग्राफ में परिवर्तन करते समय, आप मुख्य रूप से तीन फ़ाइलों के साथ काम करेंगे: - मैनिफेस्ट (`subgraph.yaml`) - यह निर्धारित करता है कि आपका सबग्राफ किन डेटा स्रोतों को इंडेक्स करेगा। @@ -82,9 +86,7 @@ graph init ### 5. अपना Subgraph डिप्लॉय करें -> तैनाती करना प्रकाशन के समान नहीं है। - -जब आप किसी सबग्राफ को तैनात (deploy) करते हैं, तो आप इसे [सबग्राफ Studio](https://thegraph.com/studio/) पर अपलोड करते हैं, जहाँ आप इसका परीक्षण, स्टेजिंग और समीक्षा कर सकते हैं। तैनात किए गए सबग्राफ का Indexing [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/) द्वारा किया जाता है, जो Edge & Node द्वारा संचालित एक एकल Indexer है, न कि The Graph Network में मौजूद कई विकेंद्रीकृत Indexers द्वारा। एक तैनात (deployed) सबग्राफ का उपयोग निःशुल्क है, यह दर-सीमित (rate-limited) होता है, सार्वजनिक रूप से दृश्य (visible) नहीं होता, और इसे मुख्य रूप से विकास (development), स्टेजिंग और परीक्षण (testing) उद्देश्यों के लिए डिज़ाइन किया गया है। +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. 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. एक बार जब आपका सबग्राफ लिखा जा चुका हो, तो निम्नलिखित कमांड चलाएँ: @@ -107,8 +109,6 @@ graph deploy ``` ```` -The CLI एक संस्करण लेबल के लिए पूछेगा। यह दृढ़ता से सिफारिश की जाती है कि [semantic versioning](https://semver.org/) का उपयोग करें, जैसे 0.0.1। - ### 6. अपने सबग्राफ की समीक्षा करें यदि आप अपना सबग्राफ प्रकाशित करने से पहले उसका परीक्षण करना चाहते हैं, तो आप [सबग्राफ Studio](https://thegraph.com/studio/) का उपयोग करके निम्नलिखित कर सकते हैं: @@ -125,55 +125,13 @@ The CLI एक संस्करण लेबल के लिए पूछे - यह आपके सबग्राफ को विकेंद्रीकृत [Indexers](/indexing/overview/) द्वारा The Graph Network पर अनुक्रमित किए जाने के लिए उपलब्ध कराता है। - यह आपकी दर सीमा को हटा देता है और आपके सबग्राफ को [Graph Explorer](https://thegraph.com/explorer/) में सार्वजनिक रूप से खोजने योग्य और क्वेरी करने योग्य बनाता है। -- यह आपके सबग्राफ को [Curators](/resources/roles/curating/) के लिए उपलब्ध कराता है ताकि वे इसे क्यूरेट कर सकें। - -> अधिक मात्रा में GRT को आप और अन्य लोग आपके सबग्राफ पर क्यूरेट करते हैं, तो अधिक Indexers को आपके सबग्राफ को इंडेक्स करने के लिए प्रोत्साहित किया जाएगा, जिससे सेवा की गुणवत्ता में सुधार होगा, विलंबता (latency) कम होगी, और आपके सबग्राफ के लिए नेटवर्क की पुनरावृत्ति (redundancy) बढ़ेगी। - -#### Subgraph Studio से प्रकाशित +- It makes your Subgraph available for [Curators](/resources/roles/curating/) to add curation signal. -अपने सबग्राफ को प्रकाशित करने के लिए, डैशबोर्ड में Publish बटन पर क्लिक करें। +To publish your Subgraph, click the Publish button in the dashboard and select your network. ![सबग्राफ Studio पर एक Subgraph प्रकाशित करें](/img/publish-sub-transfer.png) -अपने सबग्राफ को प्रकाशित करने के लिए उस नेटवर्क का चयन करें, जिसे आप चुनना चाहते हैं। - -#### Publishing from the CLI - -जैसा कि संस्करण 0.73.0 में है, अब आप अपने सबग्राफ को Graph CLI के साथ प्रकाशित कर सकते हैं। - -`graph-cli` खोलें। - -निम्नलिखित कमांड का उपयोग करें: - -```` -```sh -graph codegen && graph build -``` - -Then, - -```sh -graph publish -``` -```` - -3. एक विंडो खुलेगी, जिससे आप अपना वॉलेट कनेक्ट कर सकते हैं, मेटाडेटा जोड़ सकते हैं और अपने फ़ाइनलाइज़ किए गए सबग्राफ को अपनी पसंद के नेटवर्क पर डिप्लॉय कर सकते हैं। - -![cli-ui](/img/cli-ui.png) - -अपने परिनियोजन को अनुकूलित करने के लिए, [Publishing a सबग्राफ](/subgraphs/developing/publishing/publishing-a-subgraph/) देखें। - -#### सिग्नल को अपने Subgraph में जोड़ना - -1. Indexers को अपने सबग्राफ से क्वेरी करने के लिए आकर्षित करने हेतु, आपको इसमें GRT क्यूरेशन सिग्नल जोड़ना चाहिए। - - - यह कार्रवाई सेवा की गुणवत्ता में सुधार करती है, विलंबता को कम करती है, और आपके सबग्राफ के लिए नेटवर्क की पुनरावृत्ति और उपलब्धता को बढ़ाती है। - -2. यदि इंडेक्सिंग पुरस्कारों के लिए योग्य हैं, तो Indexers संकेतित राशि के आधार पर GRT पुरस्कार प्राप्त करते हैं। - - - यह अनुशंसा की जाती है कि कम से कम 3,000 GRT को क्यूरेट किया जाए ताकि 3 Indexers को आकर्षित किया जा सके। सबग्राफ फीचर उपयोग और समर्थित नेटवर्क के आधार पर पुरस्कार पात्रता की जांच करें। - -Curation के बारे में और जानने के लिए, [Curating](/resources/roles/curating/) पढ़ें. +> It is recommended that you curate your own Subgraph with at least 3,000 GRT to incentivize indexing. गैस लागत बचाने के लिए, आप अपने सबग्राफ को उसी लेनदेन में प्रकाशित कर सकते हैं जिसमें आप इसे क्यूरेट कर रहे हैं, बस इस विकल्प का चयन करें: From 69db73b13caeb69ddc913cf0c6a0a95244b1c0a3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:41 -0400 Subject: [PATCH 113/290] New translations overview.mdx (Romanian) --- website/src/pages/ro/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/ro/indexing/overview.mdx b/website/src/pages/ro/indexing/overview.mdx index 4a980db27f12..0b9b31f5d22d 100644 --- a/website/src/pages/ro/indexing/overview.mdx +++ b/website/src/pages/ro/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From c01c8ddb28e0c51d9fbdee4deffd127cc985f9b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:43 -0400 Subject: [PATCH 114/290] New translations overview.mdx (French) --- website/src/pages/fr/indexing/overview.mdx | 48 +++++++++++----------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/website/src/pages/fr/indexing/overview.mdx b/website/src/pages/fr/indexing/overview.mdx index 1c0d0f9c7221..be87dbd79d9a 100644 --- a/website/src/pages/fr/indexing/overview.mdx +++ b/website/src/pages/fr/indexing/overview.mdx @@ -111,11 +111,11 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. | Configuration | Postgres
(CPUs) | Postgres
(mémoire en Go) | Postgres
(disque en To) | VMs
(CPUs) | VMs
(mémoire en Go) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Petit | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Moyen | 16 | 64 | 2 | 32 | 64 | -| Grand | 72 | 468 | 3.5 | 48 | 184 | +| ------------- | :------------------: | :---------------------------: | :--------------------------: | :-------------: | :----------------------: | +| Petit | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Moyen | 16 | 64 | 2 | 32 | 64 | +| Grand | 72 | 468 | 3.5 | 48 | 184 | ### Quelles sont les précautions de sécurité de base qu'un Indexeur doit prendre ? @@ -147,26 +147,26 @@ Remarque : pour permettre une mise à l'échelle souple, il est recommandé de s #### Nœud de The Graph -| Port | Objectif | Routes | Argument CLI | Variable d'Environment | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(pour gérer les déploiements) | / | \--admin-port | - | -| 8030 | API du statut de l'indexation des subgraphs | /graphql | \--index-node-port | - | -| 8040 | Métriques Prometheus | /metrics | \--metrics-port | - | +| Port | Objectif | Routes | Argument CLI | Variable d'Environment | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | ---------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(pour gérer les déploiements) | / | \--admin-port | - | +| 8030 | API du statut de l'indexation des subgraphs | /graphql | \--index-node-port | - | +| 8040 | Métriques Prometheus | /metrics | \--metrics-port | - | #### Service d'Indexeur -| Port | Objectif | Routes | Argument CLI | Variable D'environment | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Métriques Prometheus | /metrics | \--metrics-port | - | +| Port | Objectif | Routes | Argument CLI | Variable D'environment | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Métriques Prometheus | /metrics | \--metrics-port | - | #### Indexer Agent -| Port | Objectif | Routes | Argument CLI | Variable D'environment | -| ---- | ---------------------------- | ------ | -------------------------- | --------------------------------------- | -| 8000 | API de gestion des Indexeurs | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | +| Port | Objectif | Routes | Argument CLI | Variable D'environment | +| ---- | ---------------------------- | ------ | -------------------------- | ----------------------------------------- | +| 8000 | API de gestion des Indexeurs | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | ### Mise en place d'une infrastructure de serveurs à l'aide de Terraform sur Google Cloud @@ -729,11 +729,11 @@ default => 0.1 * $SYSTEM_LOAD; Exemple de calcul des coûts d'une requête à l'aide du modèle ci-dessus : -| Requête | Prix | -| ---------------------------------------------------------------------------- | ------- | -| { pairs(skip: 5000) { id } } | 0.5 GRT | -| { tokens { symbol } } | 0.1 GRT | -| { pairs(skip: 5000) { id } tokens { symbol } } | 0.6 GRT | +| Requête | Prix | +| ------------------------------------------------------------------------------ | ------- | +| { pairs(skip: 5000) { id } } | 0.5 GRT | +| { tokens { symbol } } | 0.1 GRT | +| { pairs(skip: 5000) { id } tokens { symbol } } | 0.6 GRT | #### Application du modèle de coût From f66f3810c57d7567c9dbf60c1d0c46c209385527 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:44 -0400 Subject: [PATCH 115/290] New translations overview.mdx (Spanish) --- website/src/pages/es/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/es/indexing/overview.mdx b/website/src/pages/es/indexing/overview.mdx index cf592d9ad7e4..582962c94c0d 100644 --- a/website/src/pages/es/indexing/overview.mdx +++ b/website/src/pages/es/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 8cebae4d5cfb5555935934c97d045a5feee95347 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:46 -0400 Subject: [PATCH 116/290] New translations overview.mdx (Arabic) --- website/src/pages/ar/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/ar/indexing/overview.mdx b/website/src/pages/ar/indexing/overview.mdx index 200a3a6a64e5..f543bca55f32 100644 --- a/website/src/pages/ar/indexing/overview.mdx +++ b/website/src/pages/ar/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 04c8dbb4c24c5b2ee7e8ad0309f0a0af25e14fe7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:47 -0400 Subject: [PATCH 117/290] New translations overview.mdx (Czech) --- website/src/pages/cs/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/cs/indexing/overview.mdx b/website/src/pages/cs/indexing/overview.mdx index 8acf4fdf72a9..47b88923efa8 100644 --- a/website/src/pages/cs/indexing/overview.mdx +++ b/website/src/pages/cs/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Uzel Graf -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 6f1ca15c01b5f3b1ec54c41249969eb030910d35 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:49 -0400 Subject: [PATCH 118/290] New translations overview.mdx (German) --- website/src/pages/de/indexing/overview.mdx | 38 +++++++++++----------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/website/src/pages/de/indexing/overview.mdx b/website/src/pages/de/indexing/overview.mdx index 4635fbb7f2b9..f6128f144663 100644 --- a/website/src/pages/de/indexing/overview.mdx +++ b/website/src/pages/de/indexing/overview.mdx @@ -111,11 +111,11 @@ Indexierer können sich durch die Anwendung fortgeschrittener Techniken für die - **Large** - Vorbereitet, um alle derzeit verwendeten Subgraphen zu indizieren und Anfragen für den entsprechenden Verkehr zu bedienen. | Konfiguration | Postgres
(CPUs) | Postgres
(Speicher in GB) | Postgres
(Festplatte in TB) | VMs
(CPUs) | VMs
(Speicher in GB) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| ------------- | :------------------: | :----------------------------: | :------------------------------: | :-------------: | :-----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### Was sind einige grundlegende Sicherheitsvorkehrungen, die ein Indexierer treffen sollte? @@ -147,26 +147,26 @@ Hinweis: Um eine flexible Skalierung zu unterstützen, wird empfohlen, Abfrage- #### Graph-Knoten -| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP Server
(für Subgraph-Abfragen) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(für Subgraphen-Abonnements) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(zum Verwalten von Deployments) | / | \--admin-port | - | -| 8030 | Status der Indizierung von Subgraphen API | /graphql | \--index-node-port | - | -| 8040 | Prometheus-Metriken | /metrics | \--metrics-port | - | +| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | +| ---- | ------------------------------------------------ | ---------------------------------------------- | ------------------ | ----------------- | +| 8000 | GraphQL HTTP Server
(für Subgraph-Abfragen) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(für Subgraphen-Abonnements) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(zum Verwalten von Deployments) | / | \--admin-port | - | +| 8030 | Status der Indizierung von Subgraphen API | /graphql | \--index-node-port | - | +| 8040 | Prometheus-Metriken | /metrics | \--metrics-port | - | #### Indexer-Service -| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP Server
(für bezahlte Subgraph-Abfragen) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus-Metriken | /metrics | \--metrics-port | - | +| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | +| ---- | --------------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP Server
(für bezahlte Subgraph-Abfragen) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus-Metriken | /metrics | \--metrics-port | - | #### Indexierer-Agent -| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | -| ---- | ----------------------- | ------ | -------------------------- | --------------------------------------- | -| 8000 | Indexer-Verwaltungs-API | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | +| Port | Verwendungszweck | Routen | CLI-Argument | Umgebungsvariable | +| ---- | ------------------------------- | ------ | -------------------------- | --------------------------------------- | +| 8000 | Indexer-Verwaltungs-API | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | ### Einrichten einer Server-Infrastruktur mit Terraform auf Google Cloud From 0f9ec69c9574cad6f838f285c6d1c3f643b2e801 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:50 -0400 Subject: [PATCH 119/290] New translations overview.mdx (Italian) --- website/src/pages/it/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/it/indexing/overview.mdx b/website/src/pages/it/indexing/overview.mdx index 371d0f48cf9a..4fd39637b806 100644 --- a/website/src/pages/it/indexing/overview.mdx +++ b/website/src/pages/it/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 023af7e324ace16537d669a95683769a1645e7a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:51 -0400 Subject: [PATCH 120/290] New translations overview.mdx (Japanese) --- website/src/pages/ja/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/ja/indexing/overview.mdx b/website/src/pages/ja/indexing/overview.mdx index 25b94c36ca88..df7af3cc4dfd 100644 --- a/website/src/pages/ja/indexing/overview.mdx +++ b/website/src/pages/ja/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### グラフノード -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 2298aea048b5fd7a4911e43235833df96bf66288 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:53 -0400 Subject: [PATCH 121/290] New translations overview.mdx (Korean) --- website/src/pages/ko/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/ko/indexing/overview.mdx b/website/src/pages/ko/indexing/overview.mdx index 4a980db27f12..0b9b31f5d22d 100644 --- a/website/src/pages/ko/indexing/overview.mdx +++ b/website/src/pages/ko/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From f6780904126fa8a62e8e27b3bf1d646baca6f61a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:54 -0400 Subject: [PATCH 122/290] New translations overview.mdx (Dutch) --- website/src/pages/nl/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/nl/indexing/overview.mdx b/website/src/pages/nl/indexing/overview.mdx index 89c13c8ab279..891a4b0dba3d 100644 --- a/website/src/pages/nl/indexing/overview.mdx +++ b/website/src/pages/nl/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 464a4af9bd1d30f4d5284b37dc588cf773793e2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:56 -0400 Subject: [PATCH 123/290] New translations overview.mdx (Polish) --- website/src/pages/pl/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/pl/indexing/overview.mdx b/website/src/pages/pl/indexing/overview.mdx index 4a980db27f12..0b9b31f5d22d 100644 --- a/website/src/pages/pl/indexing/overview.mdx +++ b/website/src/pages/pl/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 44a705e4e14b122a623f08957e293549f0fff6a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:57 -0400 Subject: [PATCH 124/290] New translations overview.mdx (Portuguese) --- website/src/pages/pt/indexing/overview.mdx | 38 +++++++++++----------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/website/src/pages/pt/indexing/overview.mdx b/website/src/pages/pt/indexing/overview.mdx index 02343b809f03..a97272ae9669 100644 --- a/website/src/pages/pt/indexing/overview.mdx +++ b/website/src/pages/pt/indexing/overview.mdx @@ -111,11 +111,11 @@ Os Indexadores podem se diferenciar ao aplicar técnicas avançadas para decidir - **Grande** — Preparado para indexar todos os subgraphs usados atualmente e servir solicitações para o tráfego relacionado. | Configuração | Postgres
(CPUs) | Postgres
(memória em GBs) | Postgres
(disco em TBs) | VMs
(CPUs) | VMs
(memória em GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Pequeno | 4 | 8 | 1 | 4 | 16 | -| Normal | 8 | 30 | 1 | 12 | 48 | -| Médio | 16 | 64 | 2 | 32 | 64 | -| Grande | 72 | 468 | 3.5 | 48 | 184 | +| ------------ | :------------------: | :----------------------------: | :--------------------------: | :-------------: | :-----------------------: | +| Pequeno | 4 | 8 | 1 | 4 | 16 | +| Normal | 8 | 30 | 1 | 12 | 48 | +| Médio | 16 | 64 | 2 | 32 | 64 | +| Grande | 72 | 468 | 3.5 | 48 | 184 | ### Há alguma precaução básica de segurança que um Indexador deve tomar? @@ -147,26 +147,26 @@ Observe: Para apoiar o escalamento ágil, recomendamos que assuntos de query e d #### Graph Node -| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | -| --- | --- | --- | --- | --- | -| 8000 | Servidor HTTP GraphQL
(para queries de subgraph) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | WS GraphQL
(para inscrições a subgraphs) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(para gerir implantações) | / | \--admin-port | - | -| 8030 | API de estado de indexação do subgraph | /graphql | \--index-node-port | - | -| 8040 | Métricas Prometheus | /metrics | \--metrics-port | - | +| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | +| ----- | ----------------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | Servidor HTTP GraphQL
(para queries de subgraph) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | WS GraphQL
(para inscrições a subgraphs) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(para gerir implantações) | / | \--admin-port | - | +| 8030 | API de estado de indexação do subgraph | /graphql | \--index-node-port | - | +| 8040 | Métricas Prometheus | /metrics | \--metrics-port | - | #### Serviço Indexador -| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | -| --- | --- | --- | --- | --- | -| 7600 | Servidor HTTP GraphQL
(para queries pagos de subgraph) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Métricas Prometheus | /metrics | \--metrics-port | - | +| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | +| ----- | ----------------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | Servidor HTTP GraphQL
(para queries pagos de subgraph) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Métricas Prometheus | /metrics | \--metrics-port | - | #### Agente Indexador -| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | -| ----- | -------------------------- | ----- | -------------------------- | --------------------------------------- | -| 8000 | API de gestão de Indexador | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | +| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente | +| ----- | -------------------------- | ------ | -------------------------- | --------------------------------------- | +| 8000 | API de gestão de Indexador | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | ### Como preparar uma infraestrutura de servidor com o Terraform no Google Cloud From 1c94a4289236097aae9de5535430b9f22ccd61fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:23:59 -0400 Subject: [PATCH 125/290] New translations overview.mdx (Russian) --- website/src/pages/ru/indexing/overview.mdx | 46 +++++++++++----------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/website/src/pages/ru/indexing/overview.mdx b/website/src/pages/ru/indexing/overview.mdx index 30c9ec939dcd..f66166d8c7af 100644 --- a/website/src/pages/ru/indexing/overview.mdx +++ b/website/src/pages/ru/indexing/overview.mdx @@ -110,12 +110,12 @@ query indexerAllocations { - **Средние** – производительный Индексатор, поддерживающий 100 субграфов и 200–500 запросов в секунду. - **Высокие** – готов индексировать все используемые субграфы и обрабатывать соответствующий трафик запросов. -| Настройка | Postgres
(ЦП) | Postgres
(память в ГБ) | Postgres
(диск в ТБ) | VMs
(ЦП) | VMs
(память в ГБ) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Низкая | 4 | 8 | 1 | 4 | 16 | -| Стандартная | 8 | 30 | 1 | 12 | 48 | -| Средняя | 16 | 64 | 2 | 32 | 64 | -| Высокая | 72 | 468 | 3.5 | 48 | 184 | +| Настройка | Postgres
(ЦП) | Postgres
(память в ГБ) | Postgres
(диск в ТБ) | VMs
(ЦП) | VMs
(память в ГБ) | +| ----------- | :----------------: | :-------------------------: | :-----------------------: | :-----------: | :--------------------: | +| Низкая | 4 | 8 | 1 | 4 | 16 | +| Стандартная | 8 | 30 | 1 | 12 | 48 | +| Средняя | 16 | 64 | 2 | 32 | 64 | +| Высокая | 72 | 468 | 3.5 | 48 | 184 | ### Какие основные меры безопасности следует предпринять Индексатору? @@ -147,20 +147,20 @@ query indexerAllocations { #### Graph Node -| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP-сервер
(для запросов к Субграфу) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(для подписок на Субграф) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(для управления развертываниями) | / | \--admin-port | - | -| 8030 | API статуса индексирования Субграфа | /graphql | \--index-node-port | - | -| 8040 | Метрики Prometheus | /metrics | \--metrics-port | - | +| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | +| ---- | -------------------------------------------------- | ---------------------------------------------- | ------------------ | ---------------- | +| 8000 | GraphQL HTTP-сервер
(для запросов к Субграфу) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(для подписок на Субграф) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(для управления развертываниями) | / | \--admin-port | - | +| 8030 | API статуса индексирования Субграфа | /graphql | \--index-node-port | - | +| 8040 | Метрики Prometheus | /metrics | \--metrics-port | - | #### Сервис Индексатора -| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP-сервер
(для платных запросов к Субграфу) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Метрики Prometheus | /metrics | \--metrics-port | - | +| Порт | Назначение | Маршруты | Аргумент CLI | Переменная среды | +| ---- | ---------------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP-сервер
(для платных запросов к Субграфу) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Метрики Prometheus | /metrics | \--metrics-port | - | #### Агент Индексатора @@ -391,7 +391,7 @@ graph-indexer-service start ... # Агент Индексатора graph-indexer-agent start ... -#CLI Индексатора +#CLI Индексатора #Проброс порта Вашего pod-агента, если используется Kubernetes kubectl port-forward pod/POD_ID 18000:8000 graph indexer connect http://localhost:18000/ @@ -729,11 +729,11 @@ default => 0.1 * $SYSTEM_LOAD; Пример вычисления запросов с использованием вышеуказанной модели: -| Запрос | Цена | -| ---------------------------------------------------------------------------- | ------- | -| { pairs(skip: 5000) { id } } | 0.5 GRT | -| { tokens { symbol } } | 0.1 GRT | -| { pairs(skip: 5000) { id } tokens { symbol } } | 0.6 GRT | +| Запрос | Цена | +| ----------------------------------------------------------------------------- | ------- | +| { pairs(skip: 5000) { id } } | 0.5 GRT | +| { tokens { symbol } } | 0.1 GRT | +| { pairs(skip: 5000) { id } tokens { symbol } } | 0.6 GRT | #### Применение модели стоимости From dfad86c84ac5da6eac097b42608a508f1712c93b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:00 -0400 Subject: [PATCH 126/290] New translations overview.mdx (Swedish) --- website/src/pages/sv/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/sv/indexing/overview.mdx b/website/src/pages/sv/indexing/overview.mdx index b355374c5949..3cbd4c66ccf5 100644 --- a/website/src/pages/sv/indexing/overview.mdx +++ b/website/src/pages/sv/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graf Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From f7fbc533febc8f175a40e0c9bb6355169a19eb57 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:01 -0400 Subject: [PATCH 127/290] New translations overview.mdx (Turkish) --- website/src/pages/tr/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/tr/indexing/overview.mdx b/website/src/pages/tr/indexing/overview.mdx index 6a9d93397c39..fdaed8832e1b 100644 --- a/website/src/pages/tr/indexing/overview.mdx +++ b/website/src/pages/tr/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 7903a40db2fcb93f3b1e74d8b4acdbfb6c3b59a1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:02 -0400 Subject: [PATCH 128/290] New translations overview.mdx (Ukrainian) --- website/src/pages/uk/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/uk/indexing/overview.mdx b/website/src/pages/uk/indexing/overview.mdx index 1ef3973c70cd..2914c64219ea 100644 --- a/website/src/pages/uk/indexing/overview.mdx +++ b/website/src/pages/uk/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From e064f2b54148c4de6c2b6fa6f3f3eb693d2a8a81 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:04 -0400 Subject: [PATCH 129/290] New translations overview.mdx (Chinese Simplified) --- website/src/pages/zh/indexing/overview.mdx | 40 +++++++++++----------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/website/src/pages/zh/indexing/overview.mdx b/website/src/pages/zh/indexing/overview.mdx index a20d5cb185d4..7f85df5b083a 100644 --- a/website/src/pages/zh/indexing/overview.mdx +++ b/website/src/pages/zh/indexing/overview.mdx @@ -111,11 +111,11 @@ query indexerAllocations { - **大型** -准备对当前使用的所有子图进行索引，并为相关流量的请求提供服务。 | 设置 | Postgres
(CPUs) | Postgres
(内存 GBs) | Postgres
(硬盘TBs) | VMs
(CPUs) | VMs
(内存 GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| 小型 | 4 | 8 | 1 | 4 | 16 | -| 标准 | 8 | 30 | 1 | 12 | 48 | -| 中型 | 16 | 64 | 2 | 32 | 64 | -| 大型 | 72 | 468 | 3.5 | 48 | 184 | +| -- | :------------------: | :--------------------: | :-------------------: | :-------------: | :---------------: | +| 小型 | 4 | 8 | 1 | 4 | 16 | +| 标准 | 8 | 30 | 1 | 12 | 48 | +| 中型 | 16 | 64 | 2 | 32 | 64 | +| 大型 | 72 | 468 | 3.5 | 48 | 184 | ### 索引人应该采取哪些基本的安全防范措施？ @@ -147,26 +147,26 @@ query indexerAllocations { #### Graph 节点 -| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
（用于子图查询） | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
（用于子图订阅） | /subgraphs/id/...
/subgraphs/name/.../…… | \--ws-port | - | -| 8020 | JSON-RPC
（用于管理部署） | / | \--admin-port | - | -| 8030 | 子图索引状态 API | /graphql | \--index-node-port | - | -| 8040 | Prometheus 指标 | /metrics | \--metrics-port | - | +| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | +| ---- | --------------------------------- | ------------------------------------------------ | ------------------ | ----- | +| 8000 | GraphQL HTTP server
（用于子图查询） | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
（用于子图订阅） | /subgraphs/id/...
/subgraphs/name/.../…… | \--ws-port | - | +| 8020 | JSON-RPC
（用于管理部署） | / | \--admin-port | - | +| 8030 | 子图索引状态 API | /graphql | \--index-node-port | - | +| 8040 | Prometheus 指标 | /metrics | \--metrics-port | - | #### 索引人服务 -| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP 服务器
（用于付费子图查询） | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus 指标 | /metrics | \--metrics-port | - | +| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 | +| ---- | --------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP 服务器
（用于付费子图查询） | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus 指标 | /metrics | \--metrics-port | - | #### 索引人代理 -| 端口 | 目的 | 路径 | CLI 参数 | 环境 变量 | -| ---- | -------------- | ---- | ------------------- | --------------------------------------- | -| 8000 | 索引人管理 API | / | \--索引人-管理-端口 | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | +| 端口 | 目的 | 路径 | CLI 参数 | 环境 变量 | +| ---- | ----------------- | ------ | ----------------------- | --------------------------------------- | +| 8000 | 索引人管理 API | / | \--索引人-管理-端口 | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | ### 在谷歌云上使用 Terraform 建立服务器基础设施 @@ -729,7 +729,7 @@ default => 0.1 * $SYSTEM_LOAD; 使用上述模型的查询成本计算示例： -| 查询 | 价格 | +| 查询 | 价格 | | ---------------------------------------------------------------------------- | ------- | | { pairs(skip: 5000) { id } } | 0.5 GRT | | { tokens { symbol } } | 0.1 GRT | From 5fb423f8145537f08e28e7e7c7ad6ee7899787c0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:05 -0400 Subject: [PATCH 130/290] New translations overview.mdx (Urdu (Pakistan)) --- website/src/pages/ur/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/ur/indexing/overview.mdx b/website/src/pages/ur/indexing/overview.mdx index 8258c63fa6f1..e2a11f30cfbf 100644 --- a/website/src/pages/ur/indexing/overview.mdx +++ b/website/src/pages/ur/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### گراف نوڈ -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 697166c516a167b807ecd836c547bdcb7e78e84a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:07 -0400 Subject: [PATCH 131/290] New translations overview.mdx (Vietnamese) --- website/src/pages/vi/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/vi/indexing/overview.mdx b/website/src/pages/vi/indexing/overview.mdx index 034b74623eaf..3ffdf00a4346 100644 --- a/website/src/pages/vi/indexing/overview.mdx +++ b/website/src/pages/vi/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### Graph Node -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 976de55f696ed3d7f00d6383a5c7f011d3382a11 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:08 -0400 Subject: [PATCH 132/290] New translations overview.mdx (Marathi) --- website/src/pages/mr/indexing/overview.mdx | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/mr/indexing/overview.mdx b/website/src/pages/mr/indexing/overview.mdx index 9d78f7612f01..ce44b1b7a1d4 100644 --- a/website/src/pages/mr/indexing/overview.mdx +++ b/website/src/pages/mr/indexing/overview.mdx @@ -110,12 +110,12 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. - **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. -| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| Small | 4 | 8 | 1 | 4 | 16 | -| Standard | 8 | 30 | 1 | 12 | 48 | -| Medium | 16 | 64 | 2 | 32 | 64 | -| Large | 72 | 468 | 3.5 | 48 | 184 | +| Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | +| -------- | :------------------: | :---------------------------: | :-------------------------: | :-------------: | :----------------------: | +| Small | 4 | 8 | 1 | 4 | 16 | +| Standard | 8 | 30 | 1 | 12 | 48 | +| Medium | 16 | 64 | 2 | 32 | 64 | +| Large | 72 | 468 | 3.5 | 48 | 184 | ### What are some basic security precautions an Indexer should take? @@ -147,20 +147,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer #### आलेख नोड -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | -------------------- | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for Subgraph subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Service -| Port | Purpose | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | +| Port | Purpose | Routes | CLI Argument | Environment Variable | +| ---- | ---------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(for paid Subgraph queries) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus metrics | /metrics | \--metrics-port | - | #### Indexer Agent From 9ce0635ca1f338c0f08da3b18bd6a953128b5892 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:09 -0400 Subject: [PATCH 133/290] New translations overview.mdx (Hindi) --- website/src/pages/hi/indexing/overview.mdx | 48 +++++++++++----------- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/website/src/pages/hi/indexing/overview.mdx b/website/src/pages/hi/indexing/overview.mdx index 38a778b97854..baf5fa61aacd 100644 --- a/website/src/pages/hi/indexing/overview.mdx +++ b/website/src/pages/hi/indexing/overview.mdx @@ -60,7 +60,7 @@ query indexerAllocations { Etherscan का उपयोग करके `getRewards()` कॉल करें: - [ईथरस्कैन इंटरफेस पर रिवॉर्ड्स contract](https://etherscan.io/address/0x9Ac758AB77733b4150A901ebd659cbF8cB93ED66#readProxyContract) पर जाएं। -- `getRewards()` को कॉल करने के लिए: +- `getRewards()` को कॉल करने के लिए: - **9. getRewards** ड्रॉपडाउन का विस्तार करें। - इनपुट में **allocationID** दर्ज करें। - कृपया **Query** बटन पर क्लिक करें। @@ -111,11 +111,11 @@ Indexers उन्नत तकनीकों को लागू करके - **बड़ा **- वर्तमान में उपयोग किए जा रहे सभी सबग्राफ को इंडेक्स करने और संबंधित ट्रैफ़िक के लिए अनुरोधों को सर्व करने के लिए तैयार। | सेटअप | Postgres
(CPUs) | Postgres
(मेमोरी in GBs) | Postgres
(डिस्क in TBs) | VMs
(CPUs) | VMs
(मेमोरी in GBs) | -| --- | :-: | :-: | :-: | :-: | :-: | -| छोटा | 4 | 8 | 1 | 4 | 16 | -| मानक | 8 | 30 | 1 | 12 | 48 | -| मध्यम | 16 | 64 | 2 | 32 | 64 | -| बड़ा | 72 | 468 | 3.5 | 48 | 184 | +| ----- | :------------------: | :---------------------------: | :--------------------------: | :-------------: | :----------------------: | +| छोटा | 4 | 8 | 1 | 4 | 16 | +| मानक | 8 | 30 | 1 | 12 | 48 | +| मध्यम | 16 | 64 | 2 | 32 | 64 | +| बड़ा | 72 | 468 | 3.5 | 48 | 184 | ### कोई Indexer को कौन-कौन सी बुनियादी सुरक्षा सावधानियाँ बरतनी चाहिए? @@ -147,26 +147,26 @@ Indexer के इंफ्रास्ट्रक्चर के केंद #### Graph Node -| पोर्ट | उद्देश्य | रूट्स | आर्गुमेंट्स | पर्यावरण वेरिएबल्स | -| --- | --- | --- | --- | --- | -| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | -| 8001 | GraphQL WS
(for सबग्राफ subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | -| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | -| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | -| 8040 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | +| पोर्ट | उद्देश्य | रूट्स | आर्गुमेंट्स | पर्यावरण वेरिएबल्स | +| ----- | ----------------------------------------------- | ---------------------------------------------- | ------------------ | ------------------ | +| 8000 | GraphQL HTTP server
(for Subgraph queries) | /subgraphs/id/...
/subgraphs/name/.../... | \--http-port | - | +| 8001 | GraphQL WS
(for सबग्राफ subscriptions) | /subgraphs/id/...
/subgraphs/name/.../... | \--ws-port | - | +| 8020 | JSON-RPC
(for managing deployments) | / | \--admin-port | - | +| 8030 | Subgraph indexing status API | /graphql | \--index-node-port | - | +| 8040 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | #### Indexer सेवा -| पोर्ट | उद्देश्य | Routes | CLI Argument | Environment Variable | -| --- | --- | --- | --- | --- | -| 7600 | GraphQL HTTP server
(भुगतान किए गए सबग्राफ क्वेरीज़ के लिए) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | -| 7300 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | +| पोर्ट | उद्देश्य | Routes | CLI Argument | Environment Variable | +| ----- | ---------------------------------------------------------------- | ----------------------------------------------------------- | --------------- | ---------------------- | +| 7600 | GraphQL HTTP server
(भुगतान किए गए सबग्राफ क्वेरीज़ के लिए) | /subgraphs/id/...
/status
/channel-messages-inbox | \--port | `INDEXER_SERVICE_PORT` | +| 7300 | Prometheus मेट्रिक्स | /metrics | \--metrics-port | - | #### Indexer एजेंट -| पोर्ट | उद्देश्य | Routes | CLI Argument | Environment Variable | -| ----- | ------------------- | ------ | -------------------------- | --------------------------------------- | -| 8000 | Indexer प्रबंधन API | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | +| पोर्ट | उद्देश्य | Routes | CLI Argument | Environment Variable | +| ----- | ----------------------- | ------ | -------------------------- | --------------------------------------- | +| 8000 | Indexer प्रबंधन API | / | \--indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` | ### Google Cloud पर Terraform का उपयोग करके सर्वर अवसंरचना सेटअप करें @@ -178,7 +178,7 @@ Indexer के इंफ्रास्ट्रक्चर के केंद - Kubectl कमांड लाइन टूल - Terraform -#### Google Cloud प्रोजेक्ट बनाएं +#### Google Cloud प्रोजेक्ट बनाएं - Clone करें या [Indexer repository](https://github.com/graphprotocol/indexer) पर जाएं। @@ -525,7 +525,9 @@ graph indexer status #### Indexer प्रबंधन Indexer CLI का उपयोग करके -**Indexer Management API** के साथ इंटरैक्ट करने के लिए सुझाया गया टूल **Indexer CLI** है, जो कि **Graph CLI** का एक एक्सटेंशन है। Indexer agent को एक Indexer से इनपुट की आवश्यकता होती है ताकि वह Indexer की ओर से नेटवर्क के साथ स्वायत्त रूप से इंटरैक्ट कर सके। Indexer agent व्यवहार को परिभाषित करने के लिए **allocation management** मोड और **indexing rules** का उपयोग किया जाता है। Auto mode में, एक Indexer **indexing rules** का उपयोग करके यह तय कर सकता है कि वह किन को इंडेक्स और क्वेरी के लिए सर्व करेगा। इन नियमों को GraphQL API के माध्यम से प्रबंधित किया जाता है, जिसे agent द्वारा सर्व किया जाता है और यह Indexer Management API के रूप में जाना जाता है। Manual mode में, एक Indexer **actions queue** का उपयोग करके allocation actions बना सकता है और उन्हें निष्पादित करने से पहले स्पष्ट रूप से अनुमोदित कर सकता है। Oversight mode में, **indexing rules** का उपयोग **actions queue** को भरने के लिए किया जाता है और इन्हें निष्पादित करने से पहले भी स्पष्ट अनुमोदन की आवश्यकता होती है। +**Indexer Management API** के साथ इंटरैक्ट करने के लिए सुझाया गया टूल **Indexer CLI** है, जो कि **Graph CLI** का एक एक्सटेंशन है। Indexer agent को एक Indexer से इनपुट की आवश्यकता होती है ताकि वह Indexer की ओर से नेटवर्क के साथ स्वायत्त रूप से इंटरैक्ट कर सके। +Indexer agent व्यवहार को परिभाषित करने के लिए **allocation management** मोड और **indexing rules** का उपयोग किया जाता है। Auto mode में, एक Indexer **indexing rules** का उपयोग करके यह तय कर सकता है कि वह किन को इंडेक्स और क्वेरी के लिए सर्व करेगा। इन नियमों को GraphQL API के माध्यम से प्रबंधित किया जाता है, जिसे agent द्वारा सर्व किया जाता है और यह Indexer Management API के रूप में जाना जाता है। +Manual mode में, एक Indexer **actions queue** का उपयोग करके allocation actions बना सकता है और उन्हें निष्पादित करने से पहले स्पष्ट रूप से अनुमोदित कर सकता है। Oversight mode में, **indexing rules** का उपयोग **actions queue** को भरने के लिए किया जाता है और इन्हें निष्पादित करने से पहले भी स्पष्ट अनुमोदन की आवश्यकता होती है। #### उपयोग @@ -758,7 +760,7 @@ Once an Indexer ने प्रोटोकॉल में GRT को स् 1. ओपन द [Remix app](https://remix.ethereum.org/) एक ब्राउज़र में -2. `File Explorer` में **GraphToken.abi** नामक फ़ाइल बनाएं जिसमें [token ABI](https://raw.githubusercontent.com/graphprotocol/contracts/mainnet-deploy-build/build/abis/GraphToken.json) हो। +2. `File Explorer` में **GraphToken.abi** नामक फ़ाइल बनाएं जिसमें [token ABI](https://raw.githubusercontent.com/graphprotocol/contracts/mainnet-deploy-build/build/abis/GraphToken.json) हो। 3. `GraphToken.abi` चयनित और संपादक में खुला होने पर, Remix इंटरफ़ेस में `Deploy and run transactions` अनुभाग पर स्विच करें। From f6a8c46f9d08a5e0efd0f45000af8ee6a5750a43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:11 -0400 Subject: [PATCH 134/290] New translations explorer.mdx (German) --- website/src/pages/de/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/de/subgraphs/explorer.mdx b/website/src/pages/de/subgraphs/explorer.mdx index 3a386698a7d4..f98024526dd0 100644 --- a/website/src/pages/de/subgraphs/explorer.mdx +++ b/website/src/pages/de/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Erschließen Sie die Welt der Subgraphen und Netzwerkdaten mit [Graph Explorer] (https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Überblick -Graph Explorer besteht aus mehreren Teilen, in denen Sie mit [[Subgraphen]] (https://thegraph.com/explorer?chain=arbitrum-one) interagieren, [[delegieren]] (https://thegraph.com/explorer/delegate?chain=arbitrum-one), [[Teilnehmer]] (https://thegraph.com/explorer/participants?chain=arbitrum-one) einbeziehen, [[Netzwerkinformationen]] (https://thegraph.com/explorer/network?chain=arbitrum-one) anzeigen und auf Ihr Benutzerprofil zugreifen können. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -Nachfolgend finden Sie eine Übersicht über die wichtigsten Funktionen von Graph Explorer. Für zusätzliche Unterstützung können Sie sich den [Graph Explorer Video Guide](/subgraphs/explorer/#video-guide) ansehen. +## Voraussetzungen -### Subgraphen-Seite +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -Nachdem Sie Ihren Subgraph in Subgraph Studio bereitgestellt und veröffentlicht haben, gehen Sie zu [Graph Explorer] (https://thegraph.com/explorer) und klicken Sie auf den Link „[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)“ in der Navigationsleiste, um auf Folgendes zuzugreifen: +## Navigating Graph Explorer -- Ihre eigenen fertigen Subgraphen -- Von anderen veröffentlichte Subgraphen -- Den genauen Subgraphen, den Sie wünschen (basierend auf dem Erstellungsdatum, der Signalmenge oder dem Namen). +### Step 1. Explore Subgraphs -![Explorer Bild 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -Wenn Sie in einen Subgraphen klicken, können Sie Folgendes tun: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Testen Sie Abfragen auf dem Playground und nutzen Sie Netzwerkdetails, um fundierte Entscheidungen zu treffen. -- Signalisieren Sie GRT auf Ihrem eigenen Subgraphen oder den Subgraphen anderer, um die Indexierer auf seine Bedeutung und Qualität aufmerksam zu machen. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - Dies ist von entscheidender Bedeutung, da die Signalisierung eines Subgraphen einen Anreiz darstellt, ihn zu indizieren, was bedeutet, dass er schließlich im Netzwerk auftaucht, um Abfragen zu bedienen. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Bild 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Testen Sie Abfragen auf dem Playground und nutzen Sie Netzwerkdetails, um fundierte Entscheidungen zu treffen. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) Auf der speziellen Seite jedes Subgraphen können Sie Folgendes tun: -- Signal/Un-Signal auf Subgraphen -- Weitere Details wie Diagramme, aktuelle Bereitstellungs-ID und andere Metadaten anzeigen -- Versionen wechseln, um frühere Iterationen des Subgraphen zu erkunden - Abfrage von Subgraphen über GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Subgraphen auf dem Prüfstand testen - Anzeigen der Indexierer, die auf einem bestimmten Subgraphen indexieren - Subgraphen-Statistiken (Zuweisungen, Kuratoren, etc.) -- Anzeigen der Entität, die den Subgraphen veröffentlicht hat +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Bild 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegierten-Seite +### Step 2. Delegate GRT -Auf der [Delegierten-Seite] (https://thegraph.com/explorer/delegate?chain=arbitrum-one) finden Sie Informationen zum Delegieren, zum Erwerb von GRT und zur Auswahl eines Indexierers. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -Auf dieser Seite können Sie Folgendes sehen: +Here, you can: -- Indexierer, die die meisten Abfragegebühren erhoben haben -- Indexierer mit dem höchsten geschätzten effektiven Jahreszins +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Darüber hinaus können Sie Ihren ROI berechnen und die besten Indexierer nach Name, Adresse oder Subgraph suchen. +### Step 3. Monitor Participants in the Network -### Teilnehmer-Seite +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -Diese Seite bietet einen Überblick über alle „Teilnehmer“, d. h. alle am Netzwerk beteiligten Personen wie Indexer, Delegatoren und Kuratoren. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexierer +#### Indexer -![Explorer Bild 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexierer sind das Rückgrat des Protokolls. Sie setzen auf Subgraphen, indizieren sie und stellen allen, die Subgraphen konsumieren, Abfragen zur Verfügung. -In der Tabelle Indizierer können Sie die Delegationsparameter eines Indizierers, seinen Einsatz, die Höhe seines Einsatzes für jeden Subgraphen und die Höhe seiner Einnahmen aus Abfragegebühren und Indizierungsprämien sehen. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Besonderheiten** -- Abfragegebührenkürzung – der Prozentsatz der Abfragegebührenrabatte, den der Indexierer bei der Aufteilung mit Delegatoren teien. -- Effektiver Reward Cut - der auf den Delegationspool angewandte Indexierungs-Reward Cut. Ist er negativ, bedeutet dies, dass der Indexierer einen Teil seiner Rewards abgibt. Ist er positiv, bedeutet dies, dass der Indexierer einen Teil seiner Rewards behält. -- Verbleibende Abklingzeit - die verbleibende Zeit, bis der Indexierer die oben genannten Delegationsparameter ändern kann. Abklingzeiten werden von Indexierern festgelegt, wenn sie ihre Delegationsparameter aktualisieren. -- Eigenkapital - Dies ist der hinterlegte Einsatz des Indexierers, der bei bösartigem oder falschem Verhalten gekürzt werden kann. -- Delegiert - Einsätze von Delegatoren, die vom Indexierer zugewiesen werden können, aber nicht durchgeschnitten werden können. -- Zugewiesen - Einsatz, den Indexierer aktiv den Subgraphen zuweisen, die sie indizieren. -- Verfügbare Delegationskapazität - die Menge der delegierten Anteile, die die Indexierer noch erhalten können, bevor sie überdelegiert werden. -- Maximale Delegationskapazität - der maximale Betrag an delegiertem Einsatz, den der Indexierer produktiv akzeptieren kann. Ein überschüssiger delegierter Einsatz kann nicht für Zuteilungen oder Belohnungsberechnungen verwendet werden. -- Abfragegebühren - dies ist die Gesamtsumme der Gebühren, die Endnutzer über die gesamte Zeit für Abfragen von einem Indexierer bezahlt haben. -- Indexierer Rewards - dies ist die Gesamtsumme der Indexierer Rewards, die der Indexierer und seine Delegatoren über die gesamte Zeit verdient haben. Indexierer Rewards werden durch die Ausgabe von GRTs ausgezahlt. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexierer können sowohl Abfragegebühren als auch Indexierungsprämien verdienen. Funktionell geschieht dies, wenn Netzwerkteilnehmer GRT an einen Indexierer delegieren. Dadurch können Indexierer je nach ihren Indexierer-Parametern Abfragegebühren und Belohnungen erhalten. @@ -86,9 +106,9 @@ Indexierer können sowohl Abfragegebühren als auch Indexierungsprämien verdien Um mehr darüber zu erfahren, wie man ein Indexierer wird, können Sie einen Blick auf die [offizielle Dokumentation](/indexing/overview/) oder [The Graph Academy Indexer guides](https://thegraph.academy/delegators/choosing-indexers/) werfen. -![Indizierungs-Detailfenster](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Kuratoren +#### Curators Kuratoren analysieren Subgraphen, um festzustellen, welche Subgraphen von höchster Qualität sind. Sobald ein Kurator einen potenziell hochwertigen Subgraphen gefunden hat, kann er ihn kuratieren, indem er seine Bindungskurve signalisiert. Auf diese Weise teilen die Kuratoren den Indexierern mit, welche Subgraphen von hoher Qualität sind und indiziert werden sollten. @@ -102,11 +122,11 @@ In der unten aufgeführten Tabelle von The Curator können Sie sehen: - Die Anzahl der hinterlegten GRT - Die Anzahl der Anteile, die ein Kurator besitzt -![Explorer Bild 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) Wenn Sie mehr über die Rolle des Kurators erfahren möchten, besuchen Sie [offizielle Dokumentation](/resources/roles/curating/) oder [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegatoren +#### Delegatoren Delegatoren spielen eine Schlüsselrolle bei der Aufrechterhaltung der Sicherheit und Dezentralisierung des Graph Network. Sie beteiligen sich am Netzwerk, indem sie GRT-Token an einen oder mehrere Indexierer delegieren (d.h. „staken“). @@ -114,7 +134,7 @@ Delegatoren spielen eine Schlüsselrolle bei der Aufrechterhaltung der Sicherhei - Die Delegatoren wählen die Indexierer auf der Grundlage einer Reihe von Variablen aus, wie z. B. frühere Leistungen, Indexierungsvergütungssätze und Senkung der Abfragegebühren. - Die Reputation innerhalb der Community kann bei der Auswahl ebenfalls eine Rolle spielen. Es wird empfohlen, mit den ausgewählten Indexierern über [The Graph's Discord] (https://discord.gg/graphprotocol) oder [The Graph Forum] (https://forum.thegraph.com/) in Kontakt zu treten. -![Explorer Bild 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In der Tabelle „Delegatoren“ können Sie die aktiven Delegatoren in der Community und wichtige Metriken einsehen: @@ -127,9 +147,9 @@ In der Tabelle „Delegatoren“ können Sie die aktiven Delegatoren in der Comm If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Netzwerk-Seite +### Step 4. Analyze Network Performance -Auf dieser Seite können Sie globale KPIs sehen und haben die Möglichkeit, auf eine Epochenbasis zu wechseln und die Netzwerkmetriken detaillierter zu analysieren. Diese Details geben Ihnen ein Gefühl dafür, wie sich das Netzwerk im Laufe der Zeit entwickelt. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Überblick @@ -147,7 +167,7 @@ Ein paar wichtige Details sind zu beachten: - **Die Abfragegebühren stellen die von den Verbrauchern** generierten Gebühren dar. Sie können von den Indexierern nach einem Zeitraum von mindestens 7 Epochen (siehe unten) eingefordert werden (oder auch nicht), nachdem ihre Zuweisungen zu den Subgraphen abgeschlossen wurden und die von ihnen gelieferten Daten von den Verbrauchern validiert wurden. - **Die Indizierungs-Belohnungen stellen die Anzahl der Belohnungen dar, die die Indexierer während der Epoche von der Netzwerkausgabe beansprucht haben.** Obwohl die Protokollausgabe festgelegt ist, werden die Belohnungen erst geprägt, wenn die Indexierer ihre Zuweisungen zu den Subgraphen schließen, die sie indiziert haben. Daher variiert die Anzahl der Rewards pro Epoche (d. h. während einiger Epochen könnten Indexer kollektiv Zuweisungen geschlossen haben, die seit vielen Tagen offen waren). -![Explorer Bild 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochen @@ -161,69 +181,77 @@ Im Abschnitt Epochen können Sie je nach Epochen Metriken analysieren: - Die verteilenden Epochen sind die Epochen, in denen die Zustandskanäle für die Epochen abgerechnet werden und die Indexierer ihre Rückerstattung der Abfragegebühren beantragen können. - Die abgeschlossenen Epochen sind die Epochen, für die die Indexierer keine Abfragegebühren-Rabatte mehr beanspruchen können. -![Explorer Bild 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Ihr Benutzerprofil +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Ihr persönliches Profil ist der Ort, an dem Sie Ihre Netzwerkaktivitäten sehen können, unabhängig von Ihrer Rolle im Netzwerk. Ihre Krypto- Wallet dient als Ihr Benutzerprofil, und im Benutzer-Dashboard können Sie die folgenden Registerkarten sehen: +### Step 2. Explore the Tabs -### Profil-Übersicht +#### Profil-Übersicht In diesem Abschnitt können Sie Folgendes sehen: -- Jede Ihrer aktuellen Aktionen, die Sie durchgeführt haben. -- Ihre Profilinformationen, Beschreibung und Website (falls Sie eine hinzugefügt haben). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Bild 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Registerkarte "Subgraphen" +#### Registerkarte "Subgraphen" -Auf der Registerkarte "Subgraphen" sehen Sie Ihre veröffentlichten Subgraphen. +The Subgraphs tab displays all your published Subgraphs. -> Dies schließt keine Subgraphen ein, die mit dem CLI zu Testzwecken bereitgestellt wurden. Subgraphen werden erst angezeigt, wenn sie im dezentralen Netzwerk veröffentlicht werden. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Bild 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Registerkarte "Indizierung" +#### Registerkarte "Indizierung" -Auf der Registerkarte "Indizierung" finden Sie eine Tabelle mit allen aktiven und historischen Zuweisungen zu Subgraphen. Hier finden Sie auch Diagramme, in denen Sie Ihre bisherige Leistung als Indexierer sehen und analysieren können. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Dieser Abschnitt enthält auch Angaben zu Ihren Netto-Indexierer-Belohnungen und Netto-Abfragegebühren. Sie sehen die folgenden Metriken: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - der Einsatz von Delegatoren, der von Ihnen zugewiesen werden kann, aber nicht reduziert werden kann -- Gesamte Abfragegebühren - die gesamten Gebühren, die Nutzer im Laufe der Zeit für von Ihnen durchgeführte Abfragen bezahlt haben -- Indexierer Rewards - der Gesamtbetrag der Indexierer Rewards, die Sie erhalten haben, in GRT -- Gebührensenkung - der Prozentsatz der Rückerstattungen von Abfragegebühren, den Sie behalten, wenn Sie mit Delegatoren teilen -- Rewardkürzung - der Prozentsatz der Indexierer-Rewards, den Sie behalten, wenn Sie mit Delegatoren teilen -- Eigenkapital - Ihr hinterlegter Einsatz, der bei böswilligem oder falschem Verhalten gekürzt werden kann +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Bild 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Registerkarte "Delegieren" +![Indexer Stats](/img/Indexer-Stats.png) -Die Delegatoren sind wichtig für The Graph Network. Sie müssen ihr Wissen nutzen, um einen Indexierer auszuwählen, der eine gesunde Rendite abwirft. +#### Registerkarte "Delegieren" -Auf der Registerkarte "Delegatoren" finden Sie die Details Ihrer aktiven und historischen Delegationen sowie die Metriken der Indexierer, an die Sie delegiert haben. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In der ersten Hälfte der Seite sehen Sie Ihr Delegationsdiagramm sowie das Diagramm „Nur Belohnungen“. Auf der linken Seite sehen Sie die KPIs, die Ihre aktuellen Delegationskennzahlen widerspiegeln. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Auf dieser Registerkarte sehen Sie unter anderem die Delegator-Metriken: +Top Section: -- Delegationsprämien insgesamt -- Unrealisierte Rewards insgesamt -- Gesamte realisierte Rewards +- View delegation and rewards-only charts +- Track key metrics: + - Delegationsprämien insgesamt + - Unrealized rewards + - Realized Rewards -In der zweiten Hälfte der Seite finden Sie die Tabelle der Delegationen. Hier sehen Sie die Indexierer, an die Sie delegiert haben, sowie deren Details (wie z. B. Belohnungskürzungen, Abklingzeit, usw.). +Bottom Section: -Mit den Schaltflächen auf der rechten Seite der Tabelle können Sie Ihre Delegierung verwalten - mehr delegieren, die Delegierung aufheben oder Ihre Delegierung nach der Auftauzeit zurückziehen. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Beachten Sie, dass dieses Diagramm horizontal gescrollt werden kann. Wenn Sie also ganz nach rechts scrollen, können Sie auch den Status Ihrer Delegation sehen (delegierend, nicht delegierend, zurückziehbar). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Bild 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Registerkarte "Kuratieren" +#### Registerkarte "Kuratieren" -Auf der Registerkarte „Kuratierung“ finden Sie alle Subgraphen, für die Sie ein Signal geben (damit Sie Abfragegebühren erhalten). Mit der Signalisierung können Kuratoren den Indexierern zeigen, welche Subgraphen wertvoll und vertrauenswürdig sind und somit signalisieren, dass sie indiziert werden müssen. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Auf dieser Registerkarte finden Sie eine Übersicht über: @@ -232,22 +260,22 @@ Auf dieser Registerkarte finden Sie eine Übersicht über: - Abfragebelohnungen pro Subgraph - Aktualisiert bei Datumsdetails -![Explorer Bild 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Ihre Profileinstellungen +#### Ihre Profileinstellungen In Ihrem Benutzerprofil können Sie Ihre persönlichen Profildaten verwalten (z. B. einen ENS-Namen einrichten). Wenn Sie ein Indexierer sind, haben Sie sogar noch mehr Zugang zu den Einstellungen, die Ihnen zur Verfügung stehen. In Ihrem Benutzerprofil können Sie Ihre Delegationsparameter und Operatoren einrichten. - Operatoren führen im Namen des Indexierers begrenzte Aktionen im Protokoll durch, wie z. B. das Öffnen und Schließen von Allokationen. Operatoren sind in der Regel andere Ethereum-Adressen, die von ihrer Staking-Wallet getrennt sind und einen beschränkten Zugang zum Netzwerk haben, den Indexer persönlich festlegen können - Mit den Delegationsparametern können Sie die Verteilung der GRT zwischen Ihnen und Ihren Delegatoren steuern. -![Explorer Bild 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) Als Ihr offizielles Portal in die Welt der dezentralen Daten ermöglicht Ihnen der Graph Explorer eine Vielzahl von Aktionen, unabhängig von Ihrer Rolle im Netzwerk. Sie können zu Ihren Profileinstellungen gelangen, indem Sie das Dropdown-Menü neben Ihrer Adresse öffnen und dann auf die Schaltfläche Einstellungen klicken. ![Wallet details](/img/Wallet-Details.png) -## Zusätzliche Ressourcen +### Zusätzliche Ressourcen ### Video-Leitfaden From c1f53449b5406d8d67009b628257c147b3669dcb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:12 -0400 Subject: [PATCH 135/290] New translations explorer.mdx (Japanese) --- website/src/pages/ja/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ja/subgraphs/explorer.mdx b/website/src/pages/ja/subgraphs/explorer.mdx index 0357d63fda7e..303ac4e7f221 100644 --- a/website/src/pages/ja/subgraphs/explorer.mdx +++ b/website/src/pages/ja/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: グラフエクスプローラ --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## 概要 -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- チャート、現在のデプロイメント ID、その他のメタデータなどの詳細情報の表示 -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - サブグラフの統計情報（割り当て数、キュレーターなど） -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. インデクサー（Indexers） +#### インデクサー -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - インデクサーが生産的に受け入れることができる委任されたステークの最大量。超過した委任されたステークは、割り当てや報酬の計算には使用できません。 -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - インデクサーとそのデリゲーターが過去に獲得したインデクサー報酬の総額。 インデクサー報酬は GRT の発行によって支払われます +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. キュレーター +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - デポジットされた GRT の数 - キュレーターが所有するシェア数 -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. デリゲーター +#### 委任者 Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### 概要 @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### エポック @@ -161,69 +181,77 @@ A few key details to note: - 分配エポックとは、そのエポックの状態チャンネルが確定し、インデクサーがクエリフィーのリベートを請求できるようになるエポックのこと - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## ユーザープロファイル +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### プロフィールの概要 +#### プロフィールの概要 In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### サブグラフタブ +#### サブグラフタブ -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### インデックスタブ +#### インデックスタブ -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -このセクションには、インデクサー報酬とクエリフィーの詳細も含まれます。 以下のような指標が表示されます： +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - あなたが割り当てることができるデリゲーターからのステークですが、スラッシュされることはできません -- Total Query Fees - 提供したクエリに対してユーザーが支払った料金の合計額 -- Indexer Rewards - 受け取ったインデクサー報酬の総額（GRT） -- Fee Cut - デリゲーターとの分配時に保持するクエリフィーリベートの割合 -- Rewards Cut - デリゲーターとの分配時に保有するインデクサー報酬の割合 -- Owned - 預けているステークであり、悪質な行為や不正行為があった場合にスラッシュされる可能性がある +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### デリゲーションタブ +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### デリゲーションタブ -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -ページの前半には、自分のデリゲーションチャートと報酬のみのチャートが表示されています。 左側には、現在のデリゲーションメトリクスを反映した KPI が表示されています。 +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -このタブに表示される委任者の指標には、次のものがあります。 +Top Section: -- デリゲーション報酬の合計 -- 未実現報酬の合計 -- 実現報酬の合計 +- View delegation and rewards-only charts +- Track key metrics: + - デリゲーション報酬の合計 + - Unrealized rewards + - Realized Rewards -ページの後半には、デリゲーションテーブルがあります。 ここには、あなたがデリゲートしたインデクサーとその詳細（報酬のカットやクールダウンなど）が表示されています。 +Bottom Section: -テーブルの右側にあるボタンで、デリゲートを管理することができます。追加でデリゲートする、デリゲートを解除する、解凍期間後にデリゲートを取り消すなどの操作が可能です。 +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -このグラフは水平方向にスクロールできるので、右端までスクロールすると、委任のステータス (委任中、委任解除中、取り消し可能) も表示されることに注意してください。 +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### キュレーションタブ +#### キュレーションタブ -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. このタブでは、以下の概要を見ることができます： @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - 日付詳細に更新済み -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### プロフィールの設定 +#### プロフィールの設定 ユーザープロフィールでは、個人的なプロフィールの詳細（ENS ネームの設定など）を管理することができます。 インデクサーの方は、さらに多くの設定が可能です。 ユーザープロファイルでは、デリゲーションパラメーターとオペレーターを設定することができます。 - オペレーターは、インデクサーに代わって、割り当ての開始や終了など、プロトコル上の限定的なアクションを行います。 オペレーターは通常、ステーキングウォレットとは別の他の Ethereum アドレスで、インデクサーが個人的に設定できるネットワークへのゲート付きアクセス権を持っています。 - 「Delegation parameters」では、自分とデリゲーターの間で GRT の分配をコントロールすることができます。 -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## その他のリソース +### その他のリソース ### Video Guide From cdb90ec32dd65726565efe5cb04f8e44404ed9b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:13 -0400 Subject: [PATCH 136/290] New translations explorer.mdx (Portuguese) --- website/src/pages/pt/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/pt/subgraphs/explorer.mdx b/website/src/pages/pt/subgraphs/explorer.mdx index c1681cf69573..d7654009ec50 100644 --- a/website/src/pages/pt/subgraphs/explorer.mdx +++ b/website/src/pages/pt/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Desbloqueie o mundo dos subgraphs e dos dados de rede com o [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Visão geral -O Graph Explorer consiste de múltiplas partes onde pode-se interagir com [subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegar](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engajar com [participantes](https://thegraph.com/explorer/participants?chain=arbitrum-one), visualizar [informações de rede](https://thegraph.com/explorer/network?chain=arbitrum-one), e acessar o seu perfil de utilizador. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Por Dentro do Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -A seguir, veja um resumo de todas as funções importantes do Graph Explorer. Para saber mais, veja o [vídeo-guia do Graph Explorer](/subgraphs/explorer/#video-guide). +## Pré-requisitos -### Página de Subgraphs +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -Após implantar e editar o seu subgraph no Subgraph Studio, vá para o [Graph Explorer](https://thegraph.com/explorer) e clique no link "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)", na barra de navegação, para acessar o seguinte: +## Navigating Graph Explorer -- Os seus próprios subgraphs completos -- Subgraphs editados por outros -- O subgraph exato que quer (com base na data de criação, quantidade de sinalização, ou nome). +### Step 1. Explore Subgraphs -![Imagem do Explorer #1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -Ao clicar em um subgraph, será possível: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Testar queries na área de testes e aproveitar detalhes de rede para fazer decisões informadas. -- Sinalizar GRT no seu próprio subgraph, ou nos subgraphs de outros, para avisar os indexadores sobre a sua importância e qualidade. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - Isto é importante, porque sinalizar em um subgraph incentiva a sua indexação; ou seja, ele aparecerá em breve na rede para servir queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Imagem do Explorer 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Testar queries na área de testes e aproveitar detalhes de rede para fazer decisões informadas. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) Na página dedicada de cada subgraph, é possível: -- Sinalizar ou cancelar sinais em subgraphs -- Ver mais detalhes como gráficos, ID de lançamento atual, e outros metadados -- Trocar versões para explorar iterações passadas do subgraph - Solicitar queries de subgraphs através da GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Testar subgraphs no playground - Ver os indexadores que indexam em um certo subgraph - Estatísticas do subgraph (alocações, Curadores, etc.) -- Visualizar a entidade que editou o subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Imagem do Explorer 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Página de Delegação +### Step 2. Delegate GRT -Na [página de Delegação](https://thegraph.com/explorer/delegate?chain=arbitrum-one), é possível encontrar informações sobre como delegar, adquirir GRT, e escolher um Indexador. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -Nesta página, pode-se ver: +Here, you can: -- Os Indexadores que coletaram mais taxas de query -- Indexadores com a maior taxa anual efetiva +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Também é possível calcular a sua taxa de juros e buscar pelos maiores Indexadores por nome, endereço, ou subgraph. +### Step 3. Monitor Participants in the Network -### Participantes +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -Esta página providencia um resumo de todos os "participantes", incluindo todos que participam na rede: por exemplo, Indexadores, Delegantes, e Curadores. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexadores +#### Indexadores -![Imagem do Explorer 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Os Indexadores formam a fundação do protocolo. Eles investem em subgraphs, os indexam, e servem queries a qualquer um que consome os subgraphs. -Na tabela de Indexadores, pode-se ver os parâmetros de delegação de um Indexador; a sua participação; quanto ele investiu em cada subgraph; e a receita que ele obteve com taxas de query e recompensas de indexação. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Detalhes** -- Porção de Taxa de Query — a percentagem dos rebates da taxa de query que o Indexador guarda ao dividir com os Delegantes. -- Porção de Recompensa Efetiva — a porção de recompensa de indexação, aplicada ao pool de delegação. Se for negativa, ela significa que o Indexador está a distribuir parte das suas recompensas. Se for positiva, significa que o Indexador guarda um pouco das recompensas. -- Tempo de Recarga — o tempo que resta até o Indexador poder mudar os parâmetros de delegação acima. Os períodos de recarga são configurados pelos Indexadores quando atualizam os seus parâmetros de delegação. -- Títulos — Os stakes investidos pelo Indexador, que podem ser cortados por comportamento malicioso ou incorreto. -- Delegado — Stake de Delegantes que pode ser alocado pelo Indexador, mas não pode ser cortado. -- Alocado — O stake que os Indexadores alocam de forma ativa aos subgraphs que indexam. -- Capacidade Disponível de Delegação — a quantia de stakes delegados que os Indexadores ainda podem receber, antes que sejam delegados excessivamente. -- Capacidade Máxima de Delegação — a quantidade máxima de stake delegado que o Indexador pode aceitar produtivamente. Um excesso de stake delegado não pode ser usado para alocações ou cálculos de recompensas. -- Taxas de Query — as taxas totais que os utilizadores finais pagaram por queries de um Indexador durante todo o seu tempo. -- Recompensas de Indexador — as recompensas totais recebidas pelo Indexador e pelos Delegantes temporalmente. As recompensas de Indexador são pagas pela emissão de GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Os indexadores podem ganhar taxas de query e recompensas de indexação. Funcionalmente, isto acontece quando participantes da rede delegam GRT a um Indexador. Isto permite que Indexadores recebam taxas e recompensas de queries, a depender dos seus parâmetros de Indexador. @@ -86,9 +106,9 @@ Os indexadores podem ganhar taxas de query e recompensas de indexação. Funcion Para saber mais sobre como se tornar um Indexador, veja a [documentação oficial](/indexing/overview/) ou os [guias de Indexador da The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) -![Painel de detalhes de Indexação](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curadores +#### Curators Os Curadores analisam subgraphs para identificar os de maior qualidade. Quando um Curador achar um subgraph atraente, ele poderá curá-lo com sinais na sua bonding curve. Ao fazer isso, os Curadores avisam aos Indexadores quais subgraphs têm qualidade alta e merecem ser indexados. @@ -102,11 +122,11 @@ Na tabela de Curador abaixo, é possível ver: - O número de GRT depositado - O número de ações que um Curador tem -![Imagem do Explorer 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) Para saber mais sobre a função de Curador, veja a [documentação oficial](/resources/roles/curating/) ou visite a [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegantes +#### Delegantes Os Delegantes são fundamentais na manutenção da segurança e da descentralização da The Graph Network. Eles participam da rede com a delegação (ou seja, o investimento — ou “staking”) de tokens GRT para um ou mais indexadores. @@ -114,7 +134,7 @@ Os Delegantes são fundamentais na manutenção da segurança e da descentraliza - Os Delegantes selecionam Indexadores com base em variáveis diferentes, que incluem: histórico de desempenho, taxas de recompensa por indexação, e porções de taxa de query. - A reputação na comunidade também pode ser importante no processo de seleção. É recomendado se conectar com os Indexadores selecionados via [o Discord](https://discord.gg/graphprotocol) ou [o fórum oficial do The Graph](https://forum.thegraph.com/). -![Imagem do Explorer 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) A tabela de Delegantes mostra os Delegantes ativos na comunidade e as métricas importantes: @@ -127,9 +147,9 @@ A tabela de Delegantes mostra os Delegantes ativos na comunidade e as métricas Para saber mais sobre a função de Delegante, veja a [documentação oficial](/resources/roles/delegating/delegating/) ou visite a [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Rede +### Step 4. Analyze Network Performance -A seção de Rede mostra indicadores-chave de desempenho (KPIs) globais, e permite trocar para uma base por epoch e analisar métricas de rede em mais detalhes. Estes detalhes darão-lhe uma ideia do desempenho gradual da rede. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Visão geral @@ -147,7 +167,7 @@ Alguns detalhes importantes: - **As taxas de query representam as taxas geradas pelos consumidores**, e podem ser reivindicadas (ou não) pelos Indexadores após um período de pelo menos 7 epochs (veja abaixo), após as suas alocações aos subgraphs forem fechadas e os dados que serviram forem validados pelos consumidores. - **As recompensas de indexação representam a quantidade de recompensas que os Indexadores resgataram da emissão da rede durante a epoch.** Apesar da emissão do protocolo ser fixa, as recompensas só são mintadas quando os Indexadores fecham as suas alocações aos subgraphs que indexaram. Assim, o número de recompensas por epoch varia (por ex., durante algumas epochs, os Indexadores podem ter coletivamente fechado alocações abertas há muitos dias). -![Imagem do Explorer 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ Na seção de Epochs, pode analisar, numa base por epoch, métricas como: - Nas epochs de distribuição, são estabelecidos os canais de estado para as epochs, e os Indexadores podem reivindicar os seus rebates de taxas de query. - As epochs finalizadas são aquelas que não têm mais rebates de taxas de query para serem resgatadas pelos Indexadores; portanto, finalizadas. -![Imagem do Explorer 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Seu Perfil de Utilizador +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -É no seu perfil pessoal que verás a sua atividade na rede, sem se preocupar com a sua participação nela. A sua carteira de cripto será o seu perfil de utilizador, e com o Painel de Controlo do Utilizador, pode-se ver: +### Step 2. Explore the Tabs -### Resumo do Perfil +#### Resumo do Perfil Esta página mostra: -- Quaisquer ações atuais que tenha realizado. -- As suas informações de perfil, sua descrição, e seu sítio da web (se tiver adicionado um). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Imagem do Explorer 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Aba de Subgraphs +#### Aba de Subgraphs -A aba de Subgraphs mostra os subgraphs editados por você. +The Subgraphs tab displays all your published Subgraphs. -> Isso não inclui nenhum subgraph implantado com a CLI para fins de teste. Os subgraphs só aparecerão quando forem editados na rede descentralizada. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Imagem do Explorer 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Aba de Indexação +#### Aba de Indexação -A aba de Indexação mostrará uma tabela com todas as alocações ativas e históricas aos subgraphs, além de gráficos para analisar e ver o seu histórico de desempenho como um Indexador. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Esta secção também incluirá detalhes sobre as suas recompensas de Indexador e taxas de consulta. Verá as seguintes métricas: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Stake Delegado — O stake de Delegados que pode ser alocado por você, mas não pode ser cortado -- Taxas Totais de Query — as taxas totais que os utilizadores pagaram por consultas que serviu temporalmente -- Recompensas de Indexador — a quantia total de recompensas de Indexador que recebeu, em GRT -- Porção de Taxa — a % dos rebates das taxas de query que guardará ao dividir com os Delegantes -- Porção de Recompensas — a % dos rebates das recompensas de Indexador que guarda ao dividir com os Delegantes -- Títulos — o seu stake depositado, que pode ser cortado por comportamento malicioso ou incorreto +Track your Indexer performance with visual charts and key metrics, including: -![Imagem do Explorer 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Aba de Delegação +![Indexer Stats](/img/Indexer-Stats.png) -Os Delegantes são importantes para a Graph Network. Eles devem usar bem o seu conhecimento para escolher um Indexador que fornecerá um retorno saudável sobre as recompensas. +#### Aba de Delegação -A aba de Delegantes exibe os detalhes das suas delegações ativas e históricas, além das métricas dos Indexadores para os quais delegou. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -Na primeira metade da página estão o seu gráfico de delegação e um gráfico só de recompensas. Na esquerda, pode ver os KPIs (indicadores de desempenho) que refletem as suas métricas atuais de delegação. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -As métricas de Delegado nesta aba incluem: +Top Section: -- Recompensas totais de delegação -- Recompensas não realizadas -- Recompensas realizadas +- View delegation and rewards-only charts +- Track key metrics: + - Recompensas totais de delegação + - Unrealized rewards + - Realized Rewards -Na segunda metade da página está a tábua de delegações. Aqui, pode ver os Indexadores aos quais delegou, assim como os seus detalhes (como porções de recompensas, tempo de recarga, etc.). +Bottom Section: -Com os botões no lado direito da tábua, pode gestar a sua delegação — delegar mais, cancelar delegações, ou retirar a sua delegação após o período de degelo. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Lembre-se que este gráfico pode ser rolado horizontalmente, então se rolar totalmente à direita, pode ver o estado da sua delegação (a delegar, a cancelar, sacável). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Imagem do Explorer 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Aba de Curadoria +#### Aba de Curadoria -Na aba de Curadoria, encontrará todos os subgraphs nos quais sinaliza (assim, capaz de receber taxas de consulta). A sinalização permite que os Curadores destaquem aos Indexadores quais subgraphs são valiosos e confiáveis, e assim, indicar que eles devem ser indexados. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Dentro desta aba está um resumo de: @@ -232,22 +260,22 @@ Dentro desta aba está um resumo de: - Recompensas de query por subgraph - Detalhes de datas de atualização -![Imagem do Explorer 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Configurações do Seu Perfil +#### Configurações do Seu Perfil Dentro do seu perfil de utilizador, poderá configurar os detalhes do seu perfil pessoal (como a configuração de um nome ENS). Se fores um Indexador, terá ainda mais acesso às configurações no alcance dos seus dedos. Em seu perfil de utilizador, poderá configurar os seus parâmetros de delegação e os seus operadores. - Os Operadores tomam ações limitadas no protocolo em nome do Indexador, como abertura e fechamento de alocações. Os operadores tendem a ser outros endereços do Ethereum, separados da sua carteira de staking, com acesso guardado à rede que pode ser configurado pessoalmente pelos Indexadores - Parâmetros de delegação que permitem controlar a distribuição de GRT entre você e os seus Delegantes. -![Imagem do Explorer 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) Como o seu portal oficial no mundo dos dados descentralizados, o Graph Explorer permite-lhe tomar uma variedade de ações, independente do seu papel na rede. Pode acessar as suas configurações do perfil ao abrir o menu próximo ao seu endereço, e depois, clicar no botão de Configurações. ![Detalhes de carteira](/img/Wallet-Details.png) -## Outros Recursos +### Outros Recursos ### Guia em Vídeo From c3a3444bd507393500d66df7c10936a490578084 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:14 -0400 Subject: [PATCH 137/290] New translations explorer.mdx (Russian) --- website/src/pages/ru/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ru/subgraphs/explorer.mdx b/website/src/pages/ru/subgraphs/explorer.mdx index b963e985dd99..6de281513f1b 100644 --- a/website/src/pages/ru/subgraphs/explorer.mdx +++ b/website/src/pages/ru/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Обзор -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Внутреннее устройство Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -Ниже приведён обзор всех ключевых функций Graph Explorer. Для получения дополнительной помощи Вы можете посмотреть [видеоруководство по Graph Explorer](/subgraphs/explorer/#video-guide). +## Предварительные требования -### Страница субграфов +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Субграфы, опубликованные другими -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Изображение Explorer 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Протестировать запросы на тестовой площадке и использовать данные сети для принятия обоснованных решений. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Изображение Explorer 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Протестировать запросы на тестовой площадке и использовать данные сети для принятия обоснованных решений. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Просмотр дополнительных сведений, таких как диаграммы, текущий идентификатор развертывания и другие метаданные -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Статистика субграфов (распределения, кураторы и т. д.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Изображение Explorer 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Страница Делегатора +### Step 2. Delegate GRT -На [странице Делегатора](https://thegraph.com/explorer/delegate?chain=arbitrum-one) Вы можете найти информацию о делегировании, приобретении GRT и выборе Индексатора. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -На этой странице Вы можете увидеть следующее: +Here, you can: -- Индексаторы, собравшие наибольшее количество комиссий за запросы -- Индексаторы с самой высокой расчетной годовой процентной ставкой +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Страница участников +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -На этой странице представлен общий обзор всех «участников», включая всех участников сети, таких как Индексаторы, Делегаторы и Кураторы. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Индексаторы +#### Индексаторы -![Изображение Explorer 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Особенности** -- Часть комиссии за запросы — это процент от возвратов комиссии за запросы, который Индексатор оставляет себе при распределении с Делегаторами. -- Эффективная часть вознаграждения — это доля вознаграждения за индексирование, применяемая к пулу делегирования. Если она отрицательная, это означает, что Индексатор отдаёт часть своих вознаграждений. Если она положительная, это означает, что Индексатор сохраняет часть своих вознаграждений. -- Оставшееся время восстановления — время, оставшееся до того, как Индексатор сможет изменить вышеуказанные параметры делегирования. Периоды восстановления устанавливаются Индексаторами при обновлении параметров делегирования. -- Собственность — это депозитная доля Индексатора, которая может быть урезана за злонамеренное или некорректное поведение. -- Делегированный стейк — доля Делегаторов, которая может быть распределена Индексатором, но не может быть сокращена. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Доступная емкость делегирования — объем делегированной доли, которую Индексаторы всё ещё могут получить, прежде чем они будут перераспределены. -- Максимальная емкость делегирования — максимальная сумма делегированной доли, которую Индексатор может продуктивно принять. Избыточная делегированная ставка не может быть использована для распределения или расчета вознаграждений. -- Плата за запросы — это общая сумма комиссий, которую конечные пользователи заплатили за запросы Индексатора за все время. -- Вознаграждения Индексатора — это общая сумма вознаграждений Индексатора, полученная им и его Делегаторами за все время. Вознаграждения Индексаторов выплачиваются посредством выпуска GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Индексаторы могут получать как комиссии за запросы, так и вознаграждения за индексацию. Фактически это происходит, когда участники сети делегируют GRT Индексатору. Это позволяет Индексаторам получать комиссионные и вознаграждения в зависимости от параметров самого Индексатора. @@ -86,9 +106,9 @@ In the Indexers table, you can see an Indexers’ delegation parameters, their s Чтобы узнать больше о том, как стать Индексатором, Вы можете ознакомиться с [официальной документацией](/indexing/overview/) или [руководствами для Индексаторов Академии The Graph.] (https://thegraph.academy/delegators/choosing-indexers/) -![Панель сведений об индексировании](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Кураторы +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ Curators analyze Subgraphs to identify which Subgraphs are of the highest qualit - Количество GRT, которое было внесено - Количество акций, которыми владеет Куратор -![Изображение Explorer 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) Если Вы хотите узнать больше о роли Куратора, Вы можете сделать это, ознакомившись с [официальной документацией] (/resources/roles/curating/) или посетив [Академию The Graph](https://thegraph.academy/curators/). -#### 3. Делегаторы +#### Делегаторы Делегаторы играют ключевую роль в поддержании безопасности и децентрализации The Graph Network. Они участвуют в сети, делегируя (т. е. «стейкая») токены GRT одному или нескольким индексаторам. @@ -114,7 +134,7 @@ Curators analyze Subgraphs to identify which Subgraphs are of the highest qualit - Делегаторы выбирают Индексаторов на основе ряда различных переменных, таких как прошлые результаты, ставки вознаграждения за индексирование и снижение платы за запросы. - Репутация в сообществе может также повлиять на выбор. Вы можете связаться с Индексаторами через [Дискорд The Graph](https://discord.gg/graphprotocol) или [Форум The Graph](https://forum.thegraph.com/). -![Изображение Explorer 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) В таблице «Делегаторы» Вы можете увидеть активных в сообществе Делегаторов и важные показатели: @@ -127,9 +147,9 @@ Curators analyze Subgraphs to identify which Subgraphs are of the highest qualit If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Страница сети +### Step 4. Analyze Network Performance -На этой странице Вы можете увидеть глобальные ключевые показатели эффективности и получить возможность переключения на поэпохальную основу и более детально проанализировать сетевые метрики. Эти данные дадут Вам представление о том, как работает сеть на протяжении определённого времени. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Обзор @@ -147,7 +167,7 @@ If you want to learn more about how to become a Delegator, check out the [offici - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Изображение Explorer 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Эпохи @@ -161,69 +181,77 @@ If you want to learn more about how to become a Delegator, check out the [offici - Эпохи распределения - это эпохи, в которых состояния каналов для эпох регулируются, и Индексаторы могут требовать скидки на комиссию за запросы. - Завершенные эпохи — это эпохи, в которых Индексаторы больше не могут заявить возврат комиссии за запросы. -![Изображение Explorer 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Ваш профиль пользователя +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Ваш личный профиль — это место, где Вы можете видеть свою сетевую активность, независимо от своей роли в сети. Ваш криптокошелек будет действовать как Ваш профиль пользователя, а на панели управления пользователя Вы сможете увидеть следующие вкладки: +### Step 2. Explore the Tabs -### Обзор профиля +#### Обзор профиля В этом разделе Вы можете увидеть следующее: -- Любое из текущих действий, которые Вы совершили. -- Данные своего профиля, описание и веб-сайт (если Вы его добавили). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Изображение Explorer 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Вкладка "Субграфы" +#### Вкладка "Субграфы" -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Изображение Explorer 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Вкладка "Индексирование" +#### Вкладка "Индексирование" -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Этот раздел также будет содержать подробную информацию о Ваших чистых вознаграждениях Индексатора и чистой комиссии за запросы. Вы увидите следующие показатели: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Делегированная ставка — ставка Делегаторов, которую Вы можете выделить, но не можете уменьшить -- Общая комиссия за запросы — общая сумма комиссий, которую пользователи платили за запросы, обслуживаемые Вами за определенный период времени -- Вознаграждения Индексатора – общая сумма полученных Вами вознаграждений Индексатора в GRT -- Сокращение комиссии — процент скидки на комиссию за запросы, который Вы сохраните при разделении с Делегаторами -- Сокращение вознаграждений — процент вознаграждений Индексатора, который Вы сохраните при разделении с Делегаторами -- Собственность — Ваша внесенная ставка, которая может быть уменьшена за злонамеренное или неправильное поведение +Track your Indexer performance with visual charts and key metrics, including: -![Изображение Explorer 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Вкладка "Делегирование" +![Indexer Stats](/img/Indexer-Stats.png) -Делегаторы важны для the Graph Network. Они должны использовать свои знания, чтобы выбрать Индексатора, который обеспечит хороший доход от вознаграждений. +#### Вкладка "Делегирование" -На вкладке «Делегаторы» Вы можете найти подробную информацию о своих активных и прошлых делегированиях, а также показатели Индексаторов, которым Вы делегировали полномочия. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -В первой половине страницы Вы можете увидеть диаграмму делегирования, а также диаграмму только вознаграждений. Слева Вы можете увидеть ключевые показатели эффективности, которые отражают Ваши текущие показатели делегирования. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Метрики делегатора, которые Вы увидите на этой вкладке, включают: +Top Section: -- Общую сумму вознаграждений за делегирование -- Общее количество нереализованных наград -- Общее количество реализованных наград +- View delegation and rewards-only charts +- Track key metrics: + - Общую сумму вознаграждений за делегирование + - Unrealized rewards + - Realized Rewards -Во второй половине страницы находится таблица делегирования. Здесь Вы можете увидеть Индексаторов, которым Вы делегировали полномочия, а также подробную информацию о них (например, сокращение вознаграждений, время восстановления и т. д.). +Bottom Section: -С помощью кнопок в правой части таблицы Вы можете управлять своим делегированием: делегировать больше, отменить делегирование или отозвать свое делегирование после разморозки. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Имейте в виду, что эта диаграмма прокручивается по горизонтали, поэтому, если Вы прокрутите ее до конца вправо, Вы также сможете увидеть статус своего делегирования (делегирование, отмена делегирования, возможность отзыва). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Изображение Explorer 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Вкладка "Курирование" +#### Вкладка "Курирование" -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. На данной вкладке Вы найдете обзор: @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - Даты обновления данных -![Изображение Explorer 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Параметры Вашего профиля +#### Параметры Вашего профиля В Вашем пользовательском профиле Вы сможете управлять деталями своего личного профиля (например, настройкой имени ENS). Если Вы Индексатор, у Вас есть еще больше возможностей для доступа к настройкам. В Вашем пользовательском профиле Вы сможете настроить параметры делегирования и операторов. - Операторы выполняют ограниченные действия в протоколе от имени Индексатора, такие как открытие и закрытие распределения. Операторами обычно являются другие адреса Ethereum, отдельные от их кошелька для ставок, с ограниченным доступом к сети, который Индексаторы могут настроить лично - Параметры делегирования позволяют Вам контролировать распределение GRT между Вами и Вашими Делегаторами. -![Изображение Explorer 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) Являясь Вашим официальным порталом в мир децентрализованных данных, Graph Explorer позволяет Вам выполнять самые разные действия, независимо от Вашей роли в сети. Вы можете перейти к настройкам своего профиля, открыв выпадающее меню рядом со своим адресом и нажав кнопку «Настройки». ![Wallet details](/img/Wallet-Details.png) -## Дополнительные ресурсы +### Дополнительные ресурсы ### Видео руководство From ed2875c548d85d8622be180d33d0a8962eaaf306 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:16 -0400 Subject: [PATCH 138/290] New translations explorer.mdx (French) --- website/src/pages/fr/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/fr/subgraphs/explorer.mdx b/website/src/pages/fr/subgraphs/explorer.mdx index 7a7cf7e972db..f1a59e1c9c43 100644 --- a/website/src/pages/fr/subgraphs/explorer.mdx +++ b/website/src/pages/fr/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Découvrez le monde des subgraphs et des données de réseau avec [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Aperçu -Graph Explorer se compose de plusieurs parties où vous pouvez interagir avec les [subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [déléguer](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engager les [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), voir les [informations sur le réseau](https://thegraph.com/explorer/network?chain=arbitrum-one) et accéder à votre profil d'utilisateur. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## À l'intérieur de l'Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -Vous trouverez ci-dessous une liste de toutes les fonctionnalités clés de Graph Explorer. Pour obtenir une assistance supplémentaire, vous pouvez regarder le [guide vidéo de Graph Explorer](/subgraphs/explorer/#video-guide). +## Prérequis -### Page des subgraphs +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -Après avoir déployé et publié votre subgraph dans Subgraph Studio, allez sur [Graph Explorer](https://thegraph.com/explorer) et cliquez sur le lien "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" dans la barre de navigation pour accéder à ce qui suit : +## Navigating Graph Explorer -- Vos propres subgraphs finis -- Les subgraphs publiés par d'autres -- Le Subgraph exact que vous souhaitez (sur la base de la date de création, de la quantité de signal ou du nom). +### Step 1. Explore Subgraphs -![Image 1 de l'Explorer](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -Lorsque vous cliquez sur un subgraph, vous pouvez effectuer les opérations suivantes : +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Tester des requêtes dans le l'environnement de test et utiliser les détails du réseau pour prendre des décisions éclairées. -- Signalez des GRT sur votre propre subgraph ou sur les subgraphs d'autres personnes afin de sensibiliser les Indexeurs sur son importance et sa qualité. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - Ce point est essentiel, car le fait de signaler un subgraph incite à être indexé, ce qui signifie qu'il finira par faire surface sur le réseau pour répondre aux requêtes. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Image 2 de l'Explorer](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Tester des requêtes dans le l'environnement de test et utiliser les détails du réseau pour prendre des décisions éclairées. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) Sur la page dédiée à chaque subgraph, vous pouvez effectuer les opérations suivantes : -- Signaler/Dé-signaler sur les subgraphs -- Afficher plus de détails tels que des graphs, l'ID de déploiement actuel et d'autres métadonnées -- Passer d'une version à l'autre pour explorer les itérations passées du subgraph - Interroger les subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Tester les subgraphs dans le playground - Voir les Indexeurs qui indexent un certain subgraph - Statistiques du subgraph (allocations, conservateurs, etc.) -- Afficher l'entité qui a publié le subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Image 3 de l'Explorer](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Page de Délégué +### Step 2. Delegate GRT -Sur la [page de Délégué](https://thegraph.com/explorer/delegate?chain=arbitrum-one), vous trouverez des informations sur la délégation, l'acquisition de GRT et le choix d'un Indexeur. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -Sur cette page, vous pouvez voir les éléments suivants : +Here, you can: -- Indexeurs ayant perçu le plus de frais de requête -- Indexeurs avec l'APR estimé le plus élevé +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -En outre, vous pouvez calculer votre retour sur investissement et rechercher les meilleurs Indexeurs par nom, adresse ou subgraph. +### Step 3. Monitor Participants in the Network -### Page des participants +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -Cette page offre une vue d'ensemble de tous les "participants," c'est-à-dire de toutes les personnes qui participent au réseau, telles que les Indexeurs, les Déléguateurs et les Curateurs. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexeurs +#### Indexeurs -![Image 4 de l'Explorer](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Les Indexeurs constituent la colonne principale du protocole. Ils s'intéressent aux subgraphs, les indexent et servent des requêtes à tous ceux qui consomment des subgraphs. -Dans le tableau des Indexeurs, vous pouvez voir les paramètres de délégation d'un Indexeur, son staking, le montant qu'il a staké sur chaque subgraph et le revenu qu'il a tiré des frais de requête et des récompenses d'indexation. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. Spécificités -- Query Fee Cut - le % des frais de requête que l'Indexeur conserve lors de la répartition avec les Délégateurs. -- Effective Reward Cut - la réduction des récompenses d'indexation appliquée au pool de délégation. Si elle est négative, cela signifie que l'Indexeur donne une partie de ses récompenses. Si elle est positive, cela signifie que l'Indexeur garde une partie de ses récompenses. -- Cooldown Remaining - le temps restant avant que l'Indexeur puisse modifier les paramètres de délégation ci-dessus. Les périodes de cooldown sont définies par les Indexeurs lorsqu'ils mettent à jour leurs paramètres de délégation. -- Owned - Il s'agit du staking de l'Indexeur, qui peut être partiellement confisquée en cas de comportement malveillant ou incorrect. -- Delegated - Le staking des Délégateurs qui peut être allouée par l'Indexeur, mais ne peut pas être confisquée. -- Alloué - Le Staking que les Indexeurs allouent activement aux subgraphs qu'ils indexent. -- Available Delegation Capacity - le staking délégué que les Indexeurs peuvent encore recevoir avant d'être sur-délégués. -- Capacité de délégation maximale : montant maximum de participation déléguée que l'indexeur peut accepter de manière productive. Une mise déléguée excédentaire ne peut pas être utilisée pour le calcul des allocations ou des récompenses. -- Query Fees - il s'agit du total des frais que les utilisateurs finaux ont payés pour les requêtes d'un Indexeur au fil du temps. -- Récompenses de l'indexeur - il s'agit du total des récompenses de l'indexeur gagnées par l'indexeur et ses délégués sur toute la durée. Les récompenses des indexeurs sont payées par l'émission de GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Les Indexeurs peuvent gagner à la fois des frais de requête et des récompenses d'indexation. Fonctionnellement, cela se produit lorsque les participants au réseau délèguent des GRT à un Indexeur. Cela permet aux Indexeurs de recevoir des frais de requête et des récompenses en fonction de leurs paramètres d'Indexeur. @@ -86,9 +106,9 @@ Les Indexeurs peuvent gagner à la fois des frais de requête et des récompense Pour en savoir plus sur la façon de devenir Indexeur, vous pouvez consulter la [documentation officielle](/indexing/overview/) ou les [guides de l'Indexeur de The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) -![Volet Détails de l'indexation](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curateurs +#### Curators Les Curateurs analysent les subgraphs afin d'identifier ceux qui sont de la plus haute qualité. Une fois qu'un Curateur a trouvé un subgraph potentiellement de haute qualité, il peut le curer en signalant sa courbe de liaison. Ce faisant, les Curateurs indiquent aux Indexeurs quels subgraphs sont de haute qualité et devraient être indexés. @@ -102,11 +122,11 @@ Dans le tableau des Curateurs ci-dessous, vous pouvez voir : - Le nombre de GRT déposés - Nombre d'actions détenues par un curateur -![Image 6 de l'Explorer](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez consulter la [documentation officielle](/resources/roles/curating/) ou [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Délégués +#### Délégateurs Les Délégateurs jouent un rôle clé dans le maintien de la sécurité et de la décentralisation de The Graph Network. Ils participent au réseau en déléguant (c'est-à-dire en "stakant") des jetons GRT à un ou plusieurs Indexeurs. @@ -114,7 +134,7 @@ Les Délégateurs jouent un rôle clé dans le maintien de la sécurité et de l - Les Délégateurs sélectionnent leurs Indexeurs selon divers critères, telles que les performances passées, les taux de récompense d'indexation et le partage des frais. - La réputation au sein de la communauté peut également jouer un rôle dans le processus de sélection. Il est recommandé d'entrer en contact avec les Indexeurs sélectionnés via le [Discord de The Graph](https://discord.gg/graphprotocol) ou le [Forum de The Graph] (https://forum.thegraph.com/). -![Image 7 de l'Explorer](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) Dans le tableau des Délégateurs, vous pouvez voir les Délégateurs actifs dans la communauté et les métriques importantes : @@ -127,9 +147,9 @@ Dans le tableau des Délégateurs, vous pouvez voir les Délégateurs actifs dan Si vous souhaitez en savoir plus sur la façon de devenir Déléguateur, consultez la [documentation officielle](/resources/roles/delegating/delegating/) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Page de réseau +### Step 4. Analyze Network Performance -Sur cette page, vous pouvez voir les KPIs globaux et avoir la possibilité de passer à une base par époque et d'analyser les métriques du réseau plus en détail. Ces détails vous donneront une idée des performances du réseau au fil du temps. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Aperçu @@ -147,7 +167,7 @@ Quelques détails clés à noter : - **Les frais de requête représentent les frais générés par les consommateurs**. Ils peuvent être réclamés (ou non) par les Indexeurs après une période d'au moins 7 époques (voir ci-dessous) après que leurs allocations vers les subgraphs ont été clôturées et que les données qu'ils ont servies ont été validées par les consommateurs. - **Les récompenses d'indexation représentent le montant des récompenses que les Indexeurs ont réclamé de l'émission du réseau au cours de l'époque.** Bien que l'émission du protocole soit fixe, les récompenses ne sont mintées qu'une fois que les Indexeurs ont fermé leurs allocations vers les subgraphs qu'ils ont indexés. Ainsi, le nombre de récompenses par époque varie (par exemple, au cours de certaines époques, les Indexeurs peuvent avoir fermé collectivement des attributions qui étaient ouvertes depuis plusieurs jours). -![Image 8 de l'Explorer](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Époques @@ -161,69 +181,77 @@ Dans la section Époques, vous pouvez analyser, époque par époque, des métriq - Les époques de distribution sont les époques au cours desquelles les canaux d'État pour les époques sont réglés et les indexeurs peuvent réclamer leurs remises sur les frais de requête. - Les époques finalisées sont les époques qui n'ont plus de remboursements de frais de requête à réclamer par les Indexeurs. -![Image 9 de l'Explorer](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Votre profil d'utilisateur +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Votre profil personnel est l'endroit où vous pouvez voir votre activité sur le réseau, quel que soit votre rôle sur le réseau. Votre portefeuille crypto agira comme votre profil utilisateur, et avec le tableau de bord utilisateur, vous pourrez voir les onglets suivants : +### Step 2. Explore the Tabs -### Aperçu du profil +#### Aperçu du profil Dans cette section, vous pouvez voir ce qui suit : -- Toutes les actions en cours que vous avez effectuées. -- Les informations de votre profil, description et site web (si vous en avez ajouté un). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Image 10 de l'Explorer](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Onglet Subgraphs +#### Onglet Subgraphs -Dans l'onglet Subgraphs, vous verrez les subgraphs publiés. +The Subgraphs tab displays all your published Subgraphs. -> Cela n'inclut pas les subgraphs déployés avec la CLI à des fins de test. Les subgraphs n'apparaîtront que lorsqu'ils seront publiés sur le réseau décentralisé. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Image 11 de l'Explorer](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Onglet Indexation +#### Onglet Indexation -Dans l'onglet Indexation, vous trouverez un tableau avec toutes les allocations actives et historiques vers les subgraphs. Vous trouverez également des graphiques qui vous permettront de voir et d'analyser vos performances passées en tant qu'Indexeur. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Cette section comprendra également des détails sur vos récompenses nettes d'indexeur et vos frais de requête nets. Vous verrez les métriques suivantes : +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Participation déléguée - la participation des délégués qui peut être allouée par vous mais ne peut pas être réduite -- Total des frais de requête - le total des frais payés par les utilisateurs pour les requêtes que vous leur avez adressées au fil du temps -- Récompenses de l'indexeur - le montant total des récompenses de l'indexeur que vous avez reçues, en GRT -- Réduction des frais : % de remise sur les frais de requête que vous conserverez lors de votre séparation avec les délégués -- Récompenses de l'indexeur - le montant total des récompenses de l'indexeur que vous avez reçues, en GRT -- Possédé : votre mise déposée, qui pourrait être réduite en cas de comportement malveillant ou incorrect +Track your Indexer performance with visual charts and key metrics, including: -![Image 12 de l'Explorer](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Onglet Délégation +![Indexer Stats](/img/Indexer-Stats.png) -Les Délégateurs sont importants pour The Graph Network. Ils doivent utiliser leurs connaissances pour choisir un Indexeur qui fournira un bon rendement sur les récompenses. +#### Onglet Délégation -Dans l'onglet Délégateurs, vous pouvez trouver les détails de vos délégations actives et historiques, ainsi que les métriques des Indexeurs vers lesquels vous avez délégué. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -Dans la première moitié de la page, vous pouvez voir votre diagramme de délégation, ainsi que le diagramme des récompenses uniquement. À gauche, vous pouvez voir les indicateurs clés de performance qui reflètent vos paramètres de délégation actuels. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Les métriques du délégué que vous verrez ici dans cet onglet incluent : +Top Section: -- Récompenses totales de la délégation -- Récompenses totales non réalisées -- Récompenses totales réalisées +- View delegation and rewards-only charts +- Track key metrics: + - Récompenses totales de la délégation + - Unrealized rewards + - Realized Rewards -Dans la seconde moitié de la page, vous avez le tableau des délégations. Ici, vous pouvez voir les indexeurs auxquels vous avez délégué, ainsi que leurs détails (tels que les réductions de récompenses, le temps de recharge, etc.). +Bottom Section: -Les boutons situés à droite du tableau vous permettent de gérer votre délégation - déléguer davantage, dé-déléguer ou retirer votre délégation après la période de dégel. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Gardez à l'esprit que ce graph peut être parcouru horizontalement, donc si vous le faites défiler jusqu'à la droite, vous pouvez également voir le statut de votre délégation (en cours de délégation, non-déléguée, en cours de retrait). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Image 13 de l'Explorer](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Onglet Conservation +#### Onglet Conservation -Dans l'onglet Curation, vous trouverez tous les subgraphs que vous signalez (ce qui vous permet de recevoir des frais de requête). La signalisation permet aux Curateurs d'indiquer aux Indexeurs les subgraphs qui ont de la valeur et qui sont dignes de confiance, signalant ainsi qu'ils doivent être indexés. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Dans cet onglet, vous trouverez un aperçu de : @@ -232,22 +260,22 @@ Dans cet onglet, vous trouverez un aperçu de : - Récompenses pour les requêtes par subgraph - Détails mis à jour -![Image 14 de l'Explorer](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Paramètres de votre profil +#### Paramètres de votre profil Dans votre profil utilisateur, vous pourrez gérer les détails de votre profil personnel (comme la configuration d'un nom ENS). Si vous êtes un indexeur, vous avez encore plus accès aux paramètres à portée de main. Dans votre profil utilisateur, vous pourrez configurer vos paramètres et opérateurs de délégation. - Les opérateurs effectuent des actions limitées dans le protocole au nom de l'indexeur, telles que l'ouverture et la clôture des allocations. Les opérateurs sont généralement d'autres adresses Ethereum, distinctes de leur portefeuille de jalonnement, avec un accès sécurisé au réseau que les indexeurs peuvent définir personnellement - Les paramètres de délégation vous permettent de contrôler la répartition des GRT entre vous et vos délégués. -![Image 15 de l'Explorer](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) En tant que portail officiel dans le monde des données décentralisées, Graph Explorer vous permet de prendre diverses actions, quel que soit votre rôle dans le réseau. Vous pouvez accéder aux paramètres de votre profil en ouvrant le menu déroulant à côté de votre adresse, puis en cliquant sur le bouton Paramètres. ![détails du portefeuille](/img/Wallet-Details.png) -## Ressources supplémentaires +### Ressources supplémentaires ### Guide Vidéo From 6fc7461624f40b700322d5893ebc6aa35962b8aa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:17 -0400 Subject: [PATCH 139/290] New translations explorer.mdx (Romanian) --- website/src/pages/ro/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ro/subgraphs/explorer.mdx b/website/src/pages/ro/subgraphs/explorer.mdx index 499fcede88d3..ddb6ad1b39b6 100644 --- a/website/src/pages/ro/subgraphs/explorer.mdx +++ b/website/src/pages/ro/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- View more details such as charts, current deployment ID, and other metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraph stats (allocations, Curators, etc) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - this is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - The number of GRT that was deposited - The number of shares a Curator owns -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - The distributing epochs are the epochs in which the state channels for the epochs are being settled and Indexers can claim their query fee rebates. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Your User Profile +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profile Overview +#### Profile Overview In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphs Tab +#### Subgraphs Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - the stake from Delegators that can be allocated by you but cannot be slashed -- Total Query Fees - the total fees that users have paid for queries served by you over time -- Indexer Rewards - the total amount of Indexer rewards you have received, in GRT -- Fee Cut - the % of query fee rebates that you will keep when you split with Delegators -- Rewards Cut - the % of Indexer rewards that you will keep when splitting with Delegators -- Owned - your deposited stake, which could be slashed for malicious or incorrect behavior +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In the first half of the page, you can see your delegation chart, as well as the rewards-only chart. To the left, you can see the KPIs that reflect your current delegation metrics. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -The Delegator metrics you’ll see here in this tab include: +Top Section: -- Total delegation rewards -- Total unrealized rewards -- Total realized rewards +- View delegation and rewards-only charts +- Track key metrics: + - Total delegation rewards + - Unrealized rewards + - Realized Rewards -In the second half of the page, you have the delegations table. Here you can see the Indexers that you delegated towards, as well as their details (such as rewards cuts, cooldown, etc). +Bottom Section: -With the buttons on the right side of the table, you can manage your delegation - delegate more, undelegate, or withdraw your delegation after the thawing period. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Keep in mind that this chart is horizontally scrollable, so if you scroll all the way to the right, you can also see the status of your delegation (delegating, undelegating, withdrawable). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Within this tab, you’ll find an overview of: @@ -232,22 +260,22 @@ Within this tab, you’ll find an overview of: - Query rewards per Subgraph - Updated at date details -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Your Profile Settings +#### Your Profile Settings Within your user profile, you’ll be able to manage your personal profile details (like setting up an ENS name). If you’re an Indexer, you have even more access to settings at your fingertips. In your user profile, you’ll be able to set up your delegation parameters and operators. - Operators take limited actions in the protocol on the Indexer's behalf, such as opening and closing allocations. Operators are typically other Ethereum addresses, separate from their staking wallet, with gated access to the network that Indexers can personally set - Delegation parameters allow you to control the distribution of GRT between you and your Delegators. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From fda0ad5e71d3b5574e0ac3ce31e069d5f530a7b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:18 -0400 Subject: [PATCH 140/290] New translations explorer.mdx (Spanish) --- website/src/pages/es/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/es/subgraphs/explorer.mdx b/website/src/pages/es/subgraphs/explorer.mdx index e7d1980ac05d..07b1026ec356 100644 --- a/website/src/pages/es/subgraphs/explorer.mdx +++ b/website/src/pages/es/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Descripción -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Ver más detalles como gráficos, ID de implementación actual y otros metadatos -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Estadísticas de subgrafo (asignaciones, Curadores, etc.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexadores +#### Indexadores -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity: la cantidad máxima de participación delegada que el Indexador puede aceptar de forma productiva. Un exceso de participación delegada no puede utilizarse para asignaciones o cálculos de recompensas. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards: este es el total de recompensas del Indexador obtenidas por el Indexador y sus Delegadores durante todo el tiempo que trabajaron en conjunto. Las recompensas de los Indexadores se pagan mediante la emisión de GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curadores +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - El número de GRT que se depositaron - El número de participaciones que posee un Curador -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegadores +#### Delegadores Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Descripción @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Ciclos (epochs) @@ -161,69 +181,77 @@ En la sección de Epochs, puedes analizar, por cada epoch, métricas como: - Los ciclos de distribución son los ciclos en los que los canales correspondientes a los ciclos son establecidos y los Indexadores pueden reclamar sus reembolsos correspondientes a las tarifas de consulta. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Tu perfil de usuario +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Información general del perfil +#### Información general del perfil In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Pestaña de subgrafos +#### Pestaña de subgrafos -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Pestaña de indexación +#### Pestaña de indexación -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Esta sección también incluirá detalles sobre las recompensas netas que obtienes como Indexador y las tarifas netas que recibes por cada consulta. Verás las siguientes métricas: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake: la participación de los Delegados que puedes asignar pero que no se puede recortar -- Total Query Fees: las tarifas totales que los usuarios han pagado por las consultas que has atendido durante tu participación -- Indexer Rewards: la cantidad total de recompensas que el Indexador ha recibido, se valora en GRT -- Fee Cut: es el porcentaje que obtendrás por las consultas que has atendido, estos se distribuyen al cerrar un ciclo o cuando te separes de tus delegadores -- Rewards Cut: este es el porcentaje de recompensas que dividirás con tus delegadores una vez se cierre el ciclo -- Owned: tu stake depositado, que podría reducirse por un comportamiento malicioso o incorrecto en la red +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Pestaña de delegación +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Pestaña de delegación -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -En la primera mitad de la página, puedes ver tu gráfico de delegación, así como el gráfico de recompensas históricas. A la izquierda, puedes ver los KPI que reflejan tus métricas de delegación actuales. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Las métricas de Delegador que verás aquí en esta pestaña incluyen: +Top Section: -- Recompensas totales de delegación (Total delegation rewards) -- Recompensas totales no realizadas (Total unrealized rewards) -- Recompensas totales realizadas (Total realized rewards) +- View delegation and rewards-only charts +- Track key metrics: + - Recompensas totales de delegación (Total delegation rewards) + - Unrealized rewards + - Realized Rewards -En la segunda mitad de la página, tienes la tabla de delegaciones. Aquí puedes ver los Indexadores a los que delegaste, así como sus detalles (como recortes de recompensas, tiempo de enfriamiento, etc.). +Bottom Section: -Con los botones en el lado derecho de la tabla, puedes administrar tu delegación: delegar más, quitar tu delegación o retirar tu delegación después del período de descongelación. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Con los botones situados al lado derecho de la tabla, puedes administrar tu delegación: delegar más, anular la delegación actual o retirar tu delegación después del período de descongelación. +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Pestaña de curación +#### Pestaña de curación -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Dentro de esta pestaña, encontrarás una descripción general de: @@ -232,22 +260,22 @@ Dentro de esta pestaña, encontrarás una descripción general de: - Query rewards per Subgraph - Actualizaciones de los subgrafos -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Configuración de tu perfil +#### Configuración de tu perfil Dentro de tu perfil de usuario, podrás administrar los detalles de tu perfil personal (como configurar un nombre de ENS). Si eres un Indexador, tienes aún más acceso a la configuración al alcance de tu mano. En tu perfil de usuario, podrás configurar los parámetros y operadores de tu delegación. - Los operadores toman acciones limitadas en el protocolo en nombre del Indexador, como abrir y cerrar asignaciones. Los operadores suelen ser otras direcciones de Ethereum, separadas de su billetera de staking, con acceso cerrado a la red que los Indexadores pueden configurar personalmente - Los parámetros de delegación te permiten controlar la distribución de GRT entre tu y tus Delegadores. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Recursos Adicionales +### Recursos Adicionales ### Video Guide From aadcb1f105e9215e0ad7a9f07da58d65c1c32f9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:20 -0400 Subject: [PATCH 141/290] New translations explorer.mdx (Arabic) --- website/src/pages/ar/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ar/subgraphs/explorer.mdx b/website/src/pages/ar/subgraphs/explorer.mdx index 57d7712cc383..1f4add453b77 100644 --- a/website/src/pages/ar/subgraphs/explorer.mdx +++ b/website/src/pages/ar/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## نظره عامة -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- اعرض المزيد من التفاصيل مثل المخططات و ال ID الحالي وبيانات التعريف الأخرى -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - إحصائيات subgraphs (المخصصات ، المنسقين ، إلخ) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- مكافآت المفهرس Indexer Rewards - هو مجموع مكافآت المفهرس التي حصل عليها المفهرس ومفوضيهم Delegators. تدفع مكافآت المفهرس ب GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 3. المفوضون Delegators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - عدد ال GRT الذي تم إيداعه - عدد الأسهم التي يمتلكها المنسق -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. المفوضون Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### نظره عامة @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### الفترات Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - فترات التوزيع هي تلك الفترات التي يتم فيها تسوية قنوات الحالة للفترات ويمكن للمفهرسين المطالبة بخصم رسوم الاستعلام الخاصة بهم. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## ملف تعريف المستخدم الخاص بك +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### نظرة عامة على الملف الشخصي +#### نظرة عامة على الملف الشخصي In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### تبويب ال Subgraphs +#### تبويب ال Subgraphs -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### تبويب الفهرسة +#### تبويب الفهرسة -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -هذا القسم سيتضمن أيضا تفاصيل حول صافي مكافآت المفهرس ورسوم الاستعلام الصافي الخاصة بك. سترى المقاييس التالية: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- الحصة المفوضة Delegated Stake - هي الحصة المفوضة من قبل المفوضين والتي يمكنك تخصيصها ولكن لا يمكن شطبها -- إجمالي رسوم الاستعلام Total Query Fees - هو إجمالي الرسوم التي دفعها المستخدمون مقابل الاستعلامات التي قدمتها بمرور الوقت -- مكافآت المفهرس Indexer Rewards - هو المبلغ الإجمالي لمكافآت المفهرس التي تلقيتها ك GRT -- اقتطاع الرسوم Fee Cut -هي النسبة المئوية لخصوم رسوم الاستعلام التي ستحتفظ بها عند التقسيم مع المفوضين -- اقتطاع المكافآت Rewards Cut -هي النسبة المئوية لمكافآت المفهرس التي ستحتفظ بها عند التقسيم مع المفوضين -- مملوكة Owned - هي حصتك المودعة ، والتي يمكن شطبها بسبب السلوك الضار أو غير الصحيح +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### تبويب التفويض Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### تبويب التفويض Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -في النصف الأول من الصفحة ، يمكنك رؤية مخطط التفويض الخاص بك ، بالإضافة إلى مخطط المكافآت فقط. إلى اليسار ، يمكنك رؤية KPIs التي تعكس مقاييس التفويض الحالية. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -مقاييس التفويض التي ستراها هنا في علامة التبويب هذه تشمل ما يلي: +Top Section: -- إجمالي مكافآت التفويض -- إجمالي المكافآت الغير محققة -- إجمالي المكافآت المحققة +- View delegation and rewards-only charts +- Track key metrics: + - إجمالي مكافآت التفويض + - Unrealized rewards + - Realized Rewards -في النصف الثاني من الصفحة ، لديك جدول التفويضات. هنا يمكنك رؤية المفهرسين الذين فوضتهم ، بالإضافة إلى تفاصيلهم (مثل المكافآت المقتطعة rewards cuts، و cooldown ، الخ). +Bottom Section: -باستخدام الأزرار الموجودة على الجانب الأيمن من الجدول ، يمكنك إدارة التفويض - تفويض المزيد أو إلغاء التفويض أو سحب التفويض بعد فترة الإذابة. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -باستخدام الأزرار الموجودة على الجانب الأيمن من الجدول ، يمكنك إدارة تفويضاتك أو تفويض المزيد أو إلغاء التفويض أو سحب التفويض بعد فترة الذوبان thawing. +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### تبويب التنسيق Curating +#### تبويب التنسيق Curating -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. ضمن علامة التبويب هذه ، ستجد نظرة عامة حول: @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - تحديث في تفاصيل التاريخ -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### إعدادات ملف التعريف الخاص بك +#### إعدادات ملف التعريف الخاص بك ضمن ملف تعريف المستخدم الخاص بك ، ستتمكن من إدارة تفاصيل ملفك الشخصي (مثل إعداد اسم ENS). إذا كنت مفهرسا ، فستستطيع الوصول إلى إعدادت أكثر. في ملف تعريف المستخدم الخاص بك ، ستتمكن من إعداد بارامترات التفويض والمشغلين. - Operators تتخذ إجراءات محدودة في البروتوكول نيابة عن المفهرس ، مثل عمليات فتح وإغلاق المخصصات. Operators هي عناوين Ethereum أخرى ، منفصلة عن محفظة staking الخاصة بهم ، مع بوابة وصول للشبكة التي يمكن للمفهرسين تعيينها بشكل شخصي - تسمح لك بارامترات التفويض بالتحكم في توزيع GRT بينك وبين المفوضين. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## مصادر إضافية +### مصادر إضافية ### Video Guide From 9c16612e403366cb2246fe12c77c515b9fa863c6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:21 -0400 Subject: [PATCH 142/290] New translations explorer.mdx (Czech) --- website/src/pages/cs/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/cs/subgraphs/explorer.mdx b/website/src/pages/cs/subgraphs/explorer.mdx index 2d918567ee9d..ef576d74973a 100644 --- a/website/src/pages/cs/subgraphs/explorer.mdx +++ b/website/src/pages/cs/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Průzkumník grafů --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Přehled -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Zobrazit další podrobnosti, například grafy, ID aktuálního nasazení a další metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Statistiky podgrafů (alokace, kurátoři atd.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexery +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Maximální kapacita delegování - maximální množství delegovaných podílů, které může indexátor produktivně přijmout. Nadměrný delegovaný podíl nelze použít pro alokace nebo výpočty odměn. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Odměny indexátorů - jedná se o celkové odměny indexátorů, které indexátor a jeho delegáti získali za celou dobu. Odměny indexátorů jsou vypláceny prostřednictvím vydání GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Kurátoři +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - Počet uložených GRT - Počet akcií, které kurátor vlastní -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegáti +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Přehled @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ V části Epochy můžete na základě jednotlivých epoch analyzovat metriky, j - Distribuční epochy jsou epochy, ve kterých se vypořádávají státní kanály pro epochy a indexátoři si mohou nárokovat slevy z poplatků za dotazy. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Váš uživatelský profil +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Přehled profilů +#### Přehled profilů In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Tab Podgrafy +#### Tab Podgrafy -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Tab Indexování +#### Tab Indexování -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Tato část bude také obsahovat podrobnosti o vašich čistých odměnách za indexování a čistých poplatcích za dotazy. Zobrazí se následující metriky: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegovaná sázka – sázka od delegátů, kterou můžete přidělit vy, ale nelze ji snížit -- Celkové poplatky za dotazy - celkové poplatky, které uživatelé zaplatili za dotazy, které jste obsloužili v průběhu času -- Odměny indexátora - celková částka odměn indexátora, kterou jste obdrželi, v GRT -- Fee Cut - % slevy z poplatku za dotaz, které si ponecháte při rozdělení s delegáty -- Rozdělení odměn - % odměn indexátorů, které si ponecháte při dělení s delegáty -- Ve vlastnictví - váš vložený vklad, který může být snížen za škodlivé nebo nesprávné chování +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Tab Delegování +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Tab Delegování -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -V první polovině stránky vidíte graf delegování a také graf odměn. Vlevo vidíte klíčové ukazatele výkonnosti, které odrážejí vaše aktuální metriky delegování. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Metriky delegáta, které uvidíte na této tab, zahrnují: +Top Section: -- Celkové odměny za delegování -- Nerealizované odměny celkem -- Celkové realizované odměny +- View delegation and rewards-only charts +- Track key metrics: + - Celkové odměny za delegování + - Unrealized rewards + - Realized Rewards -V druhé polovině stránky je tabulka delegací. Zde vidíte indexátory, které jste delegovali, a také jejich podrobnosti (například snížení odměn, zkrácení doby platnosti atd.). +Bottom Section: -Pomocí tlačítek na pravé straně tabulky můžete spravovat delegování - delegovat více, zrušit delegování nebo stáhnout delegování po uplynutí doby rozmrazení. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Nezapomeňte, že tento graf lze horizontálně posouvat, takže pokud se posunete úplně doprava, uvidíte také stav svého delegování (delegování, nedelegování, odvolání). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Tab Kurátorství +#### Tab Kurátorství -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Na této tab najdete přehled: @@ -232,22 +260,22 @@ Na této tab najdete přehled: - Query rewards per Subgraph - Aktualizováno v detailu data -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Nastavení profilu +#### Nastavení profilu Ve svém uživatelském profilu budete moci spravovat své osobní údaje (například nastavit jméno ENS). Jste-li indexátorem, máte k dispozici ještě více nastavení. Ve svém uživatelském profilu budete moci nastavit parametry delegování a operátory. - Operátoři provádějí v protokolu jménem indexátoru omezené akce, například otevírají a zavírají alokace. Operátoři jsou obvykle jiné adresy Ethereum, oddělené od jejich stakingové peněženky, s uzavřeným přístupem do sítě, který si indexátoři mohou osobně nastavit - Parametry delegování umožňují řídit rozdělení GRT mezi vás a vaše delegáty. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Další zdroje +### Další zdroje ### Video Guide From 86dffb34251a8f4870d3be048ee7b1f616a865f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:22 -0400 Subject: [PATCH 143/290] New translations explorer.mdx (Italian) --- website/src/pages/it/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/it/subgraphs/explorer.mdx b/website/src/pages/it/subgraphs/explorer.mdx index 5db7212c1fb0..c249b659cdb3 100644 --- a/website/src/pages/it/subgraphs/explorer.mdx +++ b/website/src/pages/it/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Panoramica -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Visualizza ulteriori dettagli, come grafici, ID di distribuzione corrente e altri metadati -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Statistiche del subgraph (allocazione, Curator, ecc.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexer +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - l'importo massimo di stake delegato che l'Indexer può accettare in modo produttivo. Uno stake delegato in eccesso non può essere utilizzato per l'allocazione o per il calcolo dei premi. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - è il totale delle ricompense dell'Indexer guadagnate dall'Indexer e dai suoi Delegator in tutto il tempo. Le ricompense degli Indexer vengono pagate tramite l'emissione di GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curator +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - Il numero di GRT depositato - Il numero di azioni possedute da un Curator -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegator +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Panoramica @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epoche @@ -161,69 +181,77 @@ Nella sezione Epoche è possibile analizzare su base epocale metriche come: - Le epoche di distribuzione sono le epoche in cui i canali di stato per le epoche vengono regolati e gli Indexer possono richiedere gli sconti sulle tariffe di query. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Il profilo utente +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Panoramica del profilo +#### Panoramica del profilo In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Scheda di subgraph +#### Scheda di subgraph -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Scheda di indicizzazione +#### Scheda di indicizzazione -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Questa sezione include anche i dettagli sui compensi netti degli Indexer e sulle tariffe nette di query. Verranno visualizzate le seguenti metriche: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake (stake delegato)- lo stake dei Delegator che può essere assegnata dall'utente, ma che non può essere tagliata -- Total Query Fees (totale delle tariffe di query)- il totale delle tariffe che gli utenti hanno pagato per le query servite da voi nel tempo -- Indexer Rewards (ricompense dell'Indexer) - l'importo totale delle ricompense dell'Indexer ricevuti, in GRT -- Fee Cut (percentuale delle tariffe) - la percentuale dei rimborsi delle tariffe di query che si trattiene quando si divide con i Delegator -- Rewards Cut (percentuale delle ricompense) - la percentuale delle ricompense dell'Indexer che verrà trattenuta quando si divide con i Delegator -- Owned (di proprietà)- la quota depositata, che potrebbe essere tagliata in caso di comportamento dannoso o scorretto +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Scheda di delege +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Scheda di delege -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -Nella prima metà della pagina è possibile vedere il grafico delle deleghe e quello dei sole ricompense. A sinistra, si possono vedere i KPI che riflettono le metriche delle delega attuali. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Le metriche del Delegator visualizzate in questa scheda includono: +Top Section: -- Ricompense di delega totali -- Ricompense totali non realizzate -- Ricomepsne totali realizzate +- View delegation and rewards-only charts +- Track key metrics: + - Ricompense di delega totali + - Unrealized rewards + - Realized Rewards -Nella seconda metà della pagina si trova la tabella dei Delegator. Qui si possono vedere gli Indexer verso i quali si è delegata la delega, nonché i loro dettagli (come le percentuali delle ricompense, il cooldown, ecc.). +Bottom Section: -Con i pulsanti sul lato destro della tabella è possibile gestire la delega - delegare di più, non delegare o ritirare la delega dopo il periodo di scongelamento. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Tenete presente che questo grafico è scorrevole orizzontalmente, quindi se scorrete fino a destra, potete anche vedere lo stato della vostra delegazione (delegante, non delegante, revocabile). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Scheda di curation +#### Scheda di curation -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. All'interno di questa scheda è presente una panoramica di: @@ -232,22 +260,22 @@ All'interno di questa scheda è presente una panoramica di: - Query rewards per Subgraph - Aggiornamento attuale dei dettagli -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Impostazioni del profilo +#### Impostazioni del profilo All'interno del vostro profilo utente, potrete gestire i dettagli del vostro profilo personale (come impostare un nome ENS). Se siete un Indexer, avrete ancora più accesso alle impostazioni a portata di mano. Nel vostro profilo utente, potrete impostare i parametri di delegazione e gli operatori. - Gli operatori compiono azioni limitate nel protocollo per conto dell'Indexer, come l'apertura e la chiusura delle allocation. Gli operatori sono in genere altri indirizzi Ethereum, separati dal loro wallet di staking, con un accesso limitato alla rete che gli Indexer possono impostare personalmente - I parametri di delega vi permettono di controllare la distribuzione di GRT tra voi e i vostri Delegator. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From 49db5680707f1b8b0ce4e172aa876a3f7a9fa0fa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:23 -0400 Subject: [PATCH 144/290] New translations explorer.mdx (Korean) --- website/src/pages/ko/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ko/subgraphs/explorer.mdx b/website/src/pages/ko/subgraphs/explorer.mdx index 499fcede88d3..ddb6ad1b39b6 100644 --- a/website/src/pages/ko/subgraphs/explorer.mdx +++ b/website/src/pages/ko/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- View more details such as charts, current deployment ID, and other metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraph stats (allocations, Curators, etc) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - this is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - The number of GRT that was deposited - The number of shares a Curator owns -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - The distributing epochs are the epochs in which the state channels for the epochs are being settled and Indexers can claim their query fee rebates. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Your User Profile +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profile Overview +#### Profile Overview In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphs Tab +#### Subgraphs Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - the stake from Delegators that can be allocated by you but cannot be slashed -- Total Query Fees - the total fees that users have paid for queries served by you over time -- Indexer Rewards - the total amount of Indexer rewards you have received, in GRT -- Fee Cut - the % of query fee rebates that you will keep when you split with Delegators -- Rewards Cut - the % of Indexer rewards that you will keep when splitting with Delegators -- Owned - your deposited stake, which could be slashed for malicious or incorrect behavior +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In the first half of the page, you can see your delegation chart, as well as the rewards-only chart. To the left, you can see the KPIs that reflect your current delegation metrics. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -The Delegator metrics you’ll see here in this tab include: +Top Section: -- Total delegation rewards -- Total unrealized rewards -- Total realized rewards +- View delegation and rewards-only charts +- Track key metrics: + - Total delegation rewards + - Unrealized rewards + - Realized Rewards -In the second half of the page, you have the delegations table. Here you can see the Indexers that you delegated towards, as well as their details (such as rewards cuts, cooldown, etc). +Bottom Section: -With the buttons on the right side of the table, you can manage your delegation - delegate more, undelegate, or withdraw your delegation after the thawing period. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Keep in mind that this chart is horizontally scrollable, so if you scroll all the way to the right, you can also see the status of your delegation (delegating, undelegating, withdrawable). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Within this tab, you’ll find an overview of: @@ -232,22 +260,22 @@ Within this tab, you’ll find an overview of: - Query rewards per Subgraph - Updated at date details -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Your Profile Settings +#### Your Profile Settings Within your user profile, you’ll be able to manage your personal profile details (like setting up an ENS name). If you’re an Indexer, you have even more access to settings at your fingertips. In your user profile, you’ll be able to set up your delegation parameters and operators. - Operators take limited actions in the protocol on the Indexer's behalf, such as opening and closing allocations. Operators are typically other Ethereum addresses, separate from their staking wallet, with gated access to the network that Indexers can personally set - Delegation parameters allow you to control the distribution of GRT between you and your Delegators. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From fbb1e25f1e38a38b70129b680b0a3998de72a348 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:24 -0400 Subject: [PATCH 145/290] New translations explorer.mdx (Dutch) --- website/src/pages/nl/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/nl/subgraphs/explorer.mdx b/website/src/pages/nl/subgraphs/explorer.mdx index 3df0b99d43ca..9a0c6aa80167 100644 --- a/website/src/pages/nl/subgraphs/explorer.mdx +++ b/website/src/pages/nl/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Verkenner --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Details zoals grafieken, huidige implementatie-ID en andere metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraphstatistieken (allocaties, curatoren, etc.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - het maximale bedrag aan gedelegeerde inzet dat de Indexer productief kan accepteren. Een teveel aan gedelegeerde inzet kan niet worden gebruikt voor allocaties of beloningsberekeningen. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - dit zijn de totale indexerbeloningen die door de Indexer en hun Delegeerders zijn verdiend. Indexerbeloningen worden uitbetaald via de uitgifte van GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curatoren +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - Het gestorte aantal GRT - Het aantal curator-aandelen in het bezit van de curator -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In de Epochs afdeling kun je per epoch verschillende metrieken analyseren, zoals - De distribuerende epochs zijn de epochs waarin de state channels voor de epochs worden afgehandeld en Indexeerders hun querykostenkorting kunnen claimen. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Uw Gebruikersprofiel +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profieloverzicht +#### Profieloverzicht In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraph Tab +#### Subgraph Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Dit gedeelte bevat ook details over uw netto indexeringsbeloningen en netto querykosten. U zult de volgende metrics zien: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Gedelegeerde GRT - de GRT van Delegators die door u kan worden toegewezen, maar die niet kan worden geslashed -- Totale Querykosten - de totale kosten die door gebruikers in de loop van de tijd hebben betaald voor queries die door u zijn verwerkt -- Indexer-beloningen - het totale bedrag aan Indexer-beloningen dat u heeft ontvangen, in GRT -- Fee Cut - het percentage van de query fee rebates dat u houdt wanneer u het splitst met Delegators -- Reward Cut - het % van Indexer-beloningen dat u houdt bij het splitsen met Delegators -- Owned - jouw eigen gestorte inzet, die kan worden geslashed voor kwaadaardig of incorrect gedrag +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In de eerste helft van de pagina kunt u uw delegatiegrafiek zien, evenals de alleen-beloningen-grafiek. Aan de linkerkant kun u de KPI's zien die uw huidige delegatiemetrics weerspiegelen. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -De Delegator-metrieken die u hier in deze tab zult zien, omvatten: +Top Section: -- Totale delegatiebeloningen -- Totale niet-gerealiseerde beloningen -- Totaal gerealiseerde beloningen +- View delegation and rewards-only charts +- Track key metrics: + - Totale delegatiebeloningen + - Unrealized rewards + - Realized Rewards -In de tweede helft van de pagina heeft u de delegatietabel. Hier kunt u de Indexeerders zien waarnaar u hebt gedelegeerd, evenals hun parameters (zoals beloningsverlagingen, afkoelperiode, enz.). +Bottom Section: -Met de knoppen aan de rechterkant van de tabel kunt u uw delegatie beheren - meer delegeren, stoppen met delegeren of uw delegatie opnemen na de ontdooiperiode. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Houd er rekening mee dat deze grafiek horizontaal scrollbaar is, dus als u helemaal naar rechts scrolt, kunt u ook de status van uw delegatie zien (delegeren, ontdooien, opneembaar). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Binnen deze tab vind je een overzicht van: @@ -232,22 +260,22 @@ Binnen deze tab vind je een overzicht van: - Query rewards per Subgraph - Gegevens van de bijwerkdatum -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Jouw profielinstellingen +#### Jouw profielinstellingen Binnen je gebruikersprofiel kun je je persoonlijke profielgegevens beheren (zoals het instellen van een ENS-naam). Als je een Indexeerder bent, heb je nog meer toegang tot instellingen binnen handbereik. In je gebruikersprofiel kun je je delegatieparameters en operators instellen. - Operators nemen beperkte acties in het protocol namens de Indexer, zoals het openen en sluiten van allocaties. Operators zijn doorgaans andere Ethereum-adressen, los van hun wallet die inzet, met beperkte toegang tot het netwerk die Indexeerders persoonlijk kunnen instellen - Delegatieparameters stellen je in staat om de verdeling van GRT tussen jou en je Delegators te regelen. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From 4b03c094853b83831546499afd85b930ae049cfb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:26 -0400 Subject: [PATCH 146/290] New translations explorer.mdx (Polish) --- website/src/pages/pl/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/pl/subgraphs/explorer.mdx b/website/src/pages/pl/subgraphs/explorer.mdx index 499fcede88d3..ddb6ad1b39b6 100644 --- a/website/src/pages/pl/subgraphs/explorer.mdx +++ b/website/src/pages/pl/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- View more details such as charts, current deployment ID, and other metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraph stats (allocations, Curators, etc) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - this is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - The number of GRT that was deposited - The number of shares a Curator owns -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - The distributing epochs are the epochs in which the state channels for the epochs are being settled and Indexers can claim their query fee rebates. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Your User Profile +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profile Overview +#### Profile Overview In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphs Tab +#### Subgraphs Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - the stake from Delegators that can be allocated by you but cannot be slashed -- Total Query Fees - the total fees that users have paid for queries served by you over time -- Indexer Rewards - the total amount of Indexer rewards you have received, in GRT -- Fee Cut - the % of query fee rebates that you will keep when you split with Delegators -- Rewards Cut - the % of Indexer rewards that you will keep when splitting with Delegators -- Owned - your deposited stake, which could be slashed for malicious or incorrect behavior +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In the first half of the page, you can see your delegation chart, as well as the rewards-only chart. To the left, you can see the KPIs that reflect your current delegation metrics. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -The Delegator metrics you’ll see here in this tab include: +Top Section: -- Total delegation rewards -- Total unrealized rewards -- Total realized rewards +- View delegation and rewards-only charts +- Track key metrics: + - Total delegation rewards + - Unrealized rewards + - Realized Rewards -In the second half of the page, you have the delegations table. Here you can see the Indexers that you delegated towards, as well as their details (such as rewards cuts, cooldown, etc). +Bottom Section: -With the buttons on the right side of the table, you can manage your delegation - delegate more, undelegate, or withdraw your delegation after the thawing period. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Keep in mind that this chart is horizontally scrollable, so if you scroll all the way to the right, you can also see the status of your delegation (delegating, undelegating, withdrawable). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Within this tab, you’ll find an overview of: @@ -232,22 +260,22 @@ Within this tab, you’ll find an overview of: - Query rewards per Subgraph - Updated at date details -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Your Profile Settings +#### Your Profile Settings Within your user profile, you’ll be able to manage your personal profile details (like setting up an ENS name). If you’re an Indexer, you have even more access to settings at your fingertips. In your user profile, you’ll be able to set up your delegation parameters and operators. - Operators take limited actions in the protocol on the Indexer's behalf, such as opening and closing allocations. Operators are typically other Ethereum addresses, separate from their staking wallet, with gated access to the network that Indexers can personally set - Delegation parameters allow you to control the distribution of GRT between you and your Delegators. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From f6383961d077a79ce42dad0e7fbe93a54186f8c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:27 -0400 Subject: [PATCH 147/290] New translations explorer.mdx (Swedish) --- website/src/pages/sv/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/sv/subgraphs/explorer.mdx b/website/src/pages/sv/subgraphs/explorer.mdx index 87b670a3247d..c22e0a0ec72b 100644 --- a/website/src/pages/sv/subgraphs/explorer.mdx +++ b/website/src/pages/sv/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graf Utforskaren --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Översikt -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Visa mer detaljer som diagram, aktuell distributions-ID och annan metadata -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraffstatistik (tilldelningar, kuratorer, etc.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexerare +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Maximal delegeringskapacitet - den maximala mängden delegerad insats som indexeraren produktivt kan acceptera. Överskjuten delegerad insats kan inte användas för tilldelningar eller beräkningar av belöningar. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexeringsbelöningar - detta är de totala indexeringsbelöningarna som indexeraren och deras delegater har tjänat över tid. Indexeringsbelöningar betalas genom GRT-utgivning. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Kuratorer +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - Antalet GRT som deponerades - Antalet andelar en kurator äger -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegater +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Översikt @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epoker @@ -161,69 +181,77 @@ I avsnittet Epoker kan du analysera på en per-epok-basis, metriker som: - De distribuerande epokerna är de epoker där statliga kanaler för epokerna avvecklas och indexerare kan kräva sina frågeavgiftsrabatter. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Din användarprofil +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profilöversikt +#### Profilöversikt In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraffar-fliken +#### Subgraffar-fliken -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexeringstabell +#### Indexeringstabell -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -I det här avsnittet hittar du också information om dina nettobelöningar som indexerare och nettovärdaravgifter. Du kommer att se följande metriker: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegerad insats - insatsen från delegater som kan tilldelas av dig men inte kan straffas -- Totala frågeavgifter - de totala avgifter som användare har betalat för frågor som du har serverat över tid -- Indexeringsbelöningar - den totala mängd indexeringsbelöningar du har fått, i GRT -- Avgiftsskärning - den procentandel av frågeavgiftsrabatter som du kommer att behålla när du delar med delegater -- Belöningsrabatt - den procentandel av indexeringsbelöningar som du kommer att behålla när du delar med delegater -- Ägd - din deponerade insats, som kan straffas för skadligt eller felaktigt beteende +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegattabell +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegattabell -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -I den första halvan av sidan kan du se din delegatdiagram, liksom diagrammet för endast belöningar. Till vänster kan du se KPI:er som återspeglar dina aktuella delegationsmetriker. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -De delegatmetriker du kommer att se här i den här fliken inkluderar: +Top Section: -- Totala delegationsbelöningar -- Totala orealiserade belöningar -- Totala realiserade belöningar +- View delegation and rewards-only charts +- Track key metrics: + - Totala delegationsbelöningar + - Unrealized rewards + - Realized Rewards -I den andra halvan av sidan har du delegattabellen. Här kan du se indexerarna som du har delegerat till, samt deras detaljer (som belönningsskärningar, nedkylning, etc). +Bottom Section: -Med knapparna på höger sida av tabellen kan du hantera din delegation - delegera mer, avdelegatera eller ta tillbaka din delegation efter upptiningstiden. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Kom ihåg att denna tabell kan rullas horisontellt, så om du rullar hela vägen till höger kan du också se status för din delegation (delegering, avdelegering, återkallelig). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Kureringstabell +#### Kureringstabell -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Inom den här fliken hittar du en översikt över: @@ -232,22 +260,22 @@ Inom den här fliken hittar du en översikt över: - Query rewards per Subgraph - Uppdaterade datumdetaljer -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Dina profilinställningar +#### Dina profilinställningar Inom din användarprofil kommer du att kunna hantera dina personliga profiluppgifter (som att ställa in ett ENS-namn). Om du är indexerare har du ännu mer åtkomst till inställningar inom räckhåll. I din användarprofil kan du ställa in dina delegationsparametrar och operatörer. - Operatörer tar begränsade åtgärder i protokollet på indexerarens vägnar, såsom att öppna och stänga tilldelningar. Operatörer är vanligtvis andra Ethereum-adresser, separata från deras stakningsplånbok, med gated access till nätverket som indexerare personligen kan ställa in - Delegationsparametrar låter dig kontrollera fördelningen av GRT mellan dig och dina delegater. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Ytterligare resurser +### Ytterligare resurser ### Video Guide From d1dcd3798ee1a21fbd742f7f38f1449888a3a2ce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:28 -0400 Subject: [PATCH 148/290] New translations explorer.mdx (Turkish) --- website/src/pages/tr/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/tr/subgraphs/explorer.mdx b/website/src/pages/tr/subgraphs/explorer.mdx index 95128bd87f9e..419065d423a5 100644 --- a/website/src/pages/tr/subgraphs/explorer.mdx +++ b/website/src/pages/tr/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Gezgini --- -[Graph Gezgini](https://thegraph.com/explorer) ile Subgraph'ler ve ağ verilerinin dünyasını keşfedin. +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Genel Bakış -Graph Gezgini, birden fazla bölümden oluşur; bu bölümlerde [Subgraph'ler](https://thegraph.com/explorer?chain=arbitrum-one) ile etkileşime geçebilir, [delege etme](https://thegraph.com/explorer/delegate?chain=arbitrum-one) işlemi yapabilir, [katılımcılarla](https://thegraph.com/explorer/participants?chain=arbitrum-one) etkileşime geçebilir, [ağ bilgilerini](https://thegraph.com/explorer/network?chain=arbitrum-one) görüntüleyebilir ve kullanıcı profilinize erişebilirsiniz. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Graph Gezgini'nin İçinde +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -Aşağıda, Graph Gezgini'nin tüm temel özelliklerinin bir dökümü yer almaktadır. Ek destek için [Graph Gezgini video rehberini](/subgraphs/explorer/#video-guide) izleyebilirsiniz. +## Prerequisites -### Subgraph Sayfası +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -Subgraph'inizi Subgraph Studio'da dağıtıp yayımladıktan sonra [Graph Gezgini](https://thegraph.com/explorer) sayfasına gidin ve gezinme çubuğundaki "[Subgraph'lar](https://thegraph.com/explorer?chain=arbitrum-one)" bağlantısına tıklayarak aşağıdaki bölümlere erişin: +## Navigating Graph Explorer -- Kendi tamamlanmış Subgraph'leriniz -- Başkaları tarafından yayımlanmış subgraph'ler -- İstediğiniz spesifik bir subgraph (oluşturulma tarihi, sinyal miktarı veya adına göre). +### Step 1. Explore Subgraphs -![Gezgin Görüntüsü 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -Bir Subgraph'e tıkladığınızda aşağıdakileri yapabilirsiniz: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Oyun alanında (playground) sorguları test edin ve ağ detaylarından faydalanarak bilgili kararlar alın. -- Kendi Subgraph'inize veya başkalarının Subgraph'lerine GRT sinyali göndererek Endeksleyicilere bunların önemini ve kalitesini bildirin. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - Bu kritik bir öneme sahiptir çünkü bir Subgraph'e sinyal vermek, onun endekslenmesini teşvik eder. Bu da, sonunda ağ üzerinde ön plana çıkıp sorgulara hizmet verebileceği anlamına gelir. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Gezgin Görüntüsü 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Oyun alanında (playground) sorguları test edin ve ağ detaylarından faydalanarak bilgili kararlar alın. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) Her Subgraph'in kendi sayfasında aşağıdakileri yapabilirsiniz: -- Subgraph'lere sinyal verme/sinyal geri çekme -- Grafikler, mevcut dağıtım kimliği ve diğer üst veri gibi daha fazla ayrıntı görüntüleme -- Subgraph'in önceki sürümlerini incelemek için versiyonlar arasında geçiş yapma - Subgraph'leri GraphQL ile sorgulama +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Subgraph'leri playground ortamında test etme - Belirli bir Subgraph üzerinde endeksleme yapan Endeksleyicileri görüntüleme - Subgraph istatistikleri (tahsisler, Küratörler, vb.) -- Subgraph'i yayımlayan varlığı görüntüleme +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Gezgin Görüntüsü 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delege Etme Sayfası +### Step 2. Delegate GRT -[Delege Etme sayfasında](https://thegraph.com/explorer/delegate?chain=arbitrum-one), delege etme, GRT edinme ve bir Endeksleyici seçme hakkında bilgi bulabilirsiniz. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -Bu sayfada aşağıdakileri görüntüleyebilirsiniz: +Here, you can: -- En fazla sorgu ücretini toplayan Endeksleyiciler -- Tahmini APR'si (Yıllık Yüzde Getiri Oranı) en yüksek olan Endeksleyiciler +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Ayrıca, ROI (Yatırım Getirisi) hesaplayabilir ve öne çıkan Endeksleyicileri ada, adrese ya da Subgraph’e göre arayabilirsiniz. +### Step 3. Monitor Participants in the Network -### Katılımcı Sayfası +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -Bu sayfa, Endeksleyiciler, Delegatörler ve Küratörler gibi ağda yer alan tüm "katılımcıları" kapsayan genel bir görüntü sunar. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. İndeksleyiciler +#### Endeksleyiciler -![Gezgin Görüntüsü 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Endeksleyiciler, protokolün bel kemiğidir. Subgraph'ler üzerinde istifleme yapar, onları endeksler ve Subgraph'leri tüketen herkese sorgular sunarlar. -Endeksleyiciler tablosunda, bir Endeksleyicinin delegasyon parametrelerini, istif miktarını, her bir Subgraph'e ne kadar istifleme yaptığını ve sorgu ücretleri ile endeksleme ödüllerinden ne kadar gelir elde ettiğini görebilirsiniz. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Ayrıntılar** -- Sorgu Ücreti Kesintisi - Endeksleyicinin, Delegatörlerle paylaşırken sorgu ücreti iadelerinden kendine ayırdığı yüzdelik oran. -- Etkin Ödül Kesintisi - Delegasyon havuzuna uygulanan endeksleme ödülü kesintisi. Negatif bir değer, Endeksleyicinin kendi ödüllerinin bir kısmını dağıttığı anlamına gelir. Pozitif bir değer ise Endeksleyicinin ödüllerin bir kısmını kendine sakladığını gösterir. -- Kalan Bekleme Süresi - Endeksleyicinin yukarıdaki delegasyon parametrelerini değiştirebilmesi için kalan süre. Bekleme süreleri, Endeksleyiciler delegasyon parametrelerini güncellediğinde kendileri tarafından ayarlanır. -- Sahip Olunan - Endeksleyicinin yatırdığı istif miktarıdır ve kötü niyetli veya hatalı davranışlar nedeniyle kesinti (slashing) uygulanabilir. -- Delege Edilen - Delegatörlerden gelen ve Endeksleyici tarafından tahsis edilebilen, ancak kesintiye uğratılamayan istif. -- Tahsis Edilen - Endeksleyicilerin, endeksledikleri Subgraph'lere aktif olarak tahsis ettikleri istif. -- Mevcut Delegasyon Kapasitesi - Endeksleyicilerin kotalarını aşmadan önce alabilecekleri delege edilmiş istif miktarı. -- Maksimum Delegasyon Kapasitesi - Endekserin verimli bir şekilde kabul edebileceği en yüksek delegasyon miktarıdır. Fazla delege edilmiş pay, tahsisler veya ödül hesaplamaları için kullanılamaz. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- İndeksleyici Ödülleri - bu, İndeksleyici ve Delegatörler tarafından tüm zaman boyunca kazanılan toplam indeksleyici ödülleridir. İndeksleyici ödülleri GRT ihracı yoluyla ödenir. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe Nasıl Endeksleyici olunabileceğini daha ayrıntılı öğrenmek için [resmi dokümantasyona](/indexing/overview/) veya [The Graph Academy Endeksleyici rehberlerine](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz. -![Endeksleme detayları paneli](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Küratörler +#### Curators Küratörler, Subgraph'leri analiz ederek en yüksek kaliteye sahip olan Subgraph'leri belirler. Bir Küratör, potansiyel olarak yüksek kaliteli bir Subgraph bulduğunda, onun bağlanma eğrisine sinyal vererek küratörlük yapabilir. Küratörler böylece Endeksleyicilere hangi Subgraph'lerin yüksek kaliteli olduğunu ve hangilerinin endekslenmesi gerektiğini bildirir. @@ -102,11 +122,11 @@ Aşağıda listelenen Küratör tablosunda şunları görebilirsiniz: - Yatırılan GRT sayısı - Küratör'ün sahip olduğu hisse sayısı -![Gezgin Görüntüsü 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) Küratör rolü hakkında daha fazla bilgi edinmek isterseniz, [resmi dokümentasyon](/resources/roles/curating/)u veya [The Graph Academy](https://thegraph.academy/curators/)'yi ziyaret edebilirsiniz. -#### 3. Delegatörler +#### Delegatörler Delegatörler, The Graph Ağı'nın güvenliğinin ve merkeziyetsizliğinin korunmasında kilit bir rol oynar. Ağda, bir veya birden fazla Endeksleyiciye GRT token'larını delege ederek (yani istifleyerek, "stake" ederek) katılım sağlarlar. @@ -114,7 +134,7 @@ Delegatörler, The Graph Ağı'nın güvenliğinin ve merkeziyetsizliğinin koru - Delegatörler, geçmiş performans, endeksleme ödül oranları ve sorgu ücreti kesintileri gibi çeşitli değişkenlere dayanarak Endeksleyicileri seçerler. - Topluluk içindeki itibar da seçim sürecinde bir faktör olabilir. Seçtiğiniz Endeksleyicilerle [The Graph’in Discord sunucusu](https://discord.gg/graphprotocol) veya [The Graph Forumu](https://forum.thegraph.com/) üzerinden bağlantı kurmanız önerilir. -![Gezgin Görüntüsü 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) Delegatörler tablosunda, topluluktaki aktif Delegatörleri ve önemli metrikleri görebilirsiniz: @@ -127,9 +147,9 @@ Delegatörler tablosunda, topluluktaki aktif Delegatörleri ve önemli metrikler Delegatör olmak hakkında daha fazla bilgi edinmek isterseniz, [resmi dokümantasyon](/resources/roles/delegating/delegating/)u veya [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers)'yi ziyaret edebilirsiniz. -### Ağ Sayfası +### Step 4. Analyze Network Performance -Bu sayfada, küresel TPG'leri (temel performans göstergesi, İng. KPI) görüntüleyebilir, dönem bazlı görünüme geçiş yaparak ağ metriklerini daha ayrıntılı şekilde analiz edebilirsiniz. Bu detaylar, ağın zaman içindeki performansı hakkında bir fikir edinmenizi sağlar. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Genel Bakış @@ -147,7 +167,7 @@ Dikkat edilmesi gereken birkaç önemli detay: - **Sorgu ücretleri, tüketiciler tarafından üretilen ücretleri temsil eder**. Bu ücretler, Endeksleyiciler tarafından Subgraph'lere yönelik tahsislerin kapatılmasından ve sağlanan verilerin tüketiciler tarafından doğrulanmasından sonra, en az 7 dönemlik (aşağıya bakınız) bir sürenin ardından talep edilebilir (veya edilmeyebilir). - **Endeksleme ödülleri, Endeksleyicilerin dönem sırasında ağ ihraçlarından talep ettiği ödül miktarını temsil eder**. Protokol ihraç miktarı sabit olmasına rağmen, ödüller yalnızca Endeksleyicilerin endeksledikleri Subgraph'lere yönelik tahsislerini kapattıklarında oluşturulur. Bu nedenle, dönem başına ödül miktarı değişkenlik gösterir (örneğin, bazı dönemlerde Endeksleyiciler, günlerce açık kalmış tahsisleri topluca kapatmış olabilir). -![Gezgin Görüntüsü 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Dönemler @@ -161,69 +181,77 @@ Dönemler bölümünde, aşağıdaki gibi metrikleri dönem bazında analiz edeb - Dağıtım dönemleri, bildirim kanallarının dönemler için yerleştiği ve İndeksleyicilerin sorgu ücreti iadelerini talep edebildiği dönemlerdir. - Sonlandırılmış dönemler, Endeksleyiciler tarafından talep edilecek sorgu ücreti iadelerinin kalmadığı dönemlerdir. -![Gezgin Görüntüsü 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Kullanıcı Profiliniz +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Kişisel profiliniz, ağdaki rolünüz ne olursa olsun ağ etkinliğinizi görebileceğiniz yerdir. Kripto cüzdanınız kullanıcı profiliniz olarak işlev görecektir ve Kullanıcı Panosu ile aşağıdaki sekmeleri görüntüleyebileceksiniz: +### Step 2. Explore the Tabs -### Profile Genel Bakış +#### Profile Genel Bakış Bu bölümde aşağıdakileri görüntüleyebilirsiniz: -- Yaptığınız mevcut tüm işlemleriniz. -- Profil bilgileriniz, tanımınız ve (varsa) eklediğiniz web sitesi. +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Gezgin Görüntüsü 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphlar Sekmesi +#### Subgraphlar Sekmesi -Subgraph'ler sekmesinde, yayımladığınız Subgraph'leri göreceksiniz. +The Subgraphs tab displays all your published Subgraphs. -> Bu, test amaçlı, CLI ile dağıtılmış Subgraph'leri içermeyecektir. Subgraph'ler yalnızca merkeziyetsiz ağda yayımlandıklarında görünecektir. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Gezgin Görüntüsü 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### İndeksleme Sekmesi +#### İndeksleme Sekmesi -Endeksleme sekmesinde, Subgraph'lere yönelik tüm aktif ve geçmiş tahsislerin yer aldığı bir tablo bulacaksınız. Ayrıca, bir Endeksleyici olarak geçmiş performansınızı görebileceğiniz ve analiz edebileceğiniz grafiklere erişebilirsiniz. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Bu bölümde ayrıca net İndeksleyici ödülleriniz ve sorgu ücretlerinizle ilgili ayrıntılar da yer alacaktır. Aşağıdaki metrikleri göreceksiniz: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delege Edilen Pay - delegatörler'in sizin tarafınızdan tahsis edilebilen fakat kesilemeyen payları -- Toplam Sorgu Ücretleri - kullanıcıların zaman içinde sizin tarafınızdan sunulan sorgular için ödedikleri toplam ücretler -- İndeksleyici Ödülleri - GRT olarak aldığınız İndeksleyici ödüllerinin toplam tutarı -- Ücret Kesintisi - Delegatörlerle ayrıldığınızda elinizde kalacak sorgu ücreti iadelerinin yüzdesi -- Ödül Kesintisi - Delegatörlerle ayrılırken İndeksleyici ödüllerinin elinizde kalacak yüzdesi -- Depozito - kötü niyetli veya yanlış davranışlarınız sonucu kesilebilecek yatırılmış payınız +Track your Indexer performance with visual charts and key metrics, including: -![Gezgin Görüntüsü 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegasyon Sekmesi +![Indexer Stats](/img/Indexer-Stats.png) -Delegatörler, Graph Ağı için önemlidir. Sağlıklı bir ödül getirisi sağlayacak bir Endeksleyiciyi seçmek için bilgilerini kullanmaları gerekir. +#### Delegasyon Sekmesi -Delegatörler sekmesinde, aktif ve geçmiş delege işlemlerinizin detaylarını ve delege ettiğiniz Endeksleyicilerin metriklerini bulabilirsiniz. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -Sayfanın ilk yarısında, delegasyon grafiğinizin yanı sıra yalnızca ödül grafiğini de görebilirsiniz. Sol tarafta, mevcut delegasyon metriklerinizi yansıtan APG'leri görebilirsiniz. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Bu sekmede göreceğiniz Delegatör metrikleri şunları içermektedir: +Top Section: -- Toplam delegasyon ödülleri -- Toplam gerçekleşmemiş ödüller -- Toplam gerçekleşmiş ödüller +- View delegation and rewards-only charts +- Track key metrics: + - Toplam delegasyon ödülleri + - Unrealized rewards + - Realized Rewards -Sayfanın ikinci yarısında delegasyonlar tablosu yer alır. Burada delege ettiğiniz İndeksleyicileri ve ayrıntılarını (ödül kesintileri, bekleme süreleri vb.) görebilirsiniz. +Bottom Section: -Tablonun sağ tarafındaki düğmelerle delegasyonunuzu yönetebilirsiniz - daha fazla delege edebilir, delegasyonunuzu geri alabilir veya serbest kalma döneminden sonra delegasyonunuzu geri çekebilirsiniz. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Bu grafiğin yatay olarak kaydırılabilir olduğunu unutmayın, bu nedenle sağa doğru kaydırırsanız, delegasyonunuzun durumunu da görebilirsiniz (delege edilen, delegeden çıkarılan, geri çekilebilir). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Gezgin Görüntüsü 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Kürasyon Sekmesi +#### Kürasyon Sekmesi -Kürasyon sekmesinde, sinyal verdiğiniz (ve böylece sorgu ücretleri alabileceğiniz) tüm Subgraph'leri bulabilirsiniz. Sinyal vermek, Küratörlerin Endeksleyicilere hangi Subgraph'lerin değerli ve güvenilir olduğunu vurgulamasına olanak tanır, ve böylece bu Subgraph'lerin endekslenmesi gerektiğini belirtir. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Bu sekmede, aşağıdakilerin genel bir bakışını bulacaksınız: @@ -232,22 +260,22 @@ Bu sekmede, aşağıdakilerin genel bir bakışını bulacaksınız: - Her bir Subgraph için sorgu ödülleri - Güncelleme tarih detayları -![Gezgin Görüntüsü 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Profil Ayarlarınız +#### Profil Ayarlarınız Kullanıcı profilinizde, kişisel profil ayrıntılarınızı yönetebileceksiniz (bir ENS adı almak gibi). Eğer bir İndeksleyiciyseniz, daha fazla ayara erişiminiz olacaktır. Kullanıcı profilinizde, delegasyon parametrelerinizi ve operatörlerinizi ayarlayabileceksiniz. - Operatörler, İndeksleyici adına protokolde tahsislerin açılması ve kapatılması gibi sınırlı işlemlerde bulunur. Operatörler tipik olarak, stake cüzdanlarından ayrı, İndeksleyicilerin kişisel olarak ayarlayabileceği ağa kontrollü bir şekilde erişime sahip diğer Ethereum adresleridir - Delegasyon parametreleri, GRT'nin siz ve Delegatörleriniz arasındaki dağılımını kontrol etmenizi sağlar. -![Gezgin Görüntüsü 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) Graph Gezgini, merkeziyetsiz veri dünyasına açılan asıl portalınız olarak, ağdaki rolünüz ne olursa olsun birçok işlem yapmanıza olanak tanır. Profil ayarlarınıza, adresinizin yanındaki açılır menüyü açarak ve Ayarlar düğmesine tıklayarak erişebilirsiniz. ![Cüzdan detayları](/img/Wallet-Details.png) -## Ek Kaynaklar +### Ek Kaynaklar ### Video Kılavuzu From ceae5c83c96cd580ad618f1397b5e635e0f89e23 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:29 -0400 Subject: [PATCH 149/290] New translations explorer.mdx (Ukrainian) --- website/src/pages/uk/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/uk/subgraphs/explorer.mdx b/website/src/pages/uk/subgraphs/explorer.mdx index fd1259ea78b1..abb1e5db192b 100644 --- a/website/src/pages/uk/subgraphs/explorer.mdx +++ b/website/src/pages/uk/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Перегляд додаткових відомостей, таких як діаграми, поточний ID розгортання та інші ключові параметри -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Статистика підграфів (розподіл коштів, куратори тощо) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Індексатори +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Indexer Rewards - this is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - The number of GRT that was deposited - The number of shares a Curator owns -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - The distributing epochs are the epochs in which the state channels for the epochs are being settled and Indexers can claim their query fee rebates. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Your User Profile +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profile Overview +#### Profile Overview In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphs Tab +#### Subgraphs Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - the stake from Delegators that can be allocated by you but cannot be slashed -- Total Query Fees - the total fees that users have paid for queries served by you over time -- Indexer Rewards - the total amount of Indexer rewards you have received, in GRT -- Fee Cut - the % of query fee rebates that you will keep when you split with Delegators -- Rewards Cut - the % of Indexer rewards that you will keep when splitting with Delegators -- Owned - your deposited stake, which could be slashed for malicious or incorrect behavior +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -In the first half of the page, you can see your delegation chart, as well as the rewards-only chart. To the left, you can see the KPIs that reflect your current delegation metrics. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -The Delegator metrics you’ll see here in this tab include: +Top Section: -- Total delegation rewards -- Total unrealized rewards -- Total realized rewards +- View delegation and rewards-only charts +- Track key metrics: + - Total delegation rewards + - Unrealized rewards + - Realized Rewards -In the second half of the page, you have the delegations table. Here you can see the Indexers that you delegated towards, as well as their details (such as rewards cuts, cooldown, etc). +Bottom Section: -With the buttons on the right side of the table, you can manage your delegation - delegate more, undelegate, or withdraw your delegation after the thawing period. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Keep in mind that this chart is horizontally scrollable, so if you scroll all the way to the right, you can also see the status of your delegation (delegating, undelegating, withdrawable). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Within this tab, you’ll find an overview of: @@ -232,22 +260,22 @@ Within this tab, you’ll find an overview of: - Query rewards per Subgraph - Updated at date details -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Your Profile Settings +#### Your Profile Settings Within your user profile, you’ll be able to manage your personal profile details (like setting up an ENS name). If you’re an Indexer, you have even more access to settings at your fingertips. In your user profile, you’ll be able to set up your delegation parameters and operators. - Operators take limited actions in the protocol on the Indexer's behalf, such as opening and closing allocations. Operators are typically other Ethereum addresses, separate from their staking wallet, with gated access to the network that Indexers can personally set - Delegation parameters allow you to control the distribution of GRT between you and your Delegators. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Додаткові матеріали +### Додаткові матеріали ### Video Guide From 5fcf0d9f5b4f3b536e581fa6f8d75065b9dde2ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:30 -0400 Subject: [PATCH 150/290] New translations explorer.mdx (Chinese Simplified) --- website/src/pages/zh/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/zh/subgraphs/explorer.mdx b/website/src/pages/zh/subgraphs/explorer.mdx index e2e8147cd683..ce82f80a2b19 100644 --- a/website/src/pages/zh/subgraphs/explorer.mdx +++ b/website/src/pages/zh/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph 浏览器 --- -使用 [Graph Explorer](https://thegraph.com/explorer)解锁子图和网络数据。 +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## 概述 -Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) 互动，使用 [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one)，查看[网络信息](https://thegraph.com/explorer/network?chain=arbitrum-one)，并访问您的用户配置文件。 +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## 内置浏览器 +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -下面是Graph Explorer所有关键特征的细分。 您可以观看[Graph浏览器视频指南](/subgraphs/explorer/#video-guide)。 +## 先决条件 -### 子图页面 +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -部署并在Subgraph Studio发布您的子图后， 前往[Graph Explorer](https://thegraph.com/explorer)，然后点击导航栏中的“[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)”链接访问以下内容： +## Navigating Graph Explorer -- 您自己完成的子图 -- 其他人发布的子图 -- 您想要的精确子图 (基于创建的日期、信号数量或名称)。 +### Step 1. Explore Subgraphs -![Explorer 图像 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -当您点击子图时，将能够做以下工作： +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- 在面板测试查询，并能够通过网络细节来做出知情的决定。 -- 您还可以在自己的子图或其他人的子图中发出 GRT 信号，以使索引人意识到其重要性和质量。 +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - 这很关键，因为子图上的信号会激励它被索引，这意味着它将出现在网络上，最终为查询提供服务。 +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer 图像 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- 在面板测试查询，并能够通过网络细节来做出知情的决定。 +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) 在每个子图的专用页面，您可以做以下工作： -- 子图上的信号/非信号 -- 查看详细信息，例如图表、当前部署 ID 和其他元数据 -- 切换版本以探索子图的历史迭代 - 通过 GraphQL 查询子图 +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - 在面板上测试子图 - 查看在某个子图上建立索引的索引人 - 子图统计信息（分配、策展人等） -- 查看发布子图的实体 +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer 图像 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### 授权页面 +### Step 2. Delegate GRT -在 [委托](https://thegraph.com/explorer/delegate?chain=arbitrum-one)页面, 您可以找到关于委托、 获取GRT和选择索引人的信息。 +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -在这个页面上，您可以看到： +Here, you can: -- 收取最多查询费的索引人 -- 估值最大的 APR 索引人 +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -此外，您可以计算您的 ROI 并通过名称、地址或子图搜索顶级索引人。 +### Step 3. Monitor Participants in the Network -### 参与者页面 +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -这个页面提供了所有“参与者”的鸟视图，包括参与网络的每个人，如索引人、委托人和策展人。 +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. 索引人 +#### 索引人 -![Explorer 图像 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) 索引人是协议的骨干，是那些质押于子图、索引它们并向使用子图的任何人提供查询服务的人。 -在 索引人表中，您将能够看到 索引人的委托参数、他们的权益、他们对每个子图的权益以及他们从查询费用和索引奖励中获得的收入。 +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **详情** -- 查询费用划分 - 索引人与委托人划分查询费用的百分比。 -- 有效的奖励划分 - 应用于委托池的索引奖励削减。 如果是负数，则意味着索引人正在赠送部分奖励。 如果是正数，则意味着索引人保留了他们的一些奖励。 -- 冷却时间剩余 - 索引人可以更改上述委托参数之前的剩余时间。 冷却时间由索引人在更新委托参数时设置。 -- 已拥有 - 索引人的存入份额，可能会因恶意或不正确的行为被削减。 -- 已委托 - 委托人的份额可以由索引人分配，但不能被削减。 -- 已分配 - 索引人积极分配给他们正在索引的子图。 -- 可用委托容量 - 索引人在过度委托之前仍然可以收到的委托数量。 -- 最大委托容量 - 索引人可以有效接受的最大委托份额数量。 超出的委托权益不能用于分配或奖励计算。 -- 查询费用 - 这是最终用户一直以来为索引人的查询支付的费用。 -- 索引者奖励 - 这是索引人及其委托人在所有时间获得的总索引人奖励。 索引人奖励通过 GRT 发行支付。 +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. 索引人可以获得查询费用和索引奖励。 从功能上讲，当网络参与人将 GRT 委托给索引人时，就会发生这种情况。 这使索引人能够根据其索引参数接收查询费用和奖励。 @@ -86,9 +106,9 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// 要了解更多关于如何成为索引人的信息，您可以查看[官方文档](/indexing/overview/)或[The Graph学院索引人指南。](https://thegraph.academy/delegators/choosing-indexers/) -![索引详情面板](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. 策展人 +#### Curators 策展人分析子图以确定哪些子图质量最高。 一旦策展人发现一个潜在有吸引力的子图，他们就可以通过在其粘合曲线上发出信号来策展。 在这样做时，策展人让索引人知道哪些子图是高质量的且应该被索引。 @@ -102,11 +122,11 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// - 已存入的 GRT 数量 - 策展人拥有的股份数量 -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) 如果你想了解更多关于管理员角色的信息，你可以通过访问[正式文件](/resources/roles/curating/)或[The Graph学院](https://thegraph.academy/curators/)来做到这一点。 -#### 3. 委托人 +#### 委托人 委托人在维护The Graph网络的安全和去中心化方面发挥着关键作用。 他们通过向一个或多个索引人委托（如“质押”）GRT代币来参加网络。 @@ -114,7 +134,7 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// - 委托人反过来根据许多不同的变量选择索引人，例如过去的表现、索引奖励率和查询费用削减。 - 社区内部的信誉也可以在甄选过程中发挥一定作用。 建议通过[ The Graph的Discord](https://discord.gg/graphprotocol)或[ The Graph论坛](https://forum.thegraph.com/)与选中的索引人连接。 -![Explorer 图像 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) 在委托人表格上，你可以看到社区中的积极委托人和重要的衡量尺度： @@ -127,9 +147,9 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// 如果你想了解更多关于如何成为委托人的信息，你可以通过访问[正式文件](/resources/roles/delegating/delegating/)或[The Graph学院](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers)来做到这一点。 -### 网络页面 +### Step 4. Analyze Network Performance -在网络部分，您将看到全局 KPI 以及切换到每个时期的基础和更详细地分析网络指标的能力。 这些详细信息将让您了解网络随时间推移的表现。 +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### 概述 @@ -147,7 +167,7 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// - **查询费用代表消费者产生的费用**。索引人可以在至少7个时期（见下文）后声明（或不声明）它们，这些时期是在它们对子图的分配被关闭并且它们提供的数据已经被消费者验证之后。 - **索引奖励表示索引人在时期里从网络发布中获得的奖励金额。**虽然协议发布是固定的，但只有在索引人关闭其对已索引的子图的分配时，才会产生奖励。因此，每个时期的奖励数量各不相同（即在某些时期里，索引人可能会集体关闭已开放多日的分配）。 -![Explorer 图像 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### 时期 @@ -161,69 +181,77 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// - 分发时期是时期的状态通道正在结算的时期，索引人可以要求他们的查询费用回扣。 - 最终确定的时期是索引人没有留下查询费回扣的时期，因此被最终确定。 -![Explorer 图像 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## 您的用户资料 +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -无论您以何种方式参与网络，您的个人资料都是您查看网络活动的地方。 您的加密钱包将作为您的用户资料，通过用户面板，您将能够看到： +### Step 2. Explore the Tabs -### 个人资料概览 +#### 个人资料概览 在本节中，您可以查看以下内容： -- 您当前完成的任何操作。 -- 您的个人资料信息、描述和网站 (如果您添加了一个)。 +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer 图像 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### 子图标签 +#### 子图标签 -在子图选项卡中，您将看到您已发布的子图。 +The Subgraphs tab displays all your published Subgraphs. -> 这将不包括为测试目的使用 CLI 部署的任何子图——子图只会在它们发布到去中心化网络时显示。 +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer 图像 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### 索引标签 +#### 索引标签 -在索引选项卡中，您将找到一个包含所有活动和历史分配给子图的表格。 您还会找到图表，在那里可以看到和分析您过去作为索引人的表现。 +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -本节还将包括有关您的净索引人奖励和净查询费用的详细信息。 您将看到以下指标： +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- 已委托份额 - 委托人的份额，您可以分配但不能被削减 -- 总查询费用 - 用户在一段时间内为您提供的查询支付的总费用 -- 索引人奖励- 您收到的索引人奖励总额，以 GRT 为单位 -- 费用划分 - 当您与委托人拆分时，您将保留的查询费用回扣百分比 -- 奖励划分 - 与委托人拆分时您将保留的索引人奖励的百分比 -- 已拥有 - 您存入的股份，可能会因恶意或不正确的行为而被削减 +Track your Indexer performance with visual charts and key metrics, including: -![Explorer 图像 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### 委托标签 +![Indexer Stats](/img/Indexer-Stats.png) -委托人对Graph网络很重要。他们必须利用自己的知识选择一个能够提供健康回报的索引人。 +#### 委托标签 -在委托人选项卡中，可以找到您积极的和历史性委托的详情，连同您委托给索引人的指标。 +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -在页面的前半部分，您可以看到您的委托图表，以及仅奖励图表。 在左侧，您可以看到反映您当前委托指标的 KPI。 +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -您将在此选项卡中看到的委托人指标包括： +Top Section: -- 总委托奖励 -- 未实现的总奖励 -- 已实现的总奖励 +- View delegation and rewards-only charts +- Track key metrics: + - 总委托奖励 + - Unrealized rewards + - Realized Rewards -在页面的后半部分，您将看到委托标签。 在这里，您可以看到您委托给的索引人，以及它们的详细信息（例如奖励削减、冷却时间等）。 +Bottom Section: -通过表格右侧的按钮，你可以管理你的委托--更多的委托，取消委托，或在解冻期后撤回你的委托。 +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -请记住，此图表是可水平滚动的，因此如果您一直向右滚动，您还可以看到您的授权状态（委派、取消委派、可撤回）。 +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### 策展标签 +#### 策展标签 -在策展选项卡中，您将找到正在发送信号的所有子图（从而使您能够接收查询费用）。 信号允许策展人向索引人突出显示哪些子图有价值和值得信赖，从而表明它们需要被索引。 +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. 在此选项卡中，您将找到以下内容的概述： @@ -232,22 +260,22 @@ Graph Explorer由多个部分组成，您可以在其中与 [Subgraphs](https:// - 查询每个子图的奖励 - 更新日期详情 -![Explorer 图像 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### 设置您的个人资料 +#### 设置您的个人资料 在您的用户配置文件中，您将能够管理您的个人配置文件详细信息（例如设置 ENS 名称）。 如果您是 索引人，则可以轻松访问更多设置。 在您的用户配置文件中，您将能够设置您的委托参数和操作员。 - 操作员代表索引人在协议中采取有限的操作，例如打开和关闭分配。 操作员通常是其他以太坊地址，与他们的抵押钱包分开，可以访问索引人可以亲自设置的网络。 - 委托参数允许您控制 GRT 在您和您的委托人之间的分配。 -![Explorer 图像 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) 作为您进入去中心化数据世界的官方门户，无论您在网络中的角色如何，G​​raph 浏览器都允许您采取各种行动。 您可以通过打开地址旁边的下拉菜单进入您的个人资料设置，然后单击设置按钮。 ![钱包细节](/img/Wallet-Details.png) -## 其他资源 +### 其他资源 ### 视频教程 From f02dd50c0e86eed13c998905cb5c48228aaeb0cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:31 -0400 Subject: [PATCH 151/290] New translations explorer.mdx (Urdu (Pakistan)) --- website/src/pages/ur/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/ur/subgraphs/explorer.mdx b/website/src/pages/ur/subgraphs/explorer.mdx index 6074ff5c5b2f..fb843100e311 100644 --- a/website/src/pages/ur/subgraphs/explorer.mdx +++ b/website/src/pages/ur/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: گراف ایکسپلورر --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## جائزہ -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- مزید تفصیلات دیکھیں جیسے چارٹس، موجودہ تعیناتی ID، اور دیگر میٹا ڈیٹا -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - سب گراف کے اعدادوشمار (مختصات، کیوریٹرز، وغیرہ) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### انڈیکسرز +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- زیادہ سے زیاد ڈیلیلگیشن صلاحیت - ڈیلیلگیٹڈ حصص کی زیادہ سے زیادہ مقدار کو انڈیکسر نتیجہ خیز طور پر قبول کر سکتا ہے۔ ایک اضافی حصص کو مختص کرنے یا انعامات کے حساب کتاب کے لیے استعمال نہیں کیا جا سکتا. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- انڈیکسرز کے انعامات - یہ انڈیکسر اور ان کے ڈیلیگیٹرز کی طرف سے ہر وقت کمائے گئے کل انڈیکسر انعامات ہیں۔ انڈیکسر انعامات GRT کے اجراء کے ذریعے ادا کیے جاتے ہیں. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### کیوریٹرز +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - GRT کا نمبر جو جمع کیا گیا تھا - ایک کیوریٹر کے حصص کی تعداد -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### ڈیلیگیٹرز +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### جائزہ @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### ایپوکس @@ -161,69 +181,77 @@ A few key details to note: - تقسیم کرنے والے اپوچس وہ ایپوکس ہیں جن میں ایپوکس کے لیے ریاستی چینلز طے کیے جا رہے ہیں اور انڈیکسرز اپنی کیوری کی فیس میں چھوٹ کا دعویٰ کر سکتے ہیں. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## آپ کا صارف پروفائل +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### پروفائل کا جائزہ +#### پروفائل کا جائزہ In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### سب گرافس ٹیب +#### سب گرافس ٹیب -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### انڈیکسنگ ٹیب +#### انڈیکسنگ ٹیب -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -اس حصے میں آپ کے نیٹ انڈیکسر انعامات اور نیٹ استفسار کی فیس کے بارے میں تفصیلات بھی شامل ہوں گی۔ آپ کو درج ذیل میٹرکس نظر آئیں گے: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- ڈیلیگیٹڈ اسٹیک - ڈیلیگیٹرز کی طرف سے وہ داؤ جو آپ کے ذریعہ مختص کیا جاسکتا ہے لیکن اسے کم نہیں کیا جاسکتا -- کل کیوری کی فیس - وہ کل فیس جو صارفین نے وقت کے ساتھ آپ کے ذریعہ پیش کردہ کیوریز کے لیے ادا کی ہیں -- انڈیکسر انعامات - GRT میں آپ کو موصول ہونے والے انڈیکسر انعامات کی کل رقم -- فیس کٹ - کیوری کی فیس کی چھوٹ کا % جو آپ ڈیلیگیٹرز کے ساتھ الگ ہونے پر رکھیں گے -- ریوارڈز کٹ - انڈیکسر انعامات کا % جو آپ ڈیلیگیٹرز کے ساتھ تقسیم کرتے وقت رکھیں گے -- ملکیت - آپ کا جمع کردہ حصہ، جو بدنیتی پر مبنی یا غلط رویے کی وجہ سے کم کیا جا سکتا ہے +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### ڈیلگیٹنگ ٹیب +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### ڈیلگیٹنگ ٹیب -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -صفحہ کے پہلے نصف میں، آپ اپنے ڈیلیگیشن چارٹ کے ساتھ ساتھ صرف انعامات کا چارٹ دیکھ سکتے ہیں، بائیں طرف، آپ KPIs دیکھ سکتے ہیں جو آپ کی موجودہ ڈیلیگیشن میٹرکس کی عکاسی کرتے ہیں. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -ڈیلیگیٹر میٹرکس جو آپ یہاں اس ٹیب میں دیکھیں گے ان میں شامل ہیں: +Top Section: -- کل ڈیلیگیشن انعامات -- کل غیر حقیقی انعامات -- کل حقیقی انعامات +- View delegation and rewards-only charts +- Track key metrics: + - کل ڈیلیگیشن انعامات + - Unrealized rewards + - Realized Rewards -صفحہ کے دوسرے حصے میں، آپ کے پاس ڈیلیگیشنز ٹیبل ہے. یہاں آپ انڈیکسرز کو دیکھ سکتے ہیں جنہیں آپ نے ڈیلیگیٹ کیا ہے۔ نیز ان کی تفصیلات (جیسے انعامات میں کمی، کولڈاؤن وغیرہ). +Bottom Section: -ٹیبل کی دائیں جانب بٹنوں کے ساتھ، آپ اپنی ڈیلیگیشن کا انتظام کرسکتے ہیں - مزید ڈیلیگیٹ کریں، عن ڈیلیگیٹ، یہ پگھلنے کے خطرے کے بعد اپنی ڈیلیگیشن کو واپس لے لیں. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -ذہن میں رکھیں کہ یہ چارٹ افقی طور پر سکرول کرنے کے قابل ہے، لہذا اگر آپ پورے راستے سے دائیں طرف سکرول کرتے ہیں، تو آپ اپنی ڈیلیگیشن کی حیثیت بھی دیکھ سکتے ہیں ( ڈیلیگیٹنگ، غیر ڈیلیگیٹنگ، واپس لینے کے قابل). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### کیوریٹنگ ٹیب +#### کیوریٹنگ ٹیب -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. اس ٹیب کے اندر، آپ کو ایک جائزہ ملے گا: @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - تاریخ کی تفصیلات پر اپ ڈیٹ کیا گیا -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### آپ کے پروفائل کی ترتیبات +#### آپ کے پروفائل کی ترتیبات اپنے صارف پروفائل کے اندر، آپ اپنی ذاتی پروفائل کی تفصیلات کا نظم کر سکیں گے (جیسے ENS نام ترتیب دینا)۔ اگر آپ ایک انڈیکسر ہیں، تو آپ کو اپنی انگلیوں پر ترتیبات تک اور بھی زیادہ رسائی حاصل ہے۔ اپنے صارف پروفائل میں، آپ اپنے ڈیلیگیشن پیرامیٹرز اور آپریٹرز کو ترتیب دے سکیں گے. - آپریٹرز انڈیکسر کی جانب سے پروٹوکول میں محدود کاڑوائیاں کرتے ہیں، جیسے کہ مختص کھولنا اور بند کرنا. آپریٹرز عام طور پر دوسرے ایتھریم ایڈریس ہوتے ہیں، جو ان کے اسٹیکنگ والیٹ سے الگ ہوتے ہیں،نیٹ ورک تک رسائی کے ساتھ جسے انڈیکسرز ذاتی طور پر سیٹ کر سکتے ہیں - ڈیلیگیشن پیرامیٹرز آپ کو اپنے اور آپ کے ڈیلیگیٹرز کے درمیان GRT کی تقسیم کو کنٹرول کرنے کی اجازت دیتے ہیں. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## اضافی وسائل +### اضافی وسائل ### Video Guide From ba8793abb09e512458c9714a468ae7e8b4161c2d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:33 -0400 Subject: [PATCH 152/290] New translations explorer.mdx (Vietnamese) --- website/src/pages/vi/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/vi/subgraphs/explorer.mdx b/website/src/pages/vi/subgraphs/explorer.mdx index 2a5747208705..affb003c22ce 100644 --- a/website/src/pages/vi/subgraphs/explorer.mdx +++ b/website/src/pages/vi/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Trình khám phá Graph --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Tổng quan -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- Xem thêm chi tiết như biểu đồ, ID triển khai hiện tại và siêu dữ liệu khác -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Thống kê Subgraph (phân bổ, Curators, v.v.) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- Max Delegation Capacity - the maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- Thưởng Indexer - đây là tổng phần thưởng indexer mà Indexer và các Delegator của họ kiếm được cho đến hiện tại. Phần thưởng Indexer được trả thông qua việc phát hành GRT. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - Số GRT đã được nạp - Số cổ phần một Curator sở hữu -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Tổng quan @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - Epoch đang phân phối là epoch trong đó các kênh trạng thái cho các epoch đang được giải quyết và Indexer có thể yêu cầu hoàn phí truy vấn của họ. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Hồ sơ Người dùng của bạn +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Tổng quan Hồ sơ +#### Tổng quan Hồ sơ In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Tab Subgraphs +#### Tab Subgraphs -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Tab Indexing +#### Tab Indexing -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -Phần này cũng sẽ bao gồm thông tin chi tiết về phần thưởng Indexer ròng của bạn và phí truy vấn ròng. Bạn sẽ thấy các số liệu sau: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Stake được ủy quyền - phần stake từ Delegator có thể được bạn phân bổ nhưng không thể bị phạt cắt giảm (slashed) -- Total Query Fees - the total fees that users have paid for queries served by you over time -- Phần thưởng Indexer - tổng số phần thưởng Indexer bạn đã nhận được, tính bằng GRT -- Phần Cắt Phí - lượng % hoàn phí phí truy vấn mà bạn sẽ giữ lại khi ăn chia với Delegator -- Phần Cắt Thưởng - lượng % phần thưởng Indexer mà bạn sẽ giữ lại khi ăn chia với Delegator -- Được sở hữu - số stake đã nạp của bạn, có thể bị phạt cắt giảm (slashed) vì hành vi độc hại hoặc không chính xác +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Tab Delegating +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Tab Delegating -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -Trong nửa đầu của trang, bạn có thể thấy biểu đồ ủy quyền của mình, cũng như biểu đồ chỉ có phần thưởng. Ở bên trái, bạn có thể thấy các KPI phản ánh các chỉ số ủy quyền hiện tại của bạn. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -Các chỉ số Delegator mà bạn sẽ thấy ở đây trong tab này bao gồm: +Top Section: -- Total delegation rewards -- Tổng số phần thưởng chưa ghi nhận -- Tổng số phần thưởng đã ghi được +- View delegation and rewards-only charts +- Track key metrics: + - Total delegation rewards + - Unrealized rewards + - Realized Rewards -Trong nửa sau của trang, bạn có bảng ủy quyền. Tại đây, bạn có thể thấy các Indexer mà bạn đã ủy quyền, cũng như thông tin chi tiết của chúng (chẳng hạn như phần cắt thưởng, thời gian chờ, v.v.). +Bottom Section: -Với các nút ở bên phải của bảng, bạn có thể quản lý ủy quyền của mình - ủy quyền nhiều hơn, hủy bỏ hoặc rút lại ủy quyền của bạn sau khoảng thời gian rã đông (thawing period). +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -Lưu ý rằng biểu đồ này có thể cuộn theo chiều ngang, vì vậy nếu bạn cuộn hết cỡ sang bên phải, bạn cũng có thể thấy trạng thái ủy quyền của mình (ủy quyền, hủy ủy quyền, có thể rút lại). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Tab Curating +#### Tab Curating -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. Trong tab này, bạn sẽ tìm thấy tổng quan về: @@ -232,22 +260,22 @@ Trong tab này, bạn sẽ tìm thấy tổng quan về: - Query rewards per Subgraph - Chi tiết ngày được cập nhật -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Cài đặt Hồ sơ của bạn +#### Cài đặt Hồ sơ của bạn Trong hồ sơ người dùng của mình, bạn sẽ có thể quản lý chi tiết hồ sơ cá nhân của mình (như thiết lập tên ENS). Nếu bạn là Indexer, bạn thậm chí có nhiều quyền truy cập hơn vào các cài đặt trong tầm tay của mình. Trong hồ sơ người dùng của mình, bạn sẽ có thể thiết lập các tham số ủy quyền và operator của mình. - Operators (Người vận hành) thực hiện các hành động được hạn chế trong giao thức thay mặt cho Indexer, chẳng hạn như mở và đóng phân bổ. Operators thường là các địa chỉ Ethereum khác, tách biệt với ví đặt staking của họ, với quyền truy cập được kiểm soát vào mạng mà Indexer có thể cài đặt cá nhân - Tham số ủy quyền cho phép bạn kiểm soát việc phân phối GRT giữa bạn và các Delegator của bạn. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### Video Guide From e5814bb7bcce35e719f1899140527d3825aee7cd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:34 -0400 Subject: [PATCH 153/290] New translations explorer.mdx (Marathi) --- website/src/pages/mr/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/mr/subgraphs/explorer.mdx b/website/src/pages/mr/subgraphs/explorer.mdx index afcc80c29f35..d236e46a096b 100644 --- a/website/src/pages/mr/subgraphs/explorer.mdx +++ b/website/src/pages/mr/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## सविश्लेषण -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## Prerequisites -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- Subgraphs published by others -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- Test queries in the playground and be able to leverage network details to make informed decisions. -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- Test queries in the playground and be able to leverage network details to make informed decisions. +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- चार्ट, वर्तमान उपयोजन आयडी आणि इतर मेटाडेटा यासारखे अधिक तपशील पहा -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - Subgraph stats (allocations, Curators, etc) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. Indexers +#### Indexers -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **Specifics** -- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators. -- Effective Reward Cut - the indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. -- Cooldown Remaining - the time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. -- Owned - This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. -- Delegated - Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated. -- कमाल डेलिगेशन क्षमता - इंडेक्सर उत्पादकपणे स्वीकारू शकणारी जास्तीत जास्त डेलिगेटेड स्टेक. वाटप किंवा बक्षिसे गणनेसाठी जास्तीचा वाटप केला जाऊ शकत नाही. -- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time. -- इंडेक्सर रिवॉर्ड्स - हे इंडेक्सर आणि त्यांच्या प्रतिनिधींनी सर्वकाळात मिळवलेले एकूण इंडेक्सर रिवॉर्ड्स आहेत. इंडेक्सर रिवॉर्ड्स GRT जारी करून दिले जातात. +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers can earn both query fees and indexing rewards. Functionally, this happens when network participants delegate GRT to an Indexer. This enables Indexers to receive query fees and rewards depending on their Indexer parameters. @@ -86,9 +106,9 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. Curators +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ In the The Curator table listed below you can see: - The number of GRT that was deposited - The number of shares a Curator owns -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. Delegators +#### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -114,7 +134,7 @@ Delegators play a key role in maintaining the security and decentralization of T - Delegators select Indexers based on a number of different variables, such as past performance, indexing reward rates, and query fee cuts. - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) In the Delegators table you can see the active Delegators in the community and important metrics: @@ -127,9 +147,9 @@ In the Delegators table you can see the active Delegators in the community and i If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### सविश्लेषण @@ -147,7 +167,7 @@ A few key details to note: - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### Epochs @@ -161,69 +181,77 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as: - वितरण युग हे असे युग आहेत ज्यामध्ये युगांसाठी राज्य चॅनेल सेटल केले जात आहेत आणि इंडेक्सर्स त्यांच्या क्वेरी फी सवलतीचा दावा करू शकतात. - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers. -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## Your User Profile +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -Your personal profile is the place where you can see your network activity, regardless of your role on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see the following tabs: +### Step 2. Explore the Tabs -### Profile Overview +#### Profile Overview In this section, you can view the following: -- Any of your current actions you've done. -- Your profile information, description, and website (if you added one). +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### Subgraphs Tab +#### Subgraphs Tab -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### Indexing Tab +#### Indexing Tab -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -या विभागात तुमच्या निव्वळ इंडेक्सर रिवॉर्ड्स आणि नेट क्वेरी फीबद्दल तपशील देखील समाविष्ट असतील. तुम्हाला खालील मेट्रिक्स दिसतील: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- Delegated Stake - the stake from Delegators that can be allocated by you but cannot be slashed -- एकूण क्वेरी शुल्क - वापरकर्त्यांनी वेळोवेळी तुमच्याद्वारे दिलेल्या क्वेरींसाठी भरलेले एकूण शुल्क -- Indexer Rewards - the total amount of Indexer rewards you have received, in GRT -- फी कट - तुम्ही डेलिगेटर्ससह विभक्त झाल्यावर तुम्ही ठेवू शकणार्‍या क्वेरी फी सवलतींचा % -- Rewards Cut - the % of Indexer rewards that you will keep when splitting with Delegators -- मालकीचा - तुमचा जमा केलेला हिस्सा, जो दुर्भावनापूर्ण किंवा चुकीच्या वर्तनासाठी कमी केला जाऊ शकतो +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### Delegating Tab +![Indexer Stats](/img/Indexer-Stats.png) -Delegators are important to the Graph Network. They must use their knowledge to choose an Indexer that will provide a healthy return on rewards. +#### Delegating Tab -In the Delegators tab, you can find the details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards. +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -पृष्‍ठाच्या पूर्वार्धात, तुम्‍ही तुमच्‍या डेलिगेशन चार्ट तसेच रिवॉर्ड-ओन्ली चार्ट पाहू शकता. डावीकडे, तुम्ही KPI पाहू शकता जे तुमचे वर्तमान प्रतिनिधीत्व मेट्रिक्स दर्शवतात. +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -या टॅबमध्ये तुम्हाला येथे दिसणार्‍या डेलिगेटर मेट्रिक्समध्ये हे समाविष्ट आहे: +Top Section: -- एकूण प्रतिनिधीत्व बक्षिसे -- Total unrealized rewards -- Total realized rewards +- View delegation and rewards-only charts +- Track key metrics: + - एकूण प्रतिनिधीत्व बक्षिसे + - Unrealized rewards + - Realized Rewards -पृष्ठाच्या दुसऱ्या सहामाहीत, आपल्याकडे प्रतिनिधी टेबल आहे. येथे तुम्ही ज्या निर्देशांकांना तुम्ही नियुक्त केले आहे, तसेच त्यांचे तपशील (जसे की रिवॉर्ड कट, कूलडाउन इ.) पाहू शकता. +Bottom Section: -टेबलच्या उजव्या बाजूला असलेल्या बटणांच्या सहाय्याने, तुम्ही तुमचे प्रतिनिधीमंडळ व्यवस्थापित करू शकता - वितळण्याच्या कालावधीनंतर तुमचे प्रतिनिधीमंडळ अधिक प्रतिनिधी, अस्वीकृत किंवा मागे घेऊ शकता. +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -लक्षात ठेवा की हा चार्ट क्षैतिजरित्या स्क्रोल करण्यायोग्य आहे, म्हणून तुम्ही उजवीकडे स्क्रोल केल्यास, तुम्ही तुमच्या प्रतिनिधीची स्थिती देखील पाहू शकता (प्रतिनिधी, अस्वीकृत, मागे घेण्यायोग्य). +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### Curating Tab +#### Curating Tab -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. या टॅबमध्ये, तुम्हाला याचे विहंगावलोकन मिळेल: @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - Updated at date details -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### Your Profile Settings +#### Your Profile Settings तुमच्या वापरकर्ता प्रोफाइलमध्ये, तुम्ही तुमचे वैयक्तिक प्रोफाइल तपशील व्यवस्थापित करण्यास सक्षम असाल (जसे की ENS नाव सेट करणे). तुम्ही इंडेक्सर असल्यास, तुमच्या बोटांच्या टोकावर असलेल्या सेटिंग्जमध्ये तुम्हाला आणखी प्रवेश आहे. तुमच्या वापरकर्ता प्रोफाइलमध्ये, तुम्ही तुमचे डेलिगेशन पॅरामीटर्स आणि ऑपरेटर सेट करू शकाल. - ऑपरेटर इंडेक्सरच्या वतीने प्रोटोकॉलमध्ये मर्यादित कृती करतात, जसे की वाटप उघडणे आणि बंद करणे. ऑपरेटर हे सामान्यत: इतर इथरियम पत्ते असतात, जे त्यांच्या स्टॅकिंग वॉलेटपासून वेगळे असतात, इंडेक्सर्स वैयक्तिकरित्या सेट करू शकणार्‍या नेटवर्कवर गेट केलेला प्रवेश असतो - Delegation parameters allow you to control the distribution of GRT between you and your Delegators. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## अतिरिक्त संसाधने +### अतिरिक्त संसाधने ### Video Guide From cdcf607b4d47c3237c2ea1678342a29c3037e8d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Thu, 10 Apr 2025 18:24:35 -0400 Subject: [PATCH 154/290] New translations explorer.mdx (Hindi) --- website/src/pages/hi/subgraphs/explorer.mdx | 204 +++++++++++--------- 1 file changed, 116 insertions(+), 88 deletions(-) diff --git a/website/src/pages/hi/subgraphs/explorer.mdx b/website/src/pages/hi/subgraphs/explorer.mdx index 64a671781463..dd17553bf415 100644 --- a/website/src/pages/hi/subgraphs/explorer.mdx +++ b/website/src/pages/hi/subgraphs/explorer.mdx @@ -2,83 +2,103 @@ title: Graph Explorer --- -Unlock the world of Subgraphs and network data with [Graph Explorer](https://thegraph.com/explorer). +Use [Graph Explorer](https://thegraph.com/explorer) and take full advantage of its core features. ## Overview -Graph Explorer consists of multiple parts where you can interact with [Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one), [delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one), engage [participants](https://thegraph.com/explorer/participants?chain=arbitrum-one), view [network information](https://thegraph.com/explorer/network?chain=arbitrum-one), and access your user profile. +This guide explains how to use [Graph Explorer](https://thegraph.com/explorer) to quickly discover and interact with Subgraphs on The Graph Network, delegate GRT, view participant metrics, and analyze network performance. -## Inside Explorer +> When you visit Graph Explorer, you can also access the link to [explore Substreams](https://substreams.dev/). -The following is a breakdown of all the key features of Graph Explorer. For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). +## आवश्यक शर्तें -### Subgraphs Page +- To perform actions, you need a wallet (e.g., MetaMask) connected to [Graph Explorer](https://thegraph.com/explorer). + > Make sure your wallet is connected to the correct network (e.g., Arbitrum). Features and data shown are network specific. +- GRT tokens if you plan to delegate or curate. +- Basic knowledge of [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/) -After deploying and publishing your Subgraph in Subgraph Studio, go to [Graph Explorer](https://thegraph.com/explorer) and click on the "[Subgraphs](https://thegraph.com/explorer?chain=arbitrum-one)" link in the navigation bar to access the following: +## Navigating Graph Explorer -- Your own finished Subgraphs -- दूसरों द्वारा प्रकाशित subgraphs -- The exact Subgraph you want (based on the date created, signal amount, or name). +### Step 1. Explore Subgraphs -![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png) +> For additional support, you can watch the [Graph Explorer video guide](/subgraphs/explorer/#video-guide). -When you click into a Subgraph, you will be able to do the following: +Go to the Subgraphs page in [Graph Explorer](https://thegraph.com/explorer). -- प्लेग्राउंड में परीक्षण प्रश्न करें और सूचनापूर्ण निर्णय लेने के लिए नेटवर्क विवरण का उपयोग करें। -- Signal GRT on your own Subgraph or the Subgraphs of others to make indexers aware of its importance and quality. +- If you've deployed and published your Subgraph in Subgraph Studio, you can view it here. +- Search all published Subgraphs and filter them by indexed network, specific categories (such as DeFI, NFTs, and DAOs), and **most queried, most curated, recently created, and recently updated**. + +![Graph Explorer Subgraphs page](/img/explorer-subgraphs-page.png) + +To find Subgraphs indexing a specific contract, enter the contract address into the search bar. + +- For example, you can enter the L2GNS contract on Artbitrum (`0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec`) and this returns all Subgraphs indexing that contract: + +![Search by Indexing Contract](/img/explorer-search.png) - - This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it’ll eventually surface on the network to serve queries. +> Looking for indexing contracts? Check out [this Subgraph](https://thegraph.com/explorer/subgraphs/FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR?view=About&chain=arbitrum-one) which indexes contract addresses listed in its manifest. It shows all current deployments indexing those contracts on Arbitrum One, along with the signal allocated to each. -![Explorer Image 2](/img/Subgraph-Details.png) +You can click into any Subgraph, to: + +- प्लेग्राउंड में परीक्षण प्रश्न करें और सूचनापूर्ण निर्णय लेने के लिए नेटवर्क विवरण का उपयोग करें। +- Signal GRT on your own Subgraph or the Subgraphs of others to make Indexers aware of its importance and quality. + > This is critical because signaling on a Subgraph incentivizes it to be indexed, meaning it'll eventually surface on the network to serve queries. + +![Subgraph Details](/img/explorer-subgraph-details.png) On each Subgraph’s dedicated page, you can do the following: -- Signal/Un-signal on Subgraphs -- चार्ट, वर्तमान परिनियोजन आईडी और अन्य मेटाडेटा जैसे अधिक विवरण देखें -- Switch versions to explore past iterations of the Subgraph - Query Subgraphs via GraphQL +- View Subgraph ID, current deployment ID, Query URL, and other metadata +- Signal/unsignal on Subgraphs - Test Subgraphs in the playground - View the Indexers that are indexing on a certain Subgraph - सबग्राफ आँकड़े (आवंटन, क्यूरेटर, आदि) -- View the entity who published the Subgraph +- View query fees and charts +- Change versions to explore past iterations of the Subgraph +- View entity types +- View Subgraph activity -![Explorer Image 3](/img/Explorer-Signal-Unsignal.png) +![Signal/unsignal on Subgraph](/img/explorer-signal.png) -### Delegate Page +### Step 2. Delegate GRT -On the [Delegate page](https://thegraph.com/explorer/delegate?chain=arbitrum-one), you can find information about delegating, acquiring GRT, and choosing an Indexer. +Go to the [Delegate](https://thegraph.com/explorer/delegate?chain=arbitrum-one) page to learn how to delegate, get GRT, and choose an Indexer. -On this page, you can see the following: +Here, you can: -- Indexers who collected the most query fees -- Indexers with the highest estimated APR +- Compare Indexers by most query fees earned and highest estimated APR. +- Use the built-in ROI calculator or search by Indexer name or address. +- Click **"Delegate"** next to an Indexer to stake your GRT. -Additionally, you can calculate your ROI and search for top Indexers by name, address, or Subgraph. +### Step 3. Monitor Participants in the Network -### Participants Page +Go to the [Participants](https://thegraph.com/explorer/participants?chain=arbitrum-one) page to view: -This page provides a bird's-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators. +- Indexers: stakes, allocations, rewards, and delegation parameters +- Curators: signal amounts, Subgraph shares, and activity history +- Delegators: current and historical delegations, rewards, and Indexer metrics -#### 1. इंडेक्सर्स +#### Indexer -![Explorer Image 4](/img/Indexer-Pane.png) +![Indexers Table](/img/explorer-indexers.png) Indexers are the backbone of the protocol. They stake on Subgraphs, index them, and serve queries to anyone consuming Subgraphs. -In the Indexers table, you can see an Indexers’ delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. +In the Indexers table, you can see an Indexer's delegation parameters, their stake, how much they have staked to each Subgraph, and how much revenue they have made from query fees and indexing rewards. **विशिष्टताएँ** -- क्वेरी फ़ी कट - वह % जो क्वेरी फ़ी रिबेट्स का हिस्सा है जो Indexer, Delegators के साथ बाँटते समय रखता है। -- प्रभावी पुरस्कार कट - वह इंडेक्सिंग पुरस्कार कट जो डेलीगेशन पूल पर लागू होता है। यदि यह नकारात्मक है, तो इसका मतलब है कि इंडेक्सर अपने पुरस्कारों का एक हिस्सा दे रहा है। यदि यह सकारात्मक है, तो इसका मतलब है कि Indexer अपने कुछ पुरस्कार रख रहा है। -- कूलडाउन शेष - वह समय जो उपरोक्त डेलीगेशन पैरामीटर को बदलने के लिए Indexer को बचा है। कूलडाउन अवधि वे होती हैं जो Indexers अपने डेलीगेशन पैरामीटर को अपडेट करते समय सेट करते हैं। -- यह है Indexer का जमा किया गया हिस्सेदारी, जिसे दुष्ट या गलत व्यवहार के लिए काटा जा सकता है। -- प्रतिनिधि - 'Delegators' से स्टेक जो 'Indexers' द्वारा आवंटित किया जा सकता है, लेकिन इसे स्लैश नहीं किया जा सकता। -- Allocated - Stake that Indexers are actively allocating towards the Subgraphs they are indexing. -- अवेलबल डेलीगेशन कैपेसिटी - वह मात्रा जो डेलीगेटेड स्टेक है, जो Indexers अभी भी प्राप्त कर सकते हैं इससे पहले कि वे ओवर-डेलीगेटेड हो जाएं। -- अधिकतम प्रत्यायोजन क्षमता - प्रत्यायोजित हिस्सेदारी की अधिकतम राशि जिसे इंडेक्सर उत्पादक रूप से स्वीकार कर सकता है। आवंटन या पुरस्कार गणना के लिए एक अतिरिक्त प्रत्यायोजित हिस्सेदारी का उपयोग नहीं किया जा सकता है। -- क्वेरी शुल्क - यह कुल शुल्क है जो अंतिम उपयोगकर्ताओं ने सभी समय में एक Indexer से क्वेरी के लिए भुगतान किया है। -- इंडेक्सर रिवार्ड्स - यह इंडेक्सर और उनके प्रतिनिधियों द्वारा हर समय अर्जित किए गए कुल इंडेक्सर पुरस्कार हैं। इंडेक्सर पुरस्कार का भुगतान जीआरटी जारी करने के माध्यम से किया जाता है। +- Query Fee Cut: The % of the query fee rebates that the Indexer keeps when splitting with Delegators. +- Effective Reward Cut: The indexing reward cut applied to the delegation pool. If it’s negative, it means that the Indexer is giving away part of their rewards. If it’s positive, it means that the Indexer is keeping some of their rewards. +- Cooldown Remaining: The time remaining until the Indexer can change the above delegation parameters. Cooldown periods are set up by Indexers when they update their delegation parameters. +- Owned: This is the Indexer’s deposited stake, which may be slashed for malicious or incorrect behavior. +- Delegated: Stake from Delegators which can be allocated by the Indexer, but cannot be slashed. +- Allocated: Stake that Indexers are actively allocating towards the Subgraphs they are indexing. +- Available Delegation Capacity: The amount of delegated stake the Indexers can still receive before they become over-delegated. +- Max Delegation Capacity: The maximum amount of delegated stake the Indexer can productively accept. An excess delegated stake cannot be used for allocations or rewards calculations. +- Query Fees: This is the total fees that end users have paid for queries from an Indexer over all time. +- Indexer Rewards: This is the total indexer rewards earned by the Indexer and their Delegators over all time. Indexer rewards are paid through GRT issuance. Indexers दोनों क्वेरी फीस और इंडेक्सिंग पुरस्कार कमा सकते हैं। कार्यात्मक रूप से, यह तब होता है जब नेटवर्क प्रतिभागी GRT को एक Indexer को सौंपते हैं। इससे Indexers को उनके Indexer पैरामीटर के आधार पर क्वेरी फीस और पुरस्कार प्राप्त होते हैं। @@ -86,9 +106,9 @@ Indexers दोनों क्वेरी फीस और इंडेक् To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) -![Indexing details pane](/img/Indexing-Details-Pane.png) +![Indexing Details Pane](/img/Indexing-Details-Pane.png) -#### 2. क्यूरेटर +#### Curators Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. @@ -102,11 +122,11 @@ Curators analyze Subgraphs to identify which Subgraphs are of the highest qualit - जमा किए गए जीआरटी की संख्या - एक क्यूरेटर के शेयरों की संख्या -![Explorer Image 6](/img/Curation-Overview.png) +![Curators Table](/img/explorer-curators.png) If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). -#### 3. प्रतिनिधि +#### Delegator The Graph Network की सुरक्षा और विकेंद्रीकरण को बनाए रखने में Delegators की महत्वपूर्ण भूमिका होती है। वे नेटवर्क में भाग लेते हैं 'delegating' (यानी, 'staking') करके और GRT tokens को एक या एक से अधिक Indexers को सौंपते हैं। @@ -114,7 +134,7 @@ The Graph Network की सुरक्षा और विकेंद्र - डेलीगेटर्स विभिन्न कारकों के आधार पर इंडेक्सर्स का चयन करते हैं, जैसे कि पिछले प्रदर्शन, इंडेक्सिंग इनाम दरें, और क्वेरी शुल्क कट। - Reputation within the community can also play a factor in the selection process. It's recommended to connect with the selected Indexers via [The Graph's Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/). -![Explorer Image 7](/img/Delegation-Overview.png) +![Delegators Table](/img/explorer-delegators.png) Delegators तालिका में आप समुदाय में सक्रिय Delegators और महत्वपूर्ण मैट्रिक्स देख सकते हैं: @@ -127,9 +147,9 @@ Delegators तालिका में आप समुदाय में स If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). -### Network Page +### Step 4. Analyze Network Performance -On this page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. +On the [Network](https://thegraph.com/explorer/network?chain=arbitrum-one) page, you can see global KPIs and have the ability to switch to a per-epoch basis and analyze network metrics in more detail. These details will give you a sense of how the network is performing over time. #### Overview @@ -147,7 +167,7 @@ On this page, you can see global KPIs and have the ability to switch to a per-ep - **Query fees represent the fees generated by the consumers**. They can be claimed (or not) by the Indexers after a period of at least 7 epochs (see below) after their allocations towards the Subgraphs have been closed and the data they served has been validated by the consumers. - **Indexing rewards represent the amount of rewards the Indexers claimed from the network issuance during the epoch.** Although the protocol issuance is fixed, the rewards only get minted once Indexers close their allocations towards the Subgraphs they’ve been indexing. So, the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days). -![Explorer Image 8](/img/Network-Stats.png) +![Network Overview](/img/explorer-network.png) #### अवधियों को @@ -161,69 +181,77 @@ On this page, you can see global KPIs and have the ability to switch to a per-ep - वितरण युग ऐसे युग हैं जिनमें युगों के लिए राज्य चैनल तय किए जा रहे हैं और अनुक्रमणकर्ता अपनी क्वेरी शुल्क छूट का दावा कर सकते हैं। - अंतिम चरण वे चरण हैं जिनमें Indexers द्वारा दावा करने के लिए कोई प्रश्न शुल्क छूट शेष नहीं है। -![Explorer Image 9](/img/Epoch-Stats.png) +![Epochs](/img/explorer-epochs.png) + +## Access and Manage Your User Profile + +### Step 1. Access Your Profile -## आपका उपयोगकर्ता प्रोफ़ाइल +- Click your wallet address in the top right corner +- Your wallet acts as your user profile +- In your profile dashboard, you can view and interact with several useful tabs -आपकी व्यक्तिगत प्रोफ़ाइल वह स्थान है जहां आप अपने नेटवर्क गतिविधि को देख सकते हैं, चाहे आपकी भूमिका नेटवर्क पर कुछ भी हो। आपका क्रिप्टो वॉलेट आपके उपयोगकर्ता प्रोफ़ाइल के रूप में कार्य करेगा, और उपयोगकर्ता डैशबोर्ड के साथ, आप निम्नलिखित टैब देख सकेंगे: +### Step 2. Explore the Tabs -### प्रोफ़ाइल अवलोकन +#### प्रोफ़ाइल अवलोकन इस खंड में, आप निम्नलिखित देख सकते हैं: -- आपकी वर्तमान क्रियाओं में से कोई भी आपने किया है। -- आपकी प्रोफ़ाइल जानकारी, विवरण, और वेबसाइट (यदि आपने एक जोड़ी है)। +- Your activity +- Your profile information: total query fees, total shares value, owned stake, stake delegating -![Explorer Image 10](/img/Profile-Overview.png) +![Profile Overview](/img/Profile-Overview.png) -### सबग्राफ टैब +#### सबग्राफ टैब -In the Subgraphs tab, you’ll see your published Subgraphs. +The Subgraphs tab displays all your published Subgraphs. -> This will not include any Subgraphs deployed with the CLI for testing purposes. Subgraphs will only show up when they are published to the decentralized network. +> Subgraphs deployed with the CLI for testing purposes will not show up here. Subgraphs will only show up when they are published to the decentralized network. -![Explorer Image 11](/img/Subgraphs-Overview.png) +![Subgraphs Overview](/img/Subgraphs-Overview.png) -### अनुक्रमण टैब +#### अनुक्रमण टैब -In the Indexing tab, you’ll find a table with all the active and historical allocations towards Subgraphs. You will also find charts where you can see and analyze your past performance as an Indexer. +> If you haven't indexed, you will see links to stake to index Subgraphs and browse Subgraphs on Graph Explorer. -इस खंड में आपके नेट इंडेक्सर रिवार्ड्स और नेट क्वेरी फीस के विवरण भी शामिल होंगे। आपको ये मेट्रिक दिखाई देंगे: +The Indexing tab displays a table where you can review active and historical allocations to Subgraphs. -- प्रत्यायोजित हिस्सेदारी - प्रतिनिधियों की हिस्सेदारी जो आपके द्वारा आवंटित की जा सकती है लेकिन कम नहीं की जा सकती -- कुल प्रश्न शुल्क - कुल शुल्क जो उपयोगकर्ताओं ने समय के साथ आपके द्वारा की गई प्रश्नों के लिए भुगतान किया है -- इंडेक्सर रिवार्ड्स - जीआरटी में आपको प्राप्त इंडेक्सर रिवार्ड्स की कुल राशि -- शुल्क में कटौती - क्वेरी शुल्क का % छूट जो आप डेलीगेटर्स के साथ अलग होने पर रखेंगे -- रिवार्ड्स कट - इंडेक्सर रिवार्ड्स का वह % जिसे आप डेलीगेटर्स के साथ विभाजित करते समय रखेंगे -- स्वामित्व - यह इंडेक्सर की जमा हिस्सेदारी है, जिसे दुर्भावनापूर्ण या गलत व्यवहार के लिए घटाया जा सकता है +Track your Indexer performance with visual charts and key metrics, including: -![Explorer Image 12](/img/Indexer-Stats.png) +- Delegated Stake: Stake from Delegators that can be allocated by you but cannot be slashed. +- Total Query Fees: Cumulative fees from served queries. +- Indexer Rewards (in GRT): Total rewards earned. +- Fee Cut & Rewards Cut: The % of query fee rebates and Indexer rewards you'll keep when you split with Delegators. +- Owned Stake: Your deposited stake, which could be slashed for malicious or incorrect behavior. -### प्रतिनिधि टैब +![Indexer Stats](/img/Indexer-Stats.png) -Delegator ,The Graph नेटवर्क के लिए महत्वपूर्ण हैं। उन्हें अपने ज्ञान का उपयोग करके एक इंडेक्सर का चयन करना चाहिए जो पुरस्कारों पर स्वस्थ रिटर्न प्रदान करेगा। +#### प्रतिनिधि टैब -डेलीगेटर्स टैब में, आप अपनी सक्रिय और ऐतिहासिक डेलीगेशंस का विवरण पा सकते हैं, साथ ही उन Indexers के मेट्रिक्स भी जिनकी ओर आपने डेलीगेट किया है। +> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). -पृष्ठ के पहले भाग में, आप अपना प्रतिनिधिमंडल चार्ट और साथ ही केवल-पुरस्कार चार्ट देख सकते हैं। बाईं ओर, आप वे KPI देख सकते हैं जो आपके वर्तमान डेलिगेशन मेट्रिक्स को दर्शाते हैं। +The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. -इस टैब में आप यहां जो डेलिगेटर मेट्रिक्स देखेंगे उनमें शामिल हैं: +Top Section: -- कुल प्रतिनिधिमंडल पुरस्कार -- कुल अचेतन पुरस्कार -- कुल एहसास पुरस्कार +- View delegation and rewards-only charts +- Track key metrics: + - कुल प्रतिनिधिमंडल पुरस्कार + - Unrealized rewards + - Realized Rewards -पृष्ठ के दूसरे भाग में, आपके पास प्रतिनिधि तालिका है। यहां आप उन इंडेक्स को देख सकते हैं जिन्हें आपने प्रत्यायोजित किया है, साथ ही उनके विवरण (जैसे रिवॉर्ड कट, कूलडाउन, आदि)। +Bottom Section: -तालिका के दाईं ओर स्थित बटनों के साथ, आप अपने प्रतिनिधिमंडल का प्रबंधन कर सकते हैं - अधिक प्रतिनिधि, अप्रतिबंधित, या पिघलने की अवधि के बाद अपने प्रतिनिधिमंडल को वापस ले सकते हैं। +- Explore a table of your Indexer delegations, including reward cuts, cooldowns, and more. +- Use the buttons on the right side of the table to manage your delegation - delegate more, undelegate, or withdraw it after the thawing period. -ध्यान रखें कि यह चार्ट क्षैतिज रूप से स्क्रॉल करने योग्य है, इसलिए यदि आप दाईं ओर स्क्रॉल करते हैं, तो आप अपने प्रतिनिधिमंडल की स्थिति भी देख सकते हैं (प्रतिनिधि, अविभाजित, वापस लेने योग्य)। +> This table is horizontally scrollable, so scroll right to see delegation status: delegating, undelegating, or withdrawable. -![Explorer Image 13](/img/Delegation-Stats.png) +![Delegation Stats](/img/Delegation-Stats.png) -### क्यूरेटिंग टैब +#### क्यूरेटिंग टैब -In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. +The Curation tab displays all the Subgraphs you’re signaling on (thus enabling you to receive query fees). Signaling allows Curators to highlight to Indexers which Subgraphs are valuable and trustworthy, thus signaling that they need to be indexed on. इस टैब के भीतर, आपको इसका अवलोकन मिलेगा: @@ -232,22 +260,22 @@ In the Curation tab, you’ll find all the Subgraphs you’re signaling on (thus - Query rewards per Subgraph - दिनांक विवरण पर अद्यतन किया गया -![Explorer Image 14](/img/Curation-Stats.png) +![Curation Stats](/img/Curation-Stats.png) -### आपकी प्रोफ़ाइल सेटिंग्स +#### आपकी प्रोफ़ाइल सेटिंग्स अपने उपयोगकर्ता प्रोफ़ाइल के भीतर, आप अपने व्यक्तिगत प्रोफ़ाइल विवरण (जैसे ENS नाम सेट करना) प्रबंधित करने में सक्षम होंगे। यदि आप एक इंडेक्सर हैं, तो आपके पास अपनी उंगलियों पर सेटिंग्स तक और भी अधिक पहुंच है। अपने उपयोगकर्ता प्रोफ़ाइल में, आप अपने प्रतिनिधि पैरामीटर और ऑपरेटर सेट अप करने में सक्षम होंगे। - ऑपरेटर इंडेक्सर की ओर से प्रोटोकॉल में सीमित कार्रवाई करते हैं, जैसे आवंटन खोलना और बंद करना। ऑपरेटर आमतौर पर अन्य एथेरियम पते होते हैं, जो उनके स्टेकिंग वॉलेट से अलग होते हैं, नेटवर्क तक गेटेड एक्सेस के साथ जिसे इंडेक्सर्स व्यक्तिगत रूप से सेट कर सकते हैं - प्रत्यायोजन पैरामीटर की सहायता से आप अपने और अपने प्रतिनियुक्तियों के बीच GRT के वितरण को नियंत्रित कर सकते हैं. -![Explorer Image 15](/img/Profile-Settings.png) +![Profile Settings](/img/Profile-Settings.png) As your official portal into the world of decentralized data, Graph Explorer allows you to take a variety of actions, no matter your role in the network. You can get to your profile settings by opening the dropdown menu next to your address, then clicking on the Settings button. ![Wallet details](/img/Wallet-Details.png) -## Additional Resources +### Additional Resources ### वीडियो गाइड From da81dc129cc4078c7dabd49aff5da8d61ba93968 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 16:59:56 -0400 Subject: [PATCH 155/290] New translations about.mdx (Romanian) --- website/src/pages/ro/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/ro/about.mdx b/website/src/pages/ro/about.mdx index 0c18db196d1b..5f554bbb18b1 100644 --- a/website/src/pages/ro/about.mdx +++ b/website/src/pages/ro/about.mdx @@ -1,67 +1,55 @@ --- -title: Despre The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## What is The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### What is The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png) -The flow follows these steps: - -1. A dapp adds data to Ethereum through a transaction on a smart contract. -2. The smart contract emits one or more events while processing the transaction. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats. - ## Next Steps -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From bcf9398f1ccbe6c094fca28853726681fcf8e3e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 16:59:57 -0400 Subject: [PATCH 156/290] New translations about.mdx (French) --- website/src/pages/fr/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/fr/about.mdx b/website/src/pages/fr/about.mdx index 1cce1a4218ea..62fd8539f78b 100644 --- a/website/src/pages/fr/about.mdx +++ b/website/src/pages/fr/about.mdx @@ -1,67 +1,55 @@ --- -title: À propos de The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Qu’est-ce que The Graph ? +## Explanation -The Graph est un puissant protocole décentralisé qui permet d'interroger et d'indexer facilement les données de la blockchain. Il simplifie le processus complexe de requête des données blockchain, rendant ainsi le développement des applications décentralisées (dapps) plus rapide et plus simple. +### Qu’est-ce que The Graph ? -## Comprendre les fondamentaux +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Des projets dotés de contrats intelligents complexes tels que [Uniswap](https://uniswap.org/) et les initiatives NFT comme [Bored Ape Yacht Club](https://boredapeyachtclub.com/) stockent leurs données sur la blockchain Ethereum, rendant très difficile la lecture directe de données autres que les données de base depuis la blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Défis sans The Graph⁠ +### Why is Blockchain Data Hard to Query? -Dans le cas de l'exemple mentionné ci-dessus, Bored Ape Yacht Club, vous pouvez effectuer de simples opérations de lecture sur [le contrat](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). Vous pouvez voir le propriétaire d'un certain Ape, lire l'URI du contenu d'un Ape en fonction de son ID, ou connaître l'offre totale en circulation. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- Cela est possible car ces opérations de lecture sont programmées directement dans le contrat intelligent lui-même. Cependant, des requêtes et des opérations plus avancées, spécifiques et concrètes, telles que l'agrégation, la recherche, l'établissement de relations ou le filtrage complexe **ne sont pas possibles**. +## Solution -- Par exemple, si vous souhaitez identifier les Apes détenus par une adresse spécifique et affiner votre recherche en fonction d'une caractéristique particulière, il serait impossible d'obtenir cette information en interagissant directement avec le contrat. +### How The Graph Solves This -- Pour obtenir plus de données, vous devriez traiter chaque événement de [`transfert`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) jamais émis, lire les métadonnées d'IPFS en utilisant l'ID du Token et le hash IPFS, puis les agréger. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Pourquoi est-ce un problème ? +Each Subgraph defines: -Il faudrait des **heures, voire des jours,** pour qu'une application décentralisée (dapp) fonctionnant dans un navigateur obtienne une réponse à ces questions simples. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Les spécificités de la blockchain, comme la finalité des transactions, les réorganisations de chaîne et les blocs oncles (blocs rejetés lorsque deux blocs sont créés simultanément, ce qui entraîne l'omission d'un bloc de la blockchain.), ajoutent de la complexité au processus, rendant longue et conceptuellement difficile la récupération de résultats précis à partir des données de la blockchain. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph apporte une solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Aujourd'hui, il existe un protocole décentralisé soutenu par l'implémentation open source de [Graph Node](https://github.com/graphprotocol/graph-node) qui permet ce processus. +2. As the transaction is processed, the smart contract emits one or more events. -### Comment fonctionne The Graph⁠ +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Spécificités⁠ - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Un graphique expliquant comment The Graph utilise Graph Node pour répondre aux requêtes des consommateurs de données](/img/graph-dataflow.png) -La description des étapes du flux : - -1. Une dapp ajoute des données à Ethereum via une transaction sur un contrat intelligent. -2. Le contrat intelligent va alors produire un ou plusieurs événements lors du traitement de la transaction. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Le dapp interroge le Graph Node pour des données indexées à partir de la blockchain, à l'aide du [point de terminaison GraphQL](https://graphql.org/learn/) du noeud. À son tour, le Graph Node traduit les requêtes GraphQL en requêtes pour sa base de données sous-jacente afin de récupérer ces données, en exploitant les capacités d'indexation du magasin. Le dapp affiche ces données dans une interface utilisateur riche pour les utilisateurs finaux, qui s'en servent pour émettre de nouvelles transactions sur Ethereum. Le cycle se répète. - ## Les Étapes suivantes -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 6e32b8957f023971c05c47fd64d024ba75f8b533 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 16:59:58 -0400 Subject: [PATCH 157/290] New translations about.mdx (Spanish) --- website/src/pages/es/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/es/about.mdx b/website/src/pages/es/about.mdx index ffa133b4e0b7..b04de3e51252 100644 --- a/website/src/pages/es/about.mdx +++ b/website/src/pages/es/about.mdx @@ -1,67 +1,55 @@ --- -title: Acerca de The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Que es The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Que es The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Un gráfico explicando como The Graph usa Graph Node para servir consultas a los consumidores de datos](/img/graph-dataflow.png) -El flujo sigue estos pasos: - -1. Una aplicación descentralizada (dapp) añade datos a Ethereum a través de una transacción en un contrato inteligente. -2. El contrato inteligente emite uno o más eventos mientras procesa la transacción. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. La dapp consulta a través de Graph Node los datos indexados de la blockchain, utilizando el [GraphQL endpoint](https://graphql.org/learn/) del nodo. El Nodo de The Graph, a su vez, traduce las consultas GraphQL en consultas para su almacenamiento de datos subyacentes con el fin de obtener estos datos, haciendo uso de las capacidades de indexación que ofrece el almacenamiento. La dapp muestra estos datos en una interfaz muy completa para el usuario, a fin de que los end users que usan este subgrafo puedan emitir nuevas transacciones en Ethereum. El ciclo se repite. - ## Próximos puntos -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From e57c75f3297056f2780863f37c387cc0e65d7c81 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 16:59:59 -0400 Subject: [PATCH 158/290] New translations about.mdx (Arabic) --- website/src/pages/ar/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/ar/about.mdx b/website/src/pages/ar/about.mdx index 93dbeb51f658..67d4ff9a90c2 100644 --- a/website/src/pages/ar/about.mdx +++ b/website/src/pages/ar/about.mdx @@ -1,67 +1,55 @@ --- -title: حول The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## What is The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### What is The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png) -تدفق البيانات يتبع الخطوات التالية: - -1. A dapp adds data to Ethereum through a transaction on a smart contract. -2. العقد الذكي يصدر حدثا واحدا أو أكثر أثناء معالجة الإجراء. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats. - ## الخطوات التالية -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From bb1e1c7fd00b1c41370757f7cc406af7a0220115 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:01 -0400 Subject: [PATCH 159/290] New translations about.mdx (Czech) --- website/src/pages/cs/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/cs/about.mdx b/website/src/pages/cs/about.mdx index 1f43c663437f..5766eb712d13 100644 --- a/website/src/pages/cs/about.mdx +++ b/website/src/pages/cs/about.mdx @@ -1,67 +1,55 @@ --- -title: O Grafu +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Co je Graf? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Co je Graf? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Grafu vysvětlující, jak Graf používá Uzel grafu k doručování dotazů konzumentům dat](/img/graph-dataflow.png) -Průběh se řídí těmito kroky: - -1. Dapp přidává data do Ethereum prostřednictvím transakce na chytrém kontraktu. -2. Chytrý smlouva vysílá při zpracování transakce jednu nebo více událostí. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Aplikace dapp se dotazuje grafického uzlu na data indexovaná z blockchainu pomocí [GraphQL endpoint](https://graphql.org/learn/). Uzel Grafu zase překládá dotazy GraphQL na dotazy pro své podkladové datové úložiště, aby tato data načetl, přičemž využívá indexovací schopnosti úložiště. Dapp tato data zobrazuje v bohatém UI pro koncové uživatele, kteří je používají k vydávání nových transakcí na platformě Ethereum. Cyklus se opakuje. - ## Další kroky -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From f2d9b6a3fae17ad73f86cc520443f409b7aea43a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:02 -0400 Subject: [PATCH 160/290] New translations about.mdx (German) --- website/src/pages/de/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/de/about.mdx b/website/src/pages/de/about.mdx index 30ff84ae06f0..ae3f0e5334af 100644 --- a/website/src/pages/de/about.mdx +++ b/website/src/pages/de/about.mdx @@ -1,67 +1,55 @@ --- -title: Über The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Was ist The Graph? +## Explanation -The Graph ist ein leistungsstarkes dezentrales Protokoll, das eine nahtlose Abfrage und Indizierung von Blockchain-Daten ermöglicht. Es vereinfacht den komplexen Prozess der Abfrage von Blockchain-Daten und macht die App-Entwicklung schneller und einfacher. +### Was ist The Graph? -## Grundlagen verstehen +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projekte mit komplexen Smart Contracts wie [Uniswap](https://uniswap.org/) und NFTs-Initiativen wie [Bored Ape Yacht Club](https://boredapeyachtclub.com/) speichern Daten auf der Ethereum-Blockchain, was es sehr schwierig macht, etwas anderes als grundlegende Daten direkt von der Blockchain zu lesen. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Herausforderungen ohne The Graph +### Why is Blockchain Data Hard to Query? -Im Fall des oben aufgeführten konkreten Beispiels, Bored Ape Yacht Club, können Sie grundlegende Leseoperationen auf [dem Vertrag](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) durchführen. Sie können den Besitzer eines bestimmten Ape auslesen, die Inhalts-URI eines Ape anhand seiner ID lesen oder das Gesamtangebot auslesen. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- Dies ist möglich, da diese Lesevorgänge direkt in den Smart Contract selbst programmiert sind. Allerdings sind fortgeschrittene, spezifische und reale Abfragen und Operationen wie Aggregation, Suche, Beziehungen und nicht-triviale Filterung **nicht möglich**. +## Solution -- Wenn Sie sich beispielsweise nach Apes erkundigen möchten, die einer bestimmten Adresse gehören, und Ihre Suche anhand eines bestimmten Merkmals verfeinern möchten, können Sie diese Informationen nicht durch direkte Interaktion mit dem Vertrag selbst erhalten. +### How The Graph Solves This -- Um mehr Daten zu erhalten, müsste man jedes einzelne [`Übertragungsereignis`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746), das jemals gesendet wurde, verarbeiten, die Metadaten aus IPFS unter Verwendung der Token-ID und des IPFS-Hashs lesen und dann zusammenfassen. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Warum ist das ein Problem? +Each Subgraph defines: -Es würde **Stunden oder sogar Tage** dauern, bis eine dezentrale Anwendung (dapp), die in einem Browser läuft, eine Antwort auf diese einfachen Fragen erhält. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternativ können Sie einen eigenen Server einrichten, die Transaktionen verarbeiten, sie in einer Datenbank speichern und einen API-Endpunkt zur Abfrage der Daten erstellen. Diese Option ist jedoch [Ressourcen-intensiv](/resources/benefits/), muss gewartet werden, stellt einen Single Point of Failure dar und bricht wichtige Sicherheitseigenschaften, die für die Dezentralisierung erforderlich sind. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain-Eigenschaften wie Endgültigkeit, Umstrukturierung der Kette und nicht gesperrte Blöcke erhöhen die Komplexität des Prozesses und machen es zeitaufwändig und konzeptionell schwierig, genaue Abfrageergebnisse aus Blockchain-Daten zu erhalten. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph bietet eine Lösung +### Data Flow Overview -The Graph löst diese Herausforderung mit einem dezentralen Protokoll, das die Blockchain-Daten indiziert und eine effiziente und leistungsstarke Abfrage ermöglicht. Diese APIs (indizierte „Subgraphen“) können dann mit einer Standard-GraphQL-API abgefragt werden. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Heute gibt es ein dezentralisiertes Protokoll, das durch die Open-Source-Implementierung von [Graph Node](https://github.com/graphprotocol/graph-node) unterstützt wird und diesen Prozess ermöglicht. +2. As the transaction is processed, the smart contract emits one or more events. -### Die Funktionsweise von The Graph +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Die Indexierung von Blockchain-Daten ist sehr schwierig, aber The Graph macht es einfach. The Graph lernt, wie man Ethereum-Daten mit Hilfe von Subgraphen indizieren kann. Subgraphen sind benutzerdefinierte APIs, die auf Blockchain-Daten aufgebaut sind. Sie extrahieren Daten aus einer Blockchain, verarbeiten sie und speichern sie so, dass sie nahtlos über GraphQL abgefragt werden können. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Besonderheiten - -- The Graph verwendet Subgraph-Beschreibungen, die als Subgraph-Manifest innerhalb des Subgraphen bekannt sind. - -- Die Subgraph-Beschreibung beschreibt die Smart Contracts, die für einen Subgraphen von Interesse sind, die Ereignisse innerhalb dieser Verträge, auf die man sich konzentrieren soll, und wie man die Ereignisdaten den Daten zuordnet, die The Graph in seiner Datenbank speichern wird. - -- Wenn Sie einen Subgraphen erstellen, müssen Sie ein Subgraphenmanifest schreiben. - -- Nachdem Sie das `Subgraphenmanifest` geschrieben haben, können Sie das Graph CLI verwenden, um die Definition im IPFS zu speichern und einen Indexer anzuweisen, mit der Indizierung von Daten für diesen Subgraphen zu beginnen. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. Das nachstehende Diagramm enthält detailliertere Informationen über den Datenfluss, nachdem ein Subgraph-Manifest mit Ethereum-Transaktionen bereitgestellt wurde. ![Eine graphische Darstellung, die erklärt, wie The Graph Graph Node verwendet, um Abfragen an Datenkonsumenten zu stellen](/img/graph-dataflow.png) -Der Ablauf ist wie folgt: - -1. Eine Dapp fügt Ethereum durch eine Transaktion auf einem Smart Contract Daten hinzu. -2. Der Smart Contract gibt während der Verarbeitung der Transaktion ein oder mehrere Ereignisse aus. -3. Graph Node scannt Ethereum kontinuierlich nach neuen Blöcken und den darin enthaltenen Daten für Ihren Subgraph. -4. Graph Node findet in diesen Blöcken Ethereum-Ereignisse für Ihren Subgraph und führt die von Ihnen bereitgestellten Mapping-Handler aus. Das Mapping ist ein WASM-Modul, das die Dateneinheiten erstellt oder aktualisiert, die Graph Node als Reaktion auf Ethereum-Ereignisse speichert. -5. Die Dapp fragt den Graph Node über den [GraphQL-Endpunkt](https://graphql.org/learn/) des Knotens nach Daten ab, die von der Blockchain indiziert wurden. Der Graph Node wiederum übersetzt die GraphQL-Abfragen in Abfragen für seinen zugrundeliegenden Datenspeicher, um diese Daten abzurufen, wobei er die Indexierungsfunktionen des Speichers nutzt. Die Dapp zeigt diese Daten in einer reichhaltigen Benutzeroberfläche für die Endnutzer an, mit der diese dann neue Transaktionen auf Ethereum durchführen können. Der Zyklus wiederholt sich. - ## Nächste Schritte -In den folgenden Abschnitten werden die Subgraphen, ihr Einsatz und die Datenabfrage näher erläutert. - -Bevor Sie Ihren eigenen Subgraph schreiben, sollten Sie den [Graph Explorer](https://thegraph.com/explorer) erkunden und sich einige der bereits eingesetzten Subgraphen ansehen. Die Seite jedes Subgraphen enthält eine GraphQL-Spielwiese, mit der Sie seine Daten abfragen können. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From adfd58def0f7a25079a1969e370b3e5ab374bc31 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:04 -0400 Subject: [PATCH 161/290] New translations about.mdx (Italian) --- website/src/pages/it/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/it/about.mdx b/website/src/pages/it/about.mdx index 62f0bf4d3c61..8fc32184b8fd 100644 --- a/website/src/pages/it/about.mdx +++ b/website/src/pages/it/about.mdx @@ -1,67 +1,55 @@ --- -title: Informazioni su The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Che cos'è The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Che cos'è The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Un grafico che spiega come The Graph utilizza Graph Node per servire le query ai consumatori di dati](/img/graph-dataflow.png) -Il flusso segue questi passi: - -1. Una dapp aggiunge dati a Ethereum attraverso una transazione su uno smart contract. -2. Lo smart contract emette uno o più eventi durante l'elaborazione della transazione. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. La dapp effettua query del Graph Node per ottenere dati indicizzati dalla blockchain, utilizzando il [ GraphQL endpoint del nodo](https://graphql.org/learn/). Il Graph Node a sua volta traduce le query GraphQL in query per il suo archivio dati sottostante, al fine di recuperare questi dati, sfruttando le capacità di indicizzazione dell'archivio. La dapp visualizza questi dati in una ricca interfaccia utente per gli utenti finali, che li utilizzano per emettere nuove transazioni su Ethereum. Il ciclo si ripete. - ## I prossimi passi -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 8981bcdc7a1ca244868c2e9dbad8dc776b76cf3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:05 -0400 Subject: [PATCH 162/290] New translations about.mdx (Japanese) --- website/src/pages/ja/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/ja/about.mdx b/website/src/pages/ja/about.mdx index b4462cd3c1c8..d1974b836c32 100644 --- a/website/src/pages/ja/about.mdx +++ b/website/src/pages/ja/about.mdx @@ -1,67 +1,55 @@ --- -title: The Graphについて +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## とは「ザ・グラフ」 +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### とは「ザ・グラフ」 -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![グラフがグラフ ノードを使用してデータ コンシューマーにクエリを提供する方法を説明する図](/img/graph-dataflow.png) -フローは以下のステップに従います。 - -1. Dapp は、スマート コントラクトのトランザクションを通じて Ethereum にデータを追加します。 -2. スマートコントラクトは、トランザクションの処理中に 1 つまたは複数のイベントを発行します。 -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Dapp は、ノードの [GraphQL エンドポイント](https://graphql.org/learn/) を使用して、ブロックチェーンからインデックス付けされたデータをグラフ ノードに照会します。グラフ ノードは、ストアのインデックス作成機能を利用して、このデータを取得するために、GraphQL クエリを基盤となるデータ ストアのクエリに変換します。 dapp は、このデータをエンドユーザー向けの豊富な UI に表示し、エンドユーザーはそれを使用して Ethereum で新しいトランザクションを発行します。サイクルが繰り返されます。 - ## 次のステップ -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 351859677e99861eca96109b08d152ee65175a3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:07 -0400 Subject: [PATCH 163/290] New translations about.mdx (Korean) --- website/src/pages/ko/about.mdx | 64 ++++++++++++++-------------------- 1 file changed, 26 insertions(+), 38 deletions(-) diff --git a/website/src/pages/ko/about.mdx b/website/src/pages/ko/about.mdx index 833b097673d2..5f554bbb18b1 100644 --- a/website/src/pages/ko/about.mdx +++ b/website/src/pages/ko/about.mdx @@ -1,67 +1,55 @@ --- title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## What is The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### What is The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png) -The flow follows these steps: - -1. A dapp adds data to Ethereum through a transaction on a smart contract. -2. The smart contract emits one or more events while processing the transaction. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats. - ## Next Steps -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From f4d15642d3dde5e21f2c90bd67b96af2016f7e57 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:08 -0400 Subject: [PATCH 164/290] New translations about.mdx (Dutch) --- website/src/pages/nl/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/nl/about.mdx b/website/src/pages/nl/about.mdx index 7fde3b3d507d..5f554bbb18b1 100644 --- a/website/src/pages/nl/about.mdx +++ b/website/src/pages/nl/about.mdx @@ -1,67 +1,55 @@ --- -title: Over The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## What is The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### What is The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png) -The flow follows these steps: - -1. A dapp adds data to Ethereum through a transaction on a smart contract. -2. The smart contract emits one or more events while processing the transaction. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats. - ## Next Steps -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 69603384b4eb8268c6d830f0b1ba863786c375eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:09 -0400 Subject: [PATCH 165/290] New translations about.mdx (Polish) --- website/src/pages/pl/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/pl/about.mdx b/website/src/pages/pl/about.mdx index abfc28d9390b..61ba107f7b43 100644 --- a/website/src/pages/pl/about.mdx +++ b/website/src/pages/pl/about.mdx @@ -1,67 +1,55 @@ --- -title: Więcej o The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Co to jest The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Co to jest The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Grafika wyjaśniająca sposób w jaki protokół The Graph wykorzystuje węzeł Graph Node by obsługiwać zapytania dla konsumentów danych](/img/graph-dataflow.png) -Proces ten przebiega według poniższych kroków: - -1. Aplikacja dApp dodaje dane do sieci Ethereum za pomocą transakcji w smart kontrakcie. -2. Inteligentny kontrakt emituje jedno lub więcej zdarzeń podczas przetwarzania transakcji. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Aplikacja dApp wysyła zapytanie do węzła Graph Node o dane zindeksowane na blockchainie, korzystając z [punktu końcowego GraphQL](https://graphql.org/learn/). Węzeł Graph Node przekształca zapytania GraphQL na zapytania do swojego podstawowego magazynu danych w celu pobrania tych danych, wykorzystując zdolności indeksowania magazynu. Aplikacja dApp wyświetla te dane w interfejsie użytkownika dla użytkowników końcowych, którzy używają go do tworzenia nowych transakcji w sieci Ethereum. Cykl się powtarza. - ## Kolejne kroki -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From fb63e7dcf53474bc3f11537c484f14313343a51f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:11 -0400 Subject: [PATCH 166/290] New translations about.mdx (Portuguese) --- website/src/pages/pt/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/pt/about.mdx b/website/src/pages/pt/about.mdx index 22d7582d014d..d77b0df8f8bc 100644 --- a/website/src/pages/pt/about.mdx +++ b/website/src/pages/pt/about.mdx @@ -1,67 +1,55 @@ --- -title: Sobre o The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## O que é o The Graph? +## Explanation -O The Graph é um protocolo descentralizado poderoso que permite a consulta e indexação rápida de dados em blockchain. Ele simplifica o processo complexo de queries de dados de blockchain, o que facilita e acelera a programação de dApps. +### O que é o The Graph? -## Entenda o Básico +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projetos com contratos inteligentes complexos, como o [Uniswap](https://uniswap.org/) e iniciativas de NFTs como o [Bored Ape Yacht Club](https://boredapeyachtclub.com/), armazenam dados na blockchain Ethereum, o que torna muito difícil ler qualquer coisa que não seja dados básicos diretamente da blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Desafios sem o The Graph +### Why is Blockchain Data Hard to Query? -No caso do exemplo listado acima, o Bored Ape Yacht Club, é possível realizar operações básicas [no contrato](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). Pode-se ver o dono de um certo Ape, ler a URI de um Ape com base na sua ID, ou ler a reserva total. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- Isto pode ser feito porque estas operações de leitura são programadas diretamente no próprio contrato inteligente. Porém, queries e operações mais avançadas e específicas do mundo real, como agregação, busca, relacionamentos e filtros não triviais, **não são possíveis**. +## Solution -- Por exemplo, se alguém quisesse ver Apes em posse de um endereço específico e refinar a sua busca com base numa característica particular, não seria possível obter aquela informação ao interagir diretamente com o próprio contrato. +### How The Graph Solves This -- Para conseguir mais dados, seria necessário processar todo evento de [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) emitido na história, ler os metadados do IPFS usando a ID e o hash IPFS do token, e depois agregá-los. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Por que isto é um problema? +Each Subgraph defines: -Levariam **horas, ou até mesmo dias**, para que um aplicativo descentralizado (dApp) executado em um navegador conseguisse uma resposta a estas questões simples. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Propriedades de blockchain, como finalidade, reorganizações de chain, ou blocos uncle, complicam ainda mais este processo, e não apenas o tornam longo e cansativo, mas dificultam conceitualmente a retirada de resultados precisos de queries dos dados da blockchain. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Providencia uma Solução +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Hoje, há um protocolo descentralizado apoiado pela implementação de código aberto do [Graph Node](https://github.com/graphprotocol/graph-node) que facilita este processo. +2. As the transaction is processed, the smart contract emits one or more events. -### Como o The Graph Funciona +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Especificações - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Um gráfico que explica como o The Graph utiliza Graph Nodes para servir queries para consumidores de dados](/img/graph-dataflow.png) -O fluxo segue estes passos: - -1. Um dApp adiciona dados à Ethereum através de uma transação em contrato inteligente. -2. O contrato inteligente emite um ou mais eventos enquanto processa a transação. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. O dApp consulta o Graph Node para dados indexados da blockchain, através do [endpoint GraphQL](https://graphql.org/learn/) do node. O Graph Node, por sua vez, traduz os queries GraphQL em queries para o seu armazenamento subjacente de dados para poder retirar estes dados, com o uso das capacidades de indexação do armazenamento. O dApp exibe estes dados em uma interface rica para utilizadores finais, que eles usam para emitir novas transações na Ethereum. E o ciclo se repete. - ## Próximos Passos -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 62854c9dceb52e507ac8ce113c01a1f2c6bc9e71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:12 -0400 Subject: [PATCH 167/290] New translations about.mdx (Russian) --- website/src/pages/ru/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/ru/about.mdx b/website/src/pages/ru/about.mdx index d940c455bdf7..f6ce5dcfc2ec 100644 --- a/website/src/pages/ru/about.mdx +++ b/website/src/pages/ru/about.mdx @@ -1,67 +1,55 @@ --- -title: О The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Что такое Graph? +## Explanation -The Graph — это мощный децентрализованный протокол, который позволяет беспрепятственно запрашивать и индексировать данные блокчейна. Это упрощает сложный процесс запроса данных блокчейна, ускоряя и упрощая разработку децентрализованных приложений. +### Что такое Graph? -## Понимание основ +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Проекты со сложными смарт-контрактами, такие как [Uniswap](https://uniswap.org/), и инициативы по созданию NFT, подобные [Bored Ape Yacht Club](https://boredapeyachtclub.com/), хранят данные в блокчейне Ethereum, что делает практически невозможным непосредственное чтение чего-либо, кроме базовых данных, из блокчейна. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Сложности, которые могут возникнуть без использования The Graph +### Why is Blockchain Data Hard to Query? -В приведенном выше примере, Bored Ape Yacht Club, Вы можете выполнять базовые операции чтения [контракта](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). Вы можете узнать владельца определенного Ape, прочитать URI контента Ape на основе его идентификатора или узнать общее предложение. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- Это можно сделать, поскольку данные операции чтения запрограммированы непосредственно в самом смарт-контракте. Однако более сложные, конкретные и реальные запросы и операции, такие как агрегирование, поиск, связи и нетривиальная фильтрация, **невозможны**. +## Solution -- Например, если Вы хотите узнать об Apes, принадлежащих определенному адресу, и уточнить свой поиск на основе конкретной характеристики, Вы не сможете получить эту информацию путем прямого взаимодействия с самим контрактом. +### How The Graph Solves This -- Чтобы получить больше данных, Вам придется обработать каждое когда-либо созданное событие [`передачи`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746), прочитать метаданные из IPFS, используя идентификатор токена и хэш IPFS, а затем агрегировать их. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Почему это является проблемой? +Each Subgraph defines: -Децентрализованному приложению (dapp), запущенному в браузере, потребуются **часы или даже дни**, чтобы получить ответ на эти простые вопросы. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -В качестве альтернативы у Вас есть возможность настроить собственный сервер, обрабатывать транзакции, хранить их в базе данных и создать конечную точку API для запроса данных. Однако этот вариант [ресурсоемок](/resources/benefits/), требует обслуживания, создает единую точку отказа и нарушает важные требования безопасности, необходимые для децентрализации. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Такие свойства блокчейна, как окончательность, реорганизация чейна и необработанные блоки, усложняют процесс, делая получение точных результатов запроса из данных блокчейна трудоемким и концептуально сложным. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph предлагает решение +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Сегодня существует децентрализованный протокол, поддерживаемый реализацией с открытым исходным кодом [Graph Node](https://github.com/graphprotocol/graph-node), который обеспечивает этот процесс. +2. As the transaction is processed, the smart contract emits one or more events. -### Как функционирует The Graph +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Специфические особенности - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![График, объясняющий потребителям данных, как The Graph использует Graph Node для обслуживания запросов](/img/graph-dataflow.png) -Данные проходят следующий путь: - -1. Dapp добавляет данные в Ethereum через транзакцию в смарт-контракте. -2. Смарт-контракт генерирует одно или несколько событий во время обработки транзакции. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Dapp запрашивает у Graph Node данные, проиндексированные с блокчейна, используя [конечную точку GraphQL](https://graphql.org/learn/) ноды. В свою очередь, Graph Node переводит запросы GraphQL в запросы к его базовому хранилищу данных, чтобы получить эти данные, используя возможности индексации этого хранилища. Dapp отображает эти данные в насыщенном пользовательском интерфейсе для конечных пользователей, который они используют для создания новых транзакций в Ethereum. Цикл повторяется. - ## Что далее -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From e284094b44aa5ae63011fcc93a6fcb134bebea4c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:14 -0400 Subject: [PATCH 168/290] New translations about.mdx (Swedish) --- website/src/pages/sv/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/sv/about.mdx b/website/src/pages/sv/about.mdx index 8f3ae9f1a8e7..0107ba23af82 100644 --- a/website/src/pages/sv/about.mdx +++ b/website/src/pages/sv/about.mdx @@ -1,67 +1,55 @@ --- -title: Om The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Vad är The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Vad är The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![En grafik som förklarar hur The Graf använder Graf Node för att servera frågor till datakonsumenter](/img/graph-dataflow.png) -Följande steg följs: - -1. En dapp lägger till data i Ethereum genom en transaktion på ett smart kontrakt. -2. Det smarta kontraktet sänder ut en eller flera händelser under bearbetningen av transaktionen. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Dappen frågar Graph Node om data som indexerats från blockkedjan med hjälp av nodens [GraphQL-slutpunkt](https://graphql.org/learn/). Graph Node översätter i sin tur GraphQL-frågorna till frågor för sin underliggande datalagring för att hämta dessa data, och använder lagrets indexeringsegenskaper. Dappen visar dessa data i ett användarvänligt gränssnitt för slutanvändare, som de använder för att utfärda nya transaktioner på Ethereum. Cykeln upprepas. - ## Nästa steg -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 59e213015b8c1db97e2e12515417d93ba1c26a53 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:15 -0400 Subject: [PATCH 169/290] New translations about.mdx (Turkish) --- website/src/pages/tr/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/tr/about.mdx b/website/src/pages/tr/about.mdx index 3b1dce5a5617..3a45ddfae492 100644 --- a/website/src/pages/tr/about.mdx +++ b/website/src/pages/tr/about.mdx @@ -1,67 +1,55 @@ --- -title: Graph Hakkında +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## The Graph Nedir? +## Explanation -The Graph, blokzinciri verilerinin pürüzsüz bir şekilde sorgulanmasını ve endekslenmesini sağlayan güçlü bir merkeziyetsiz protokoldür. Blokzinciri verilerini sorgulama sürecini basitleştirerek merkeziyetsiz uygulama (dapp) geliştirmeyi daha hızlı ve daha kolay hale getirir. +### The Graph Nedir? -## Temeller +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Karmaşık akıllı sözleşmelere sahip [Uniswap](https://uniswap.org/) gibi projeler ve [Bored Ape Yacht Club](https://boredapeyachtclub.com/) gibi NFT girişimleri Ethereum blokzinciri üzerinde veri depolar. Bu akıllı sözleşmelerin karmaşık doğası, temel verilerin ötesinde herhangi bir şeyin doğrudan blokzincirinden okunmasını ciddi derecede zorlaştırır. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### The Graph Olmadığında Karşılaşılan Zorluklar +### Why is Blockchain Data Hard to Query? -Yukarıda bahsedilen Bored Ape Yacht Club örneğinde, [sözleşmenin](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) okuma fonksiyonlarını kullanarak temel veri sorgulama işlemleri gerçekleştirebilirsiniz. Belirli bir Ape'in sahibini, ID numarasına göre Ape'in içerik URI'sini, ya da toplam arzı sorgulayabilirsiniz. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- Bu işlemler, okuma fonksiyonlarının doğrudan akıllı sözleşmeye kodlanmış olması sayesinde mümkündür. Ancak agregasyon, arama, ilişkisel veriler ve daha karmaşık filtrelemeler ile birlikte daha ileri düzey, spesifik ve gerçek dünyada karşılaşılan işlemlerin doğrudan akıllı sözleşmeler üzerinden yapılması **mümkün değildir**. +## Solution -- Örneğin, belirli bir adresin sahip olduğu Ape'leri sorgulamak ve aramanızı belirli bir özelliğe göre daraltmak isterseniz, bu bilgiyi doğrudan sözleşme ile etkileşime girerek elde edemezsiniz. +### How The Graph Solves This -- Daha fazla veri elde etmek için, şimdiye kadar yayımlanmış her bir [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) olayını işlemek, Token ID ve IPFS hash'ini kullanarak metaveriyi IPFS'ten okumak ve ardından bunları bir araya getirmeniz gerekir. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Bu neden bir sorun? +Each Subgraph defines: -Bu basit sorulara yanıt almak, tarayıcıda çalışan bir merkeziyetsiz uygulama (dapp) için **saatler, hatta günler ** sürebilir. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Finalite, zincir yeniden organizasyonu ve "uncle" bloklar gibi blokzinciri özellikleri, sürece karmaşıklık katar ve doğru sorgu sonuçlarını blokzinciri verilerinden elde etmeyi zaman alıcı hale getirip kavramsal olarak zorlaştırır. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph'in Sağladığı Çözüm +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Artık, bu süreci mümkün kılan, [Graph Düğümü](https://github.com/graphprotocol/graph-node)'nün açık kaynaklı implementasyonuna dayanan merkeziyetsiz bir protokol mevcut. +2. As the transaction is processed, the smart contract emits one or more events. -### The Graph'in Çalışma Şekli +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Ayrıntılar - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![The Graph'in, Graph Düğümü'nü kullanarak veri tüketicilerine sorgu sunma sürecini açıklayan bir grafik](/img/graph-dataflow.png) -Veri akışı şu şekildedir: - -1. Bir dapp, bir akıllı sözleşme üzerinde işlem yaparak Ethereum'a veri ekler. -2. Akıllı sözleşme, işlemi işlerken bir veya daha fazla olay yayımlar. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Dapp, blokzincirinden endekslenen veriler için Graph Düğümüne, düğümün [GraphQL uç noktası](https://graphql.org/learn/) üzerinden sorgu gönderir. Graph Düğümü ise veriyi getirmek için bu sorguları kendi veri deposuna yönelik sorgulara çevirir ve depolama sisteminin endeksleme kabiliyetlerini kullanarak bu verileri alır. Dapp, bu verileri son kullanıcılar için zengin bir arayüzde gösterir ve kullanıcılar bu arayüzü kullanarak Ethereum'da yeni işlemler gerçekleştirir. Bu döngü tekrarlanır. - ## Sonraki Adımlar -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From a588a99d6a69a72842674241d40a73b3ea868ab1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:17 -0400 Subject: [PATCH 170/290] New translations about.mdx (Ukrainian) --- website/src/pages/uk/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/uk/about.mdx b/website/src/pages/uk/about.mdx index 55eb5593f48b..523dfadf84ea 100644 --- a/website/src/pages/uk/about.mdx +++ b/website/src/pages/uk/about.mdx @@ -1,67 +1,55 @@ --- -title: Про The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## Що таке The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### Що таке The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![Малюнок, що пояснює, як The Graph використовує Graph Node для обслуговування запитів до споживачів даних](/img/graph-dataflow.png) -Цей потік даних проходить такі етапи: - -1. Додаток відправляє дані в мережу Ethereum через транзакцію в смартконтракті. -2. Під час обробки транзакції смартконтракт видає одну або декілька різних подій. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. Додаток запитує Graph Node про дані, проіндексовані в блокчейні, використовуючи [кінцеву точку GraphQL](https://graphql.org/learn/). The Graph Node, і собі, переводить запити GraphQL в запити до свого базового сховища даних, щоб отримати ці дані, використовуючи можливості індексації сховища. Dapp відображає ці дані в величезному інтерфейсі для кінцевих користувачів, який вони використовують для створення нових транзакцій на Ethereum. Цикл повторюється. - ## Наступні кроки -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 43a5fc8fbaee35ab2b2bfd72e85ef2cd878b283b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:18 -0400 Subject: [PATCH 171/290] New translations about.mdx (Chinese Simplified) --- website/src/pages/zh/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/zh/about.mdx b/website/src/pages/zh/about.mdx index df1778ca8c0b..97d5bda63989 100644 --- a/website/src/pages/zh/about.mdx +++ b/website/src/pages/zh/about.mdx @@ -1,67 +1,55 @@ --- -title: 关于 The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## 什么是 The Graph？ +## Explanation -The Graph是一个强大的去中心化协议，可以无缝地查询区块链数据并将其索引。 它简化了查询区块链数据的复杂过程，使开发dapp 更快和更容易。 +### 什么是 The Graph？ -## 了解基础知识 +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -像 [Uniswap](https://uniswap.org/)这样具有复杂智能合约的项目，以及像 [Bored Ape Yacht Club](https://boredapeyachtclub.com/) 这样的 NFTs 倡议，都在以太坊区块链上存储数据，因此，除了直接从区块链上读取基本数据外，真的很难。 +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### 没有The Graph的挑战 +### Why is Blockchain Data Hard to Query? -在上面列出的例子中，Bored Ape Yacht Club，您可以在 [合约](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code)上进行基本的读取操作。 您可以读取某个Ape的所有者。根据他们的ID阅读Ape的内容URI，或者阅读总供应。 +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- 之所以能够做到这一点，是因为这些已阅读的操作直接编入智能合约本身。 然而，更高级、具体和现实世界的查询和操作，如集成、搜索、关系和非微不足道的过滤， **是不可能的**。 +## Solution -- 例如，如果您想要查询某个特定地址所拥有的Ape，并根据某个特定特征改进您的搜索， 你无法通过与合约本身直接互动获取这种信息。 +### How The Graph Solves This -- 为了获得这些数据，你必须处理曾经发出的每一个 [`传输`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) 事件，使用Token ID和IPFS的哈希值从IPFS读取元数据，然后将其汇总。 +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### 为什么这是个问题？ +Each Subgraph defines: -在浏览器中运行的去中心化应用程序（dapp）需要**几小时甚至几天**才能得到这些简单问题的答案。 +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -你也可以建立你自己的服务器，在那里处理交易，把它们保存到数据库，并在上面建立一个 API 终端，以便查询数据。 然而，这种选择是[资源密集型的](/resources/benefits/)，需要维护，会出现单点故障，并破坏了去中心化化所需的重要安全属性。 +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -区块链的属性，如最终性、链重组或未封闭的区块，使这一过程进一步复杂化，并使从区块链数据中检索出正确查询结果不仅耗时，而且在概念上也很难。 +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph提供了一个解决办法 +### Data Flow Overview -The Graph通过一个去中心化的协议解决了这个挑战，这个协议可以索引并使区块链数据能够高效和高性能的查询。 这些API(索引的 "Subgraphs") 然后可以用标准的 GraphQL API查询。 +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -今天有一个去中心化的协议，它得到了 [Graph Node](https://github.com/graphprotocol/graph-node) 开放源代码实现的支持。 +2. As the transaction is processed, the smart contract emits one or more events. -### The Graph 如何起效 +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -索引区块链数据是非常困难的，但是The Graph使它变得容易。The Graph通过子图学习如何索引以太坊数据。 子图是基于 blockchain 数据从区块链中提取数据的自定义 API， 处理它，并存储它，以便它可以通过 GraphQL 无缝查询。 +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### 详情 - -- The Graph使用子图描述，它称为子图中的子图清单。 - -- 子图描述定义了子图所关注的智能合约，这些合约中需要关注的事件，以及如何将事件数据映射到The Graph将存储在其数据库中的数据。 - -- 创建子图时，您需要写子图清单。 - -- 一旦编写了`子图清单`，就可以使用Graph CLI将定义存储在IPFS中，并告诉索引人开始为该子图的数据编制索引。 +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. 此图提供了部署子图清单后用于处理以太坊交易的数据流的更多细节。 ![解释The Graph如何使用Graph节点向数据消费者提供查询的图形。](/img/graph-dataflow.png) -流程遵循这些步骤： - -1. 一个去中心化的应用程序通过智能合约上的交易向以太坊添加数据。 -2. 智能合约在处理交易时，会发出一个或多个事件。 -3. Graph 节点不断扫描以太坊的新区块和它们可能包含的子图的数据。 -4. Graph 节点在这些区块中为你的子图找到以太坊事件并运行你提供的映射处理程序。 映射是一个 WASM 模块，它创建或更新 Graph 节点存储的数据实体，以响应以太坊事件。 -5. 去中心化的应用程序使用Graph节点的[GraphQL 端点](https://graphql.org/learn/)，从区块链的索引中查询 Graph 节点的数据。 Graph 节点反过来将 GraphQL 查询转化为对其底层数据存储的查询，以便利用存储的索引功能来获取这些数据。 去中心化的应用程序在一个丰富的用户界面中为终端用户显示这些数据，他们用这些数据在以太坊上发行新的交易。 就这样周而复始。 - ## 下一步 -以下各节更深入地审视了子图、其部署情况和数据查询情况。 - -在编写自己的子图之前，建议您探索[Graph Explorer](https://thegraph.com/explorer)并查看一些已经部署的子图。每个Subgraph的页面都包含一个GraphQL游乐场，允许您查询其数据。 +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 8d8b338127d2e999bfdbd4d3a273b70040bb9b61 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:19 -0400 Subject: [PATCH 172/290] New translations about.mdx (Urdu (Pakistan)) --- website/src/pages/ur/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/ur/about.mdx b/website/src/pages/ur/about.mdx index d737a0994ad9..99b8b2874d2a 100644 --- a/website/src/pages/ur/about.mdx +++ b/website/src/pages/ur/about.mdx @@ -1,67 +1,55 @@ --- -title: گراف کے بارے میں +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## گراف کیا ہے؟ +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### گراف کیا ہے؟ -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![ایک گرافک یہ بتاتا ہے کہ گراف کس طرح ڈیٹا صارفین کو کیوریز پیش کرنے کے لیے گراف نوڈ کا استعمال کرتا ہے](/img/graph-dataflow.png) -بہاؤ ان مراحل کی پیروی کرتا ہے: - -1. ایک ڈیپ سمارٹ کنٹریکٹ پر ٹرانزیکشن کے ذریعے سے ایتھیریم میں ڈیٹا کا اضافہ کرتی ہے. -2. سمارٹ کنٹریکٹ ٹرانزیکشن پر کارروائی کے دوران ایک یا ایک سے زیادہ واقعات کا اخراج کرتا ہے. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. ڈیپ بلاکچین سے انڈیکس کردہ ڈیٹا کے لیے گراف نوڈ کو کیوری کرتی ہے, نوڈ کے [GraphQL اینڈ پوائنٹ](https://graphql.org/learn/) کا استعمال کرتے ہوئے. گراف نوڈ بدلے میں اس ڈیٹا کو حاصل کرنے کے لیے GraphQL کی کیوریز کو اپنے بنیادی ڈیٹا اسٹور کی کیوریز میں تبدیل کرتا ہے, سٹور کی انڈیکسنگ کی صلاحیتوں کا استعمال کرتے ہوئے. ڈیسینٹرلائزڈ ایپلیکیشن اس ڈیٹا کو صارفین کے لیے ایک بھرپور UI میں دکھاتی ہے, جسے وہ ایتھیریم پر نئی ٹرانزیکشنز جاری کرنے کے لیے استعمال کرتے ہیں. یہ سلسلہ دہرایا جاتا ہے. - ## اگلے مراحل -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 32bdc564e3f6acec98877721c3051de009d0507d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:21 -0400 Subject: [PATCH 173/290] New translations about.mdx (Vietnamese) --- website/src/pages/vi/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/vi/about.mdx b/website/src/pages/vi/about.mdx index dbcf77b348c9..78da571b8c29 100644 --- a/website/src/pages/vi/about.mdx +++ b/website/src/pages/vi/about.mdx @@ -1,67 +1,55 @@ --- -title: Về The Graph +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## What is The Graph? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### What is The Graph? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png) -Quy trình thực hiện theo các bước sau: - -1. A dapp adds data to Ethereum through a transaction on a smart contract. -2. Hợp đồng thông minh phát ra một hoặc nhiều sự kiện trong khi xử lý giao dịch. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats. - ## Bước tiếp theo -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 11ae5ce1b213787909454704f77278fcfcea328d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:22 -0400 Subject: [PATCH 174/290] New translations about.mdx (Marathi) --- website/src/pages/mr/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/mr/about.mdx b/website/src/pages/mr/about.mdx index 9597ecb03bb2..a8534ea1d258 100644 --- a/website/src/pages/mr/about.mdx +++ b/website/src/pages/mr/about.mdx @@ -1,67 +1,55 @@ --- -title: ग्राफ बद्दल +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## द ग्राफ म्हणजे काय? +## Explanation -The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier. +### द ग्राफ म्हणजे काय? -## Understanding the Basics +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain. +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### Challenges Without The Graph +### Why is Blockchain Data Hard to Query? -In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply. +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**. +## Solution -- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself. +### How The Graph Solves This -- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### Why is this a problem? +Each Subgraph defines: -It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph Provides a Solution +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process. +2. As the transaction is processed, the smart contract emits one or more events. -### How The Graph Functions +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### Specifics - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![ग्राफिक डेटा ग्राहकांना प्रश्न देण्यासाठी ग्राफ नोड कसा वापरतो हे स्पष्ट करणारे ग्राफिक](/img/graph-dataflow.png) -प्रवाह या चरणांचे अनुसरण करतो: - -1. A dapp स्मार्ट करारावरील व्यवहाराद्वारे इथरियममध्ये डेटा जोडते. -2. व्यवहारावर प्रक्रिया करताना स्मार्ट करार एक किंवा अधिक इव्हेंट सोडतो. -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. नोडचा [GraphQL एंडपॉइंट](https://graphql.org/learn/) वापरून ब्लॉकचेन वरून अनुक्रमित केलेल्या डेटासाठी dapp ग्राफ नोडची क्वेरी करते. ग्राफ नोड यामधून, स्टोअरच्या इंडेक्सिंग क्षमतांचा वापर करून, हा डेटा मिळविण्यासाठी त्याच्या अंतर्निहित डेटा स्टोअरच्या क्वेरींमध्ये GraphQL क्वेरीचे भाषांतर करतो. dapp हा डेटा अंतिम वापरकर्त्यांसाठी समृद्ध UI मध्ये प्रदर्शित करते, जो ते Ethereum वर नवीन व्यवहार जारी करण्यासाठी वापरतात. चक्राची पुनरावृत्ती होते. - ## पुढील पायऱ्या -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From f10559a9aa1ee6217433306c7db2afb3677e422f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:23 -0400 Subject: [PATCH 175/290] New translations about.mdx (Hindi) --- website/src/pages/hi/about.mdx | 66 ++++++++++++++-------------------- 1 file changed, 27 insertions(+), 39 deletions(-) diff --git a/website/src/pages/hi/about.mdx b/website/src/pages/hi/about.mdx index 98bf7a76374e..c4676efea513 100644 --- a/website/src/pages/hi/about.mdx +++ b/website/src/pages/hi/about.mdx @@ -1,67 +1,55 @@ --- -title: The Graph के बारे में +title: About The Graph +description: This page summarizes the core concepts and basics of The Graph Network. --- -## The Graph क्या है? +## Explanation -The Graph एक शक्तिशाली विकेंद्रीकृत प्रोटोकॉल है जो ब्लॉकचेन डेटा को आसानी से क्वेरी और इंडेक्स करने में सक्षम बनाता है। यह ब्लॉकचेन डेटा को क्वेरी करने की जटिल प्रक्रिया को सरल बनाता है, जिससे डैप विकास तेज और आसान हो जाता है। +### The Graph क्या है? -## मूल बातें समझना +The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/). -जटिल स्मार्ट कॉन्ट्रैक्ट्स वाले प्रोजेक्ट्स, जैसे [Uniswap](https://uniswap.org/) और NFT इनिशिएटिव्स जैसे [Bored Ape Yacht Club](https://boredapeyachtclub.com/), डेटा को एथेरियम ब्लॉकचेन पर स्टोर करते हैं, जिससे ब्लॉकचेन से सीधे मूलभूत डेटा के अलावा किसी अन्य जानकारी को पढ़ना बहुत कठिन हो जाता है। +The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval. -### The Graph के बिना चुनौतियाँ +### Why is Blockchain Data Hard to Query? -उदाहरण के रूप में, Bored Ape Yacht Club के मामले में, आप [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) पर बुनियादी रीड ऑपरेशन कर सकते हैं। आप किसी विशेष एपी के मालिक को पढ़ सकते हैं, एपी के ID के आधार पर कंटेंट URI पढ़ सकते हैं, या कुल आपूर्ति को पढ़ सकते हैं। +Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive. -- यह संभव है क्योंकि ये पढ़ाई संचालन सीधे स्मार्ट कॉन्ट्रैक्ट में प्रोग्राम किए गए हैं। हालांकि, अधिक उन्नत, विशिष्ट और वास्तविक दुनिया की क्वेरीज़ और संचालन जैसे कि एग्रीगेशन, सर्च, रिलेशनशिप, और जटिल फ़िल्टरिंग, **संभव नहीं हैं**। +## Solution -- उदाहरण के लिए, यदि आप किसी विशेष पते द्वारा स्वामित्व वाले Apes के बारे में पूछताछ करना चाहते हैं और किसी विशेष विशेषता के आधार पर अपनी खोज को परिष्कृत करना चाहते हैं, तो आप यह जानकारी सीधे कॉन्ट्रैक्ट के साथ बातचीत करके प्राप्त नहीं कर पाएंगे। +### How The Graph Solves This -- ज्यादा डेटा प्राप्त करने के लिए, आपको हर एक [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) इवेंट को प्रोसेस करना होगा, IPFS से Token ID और IPFS हैश का उपयोग करके मेटाडेटा पढ़ना होगा, और फिर उसे संक्षिप्त करना होगा। +The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing. -### यह एक समस्या क्यों है? +Each Subgraph defines: -यह सरल सवालों का जवाब पाने में एक ब्राउज़र में चल रही एक विकेन्द्रीकृत एप्लिकेशन (dapp) को **घंटे या यहाँ तक कि दिन** लग सकते हैं। +- Which smart contracts to watch +- Which events to extract +- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/) -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/) -ब्लॉकचेन की विशेषताएँ, जैसे अंतिमता, चेन पुनर्गठन, और अंकल ब्लॉक्स, प्रक्रिया में जटिलता जोड़ती हैं, जिससे ब्लॉकचेन डेटा से सटीक क्वेरी परिणाम प्राप्त करना समय लेने वाला और अवधारणात्मक रूप से चुनौतीपूर्ण हो जाता है। +1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings. +2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS. +3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks. +4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/). -## The Graph एक समाधान प्रदान करता है +### Data Flow Overview -The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "Subgraphs") can then be queried with a standard GraphQL API. +1. A dapp triggers a transaction on Ethereum by interacting with a smart contract. -आज एक विकेंद्रीकृत प्रोटोकॉल है, जो [Graph Node](https://github.com/graphprotocol/graph-node) के ओपन सोर्स इम्प्लीमेंटेशन द्वारा समर्थित है, जो इस प्रक्रिया को सक्षम बनाता है। +2. As the transaction is processed, the smart contract emits one or more events. -### The Graph कैसे काम करता है +3. [Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph. -Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using Subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL. +4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed. -#### विशिष्टताएँ - -- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph. - -- The Subgraph description outlines the smart contracts of interest for a Subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database. - -- When creating a Subgraph, you need to write a Subgraph manifest. - -- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that Subgraph. +5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle. The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions. ![एक ग्राफ़िक समझाता है कि कैसे ग्राफ़ डेटा उपभोक्ताओं को क्वेरीज़ प्रदान करने के लिए ग्राफ़ नोड का उपयोग करता है](/img/graph-dataflow.png) -प्रवाह इन चरणों का पालन करता है: - -1. एक विकेंद्रीकृत एप्लिकेशन स्मार्ट अनुबंध पर लेनदेन के माध्यम से एथेरियम में डेटा जोड़ता है। -2. लेन-देन संसाधित करते समय स्मार्ट अनुबंध एक या अधिक घटनाओं का उत्सर्जन करता है। -3. Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain. -4. Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events. -5. नोड के [GraphQL समापन बिंदु](https://graphql.org/learn/) का उपयोग करते हुए, विकेन्द्रीकृत एप्लिकेशन ब्लॉकचैन से अनुक्रमित डेटा के लिए ग्राफ़ नोड से पूछताछ करता है। ग्राफ़ नोड बदले में इस डेटा को प्राप्त करने के लिए, स्टोर की इंडेक्सिंग क्षमताओं का उपयोग करते हुए, अपने अंतर्निहित डेटा स्टोर के लिए ग्राफ़कॉल प्रश्नों का अनुवाद करता है। विकेंद्रीकृत एप्लिकेशन इस डेटा को एंड-यूजर्स के लिए एक समृद्ध यूआई में प्रदर्शित करता है, जिसका उपयोग वे एथेरियम पर नए लेनदेन जारी करने के लिए करते हैं। चक्र दोहराता है। - ## अगले कदम -The following sections provide a more in-depth look at Subgraphs, their deployment and data querying. - -Before you write your own Subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed Subgraphs. Each Subgraph's page includes a GraphQL playground, allowing you to query its data. +Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs. From 4e7f904e4cb902e1ad67f54643cfacc1b430e494 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:25 -0400 Subject: [PATCH 176/290] New translations tap.mdx (German) --- website/src/pages/de/indexing/tap.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/de/indexing/tap.mdx b/website/src/pages/de/indexing/tap.mdx index a3eec839d931..8d76412fd28b 100644 --- a/website/src/pages/de/indexing/tap.mdx +++ b/website/src/pages/de/indexing/tap.mdx @@ -45,19 +45,19 @@ Solange Sie `tap-agent` und `indexer-agent` ausführen, wird alles automatisch a ### Verträge -| Vertrag | Arbitrum Mainnet (42161) | Arbitrum Sepolia (421614) | -| ------------------- | -------------------------------------------- | -------------------------------------------- | -| TAP-Prüfer | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | -| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | -| Treuhandkonto | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | +| Vertrag | Arbitrum Mainnet (42161) | Arbitrum Sepolia (421614) | +| -------------------------- | -------------------------------------------- | -------------------------------------------- | +| TAP-Prüfer | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Treuhandkonto | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | ### Gateway -| Komponente | Edge- und Node-Mainnet (Arbitrum-Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | -| ------------- | --------------------------------------------- | --------------------------------------------- | -| Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| Unterzeichner | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| Komponente | Edge- und Node-Mainnet (Arbitrum-Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | +| ---------------- | ---------------------------------------------- | --------------------------------------------- | +| Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| Unterzeichner | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### Voraussetzungen From 15525d805e6cba27726a8d657a27c21c8ec23edc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:26 -0400 Subject: [PATCH 177/290] New translations tap.mdx (Portuguese) --- website/src/pages/pt/indexing/tap.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/pt/indexing/tap.mdx b/website/src/pages/pt/indexing/tap.mdx index 197d8757b967..79de9a57e6ae 100644 --- a/website/src/pages/pt/indexing/tap.mdx +++ b/website/src/pages/pt/indexing/tap.mdx @@ -45,19 +45,19 @@ Tudo será executado automaticamente enquanto `tap-agent` e `indexer-agent` fore ### Contratos -| Contrato | Mainnet Arbitrum (42161) | Arbitrum Sepolia (421614) | -| ------------------- | -------------------------------------------- | -------------------------------------------- | -| Verificador do TAP | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | -| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | -| Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | +| Contrato | Mainnet Arbitrum (42161) | Arbitrum Sepolia (421614) | +| ------------------------- | -------------------------------------------- | -------------------------------------------- | +| Verificador do TAP | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | ### Porta de Ligação -| Componente | Mainnet Edge and Note (Mainnet Arbitrum) | Testnet do Edge and Node (Arbitrum Sepolia) | -| ----------- | --------------------------------------------- | --------------------------------------------- | -| Remetente | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| Signatários | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| Agregador | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| Componente | Mainnet Edge and Note (Mainnet Arbitrum) | Testnet do Edge and Node (Arbitrum Sepolia) | +| -------------- | --------------------------------------------- | ------------------------------------------------ | +| Remetente | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| Signatários | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Agregador | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### Pré-requisitos From 70af7b7a8ab59f845d226df88604225e51a9628e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:27 -0400 Subject: [PATCH 178/290] New translations tap.mdx (Hindi) --- website/src/pages/hi/indexing/tap.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/website/src/pages/hi/indexing/tap.mdx b/website/src/pages/hi/indexing/tap.mdx index 9aff98fe1eae..bed6a68c4a5d 100644 --- a/website/src/pages/hi/indexing/tap.mdx +++ b/website/src/pages/hi/indexing/tap.mdx @@ -51,13 +51,13 @@ GraphTally allows a sender to make multiple payments to a receiver, **Receipts** | AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | | Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | -### गेटवे +### गेटवे -| घटक | Edge and Node Mainnet (Arbitrum Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | -| ---------------- | --------------------------------------------- | --------------------------------------------- | -| प्रेषक | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| हस्ताक्षरकर्ता | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| संकेन्द्रीयकर्ता | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| घटक | Edge and Node Mainnet (Arbitrum Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | +| ----------------- | --------------------------------------------- | --------------------------------------------- | +| प्रेषक | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| हस्ताक्षरकर्ता | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| संकेन्द्रीयकर्ता | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### आवश्यक शर्तें @@ -117,7 +117,7 @@ operator_mnemonic = "celery smart tip orange scare van steel radio dragon joy al [database] # Indexer घटकों के लिए उपयोग किए जाने वाले Postgres डेटाबेस का URL। वही डेटाबेस -# जिसका उपयोग `indexer-agent` द्वारा किया जाता है। यह अपेक्षित है कि `indexer-agent` +# जिसका उपयोग `indexer-agent` द्वारा किया जाता है। यह अपेक्षित है कि `indexer-agent` #आवश्यक तालिकाएँ बनाएगा। postgres_url = "postgres://postgres@postgres:5432/postgres" @@ -186,7 +186,7 @@ max_amount_willing_to_lose_grt = 20 ### Grafana डैशबोर्ड -आप Grafana Dashboard (https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) डाउनलोड कर सकते हैं और इम्पोर्ट कर सकते हैं। +आप Grafana Dashboard (https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) डाउनलोड कर सकते हैं और इम्पोर्ट कर सकते हैं। ### लॉन्चपैड From 7243823238f45799eebadf3cbeba06a85cc7364a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:39 -0400 Subject: [PATCH 179/290] New translations enums.mdx (Russian) --- website/src/pages/ru/subgraphs/guides/enums.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ru/subgraphs/guides/enums.mdx b/website/src/pages/ru/subgraphs/guides/enums.mdx index 1d696e352f9a..6109eaaae73f 100644 --- a/website/src/pages/ru/subgraphs/guides/enums.mdx +++ b/website/src/pages/ru/subgraphs/guides/enums.mdx @@ -72,7 +72,7 @@ type Token @entity { enum Marketplace { OpenSeaV1 # Представляет случай, когда NFT CryptoCoven торгуется на маркетплейсе OpenSeaV1 OpenSeaV2 # Представляет случай, когда NFT CryptoCoven торгуется на маркетплейсе OpenSeaV2 - SeaPort # Представляет случай, когда NFT CryptoCoven торгуется на маркетплейсе SeaPort + SeaPort # Представляет случай, когда NFT CryptoCoven торгуется на маркетплейсе SeaPort LooksRare # Представляет случай, когда NFT CryptoCoven торгуется на маркетплейсе LooksRare # ...и другие рынки } From 515bf6bfbabd46b2eb6816d2d27fc83be445c853 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:41 -0400 Subject: [PATCH 180/290] New translations enums.mdx (Turkish) --- website/src/pages/tr/subgraphs/guides/enums.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/tr/subgraphs/guides/enums.mdx b/website/src/pages/tr/subgraphs/guides/enums.mdx index 18c3021ed435..8b5ab54177af 100644 --- a/website/src/pages/tr/subgraphs/guides/enums.mdx +++ b/website/src/pages/tr/subgraphs/guides/enums.mdx @@ -92,7 +92,7 @@ Enum'dan pazar yeri adını bir dize olarak almak için bir fonksiyonu şöyle u export function getMarketplaceName(marketplace: Marketplace): string { // Enum değerini bir dizeye eşlemek için if-else ifadelerini kullanma if (marketplace === Marketplace.OpenSeaV1) { - return 'OpenSeaV1' // I Eğer pazar yeri OpenSea ise, onun dize temsilini döndür + return 'OpenSeaV1' // I Eğer pazar yeri OpenSea ise, onun dize temsilini döndür } else if (marketplace === Marketplace.OpenSeaV2) { return 'OpenSeaV2' } else if (marketplace === Marketplace.SeaPort) { From 3712b31d6e17f279277c3001fe01b140c0d97daf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:45 -0400 Subject: [PATCH 181/290] New translations enums.mdx (Hindi) --- website/src/pages/hi/subgraphs/guides/enums.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/hi/subgraphs/guides/enums.mdx b/website/src/pages/hi/subgraphs/guides/enums.mdx index d44418fec528..b4883c3bce8b 100644 --- a/website/src/pages/hi/subgraphs/guides/enums.mdx +++ b/website/src/pages/hi/subgraphs/guides/enums.mdx @@ -68,7 +68,7 @@ Enums प्रकार सुरक्षा प्रदान करते NFTs के व्यापार किए जाने वाले विभिन्न मार्केटप्लेस के लिए enums को परिभाषित करने के लिए, अपने Subgraph स्कीमा में निम्नलिखित का उपयोग करें: ```gql -#मार्केटप्लेस के लिए Enum जो CryptoCoven कॉन्ट्रैक्ट के साथ इंटरएक्टेड हैं (संभवत: ट्रेड/मिंट) +#मार्केटप्लेस के लिए Enum जो CryptoCoven कॉन्ट्रैक्ट के साथ इंटरएक्टेड हैं (संभवत: ट्रेड/मिंट) enum Marketplace { OpenSeaV1 # जब CryptoCoven NFT को इस बाजार में व्यापार किया जाता है OpenSeaV2 # जब CryptoCoven NFT को OpenSeaV2 बाजार में व्यापार किया जाता है From be5803c7acf664bdfa1fe700fff3c69e06e7d61a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:00:51 -0400 Subject: [PATCH 182/290] New translations tap.mdx (French) --- website/src/pages/fr/indexing/tap.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/fr/indexing/tap.mdx b/website/src/pages/fr/indexing/tap.mdx index 68a0b79a2e6f..1986db8769ee 100644 --- a/website/src/pages/fr/indexing/tap.mdx +++ b/website/src/pages/fr/indexing/tap.mdx @@ -45,19 +45,19 @@ Tant que vous exécutez `tap-agent` et `indexer-agent`, tout sera exécuté auto ### Contrats -| Contrat | Mainnet Arbitrum (42161) | Arbitrum Sepolia (421614) | -| --- | --- | --- | -| TAP Verifier | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | -| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | -| Tiers de confiance (Escrow) | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | +| Contrat | Mainnet Arbitrum (42161) | Arbitrum Sepolia (421614) | +| ---------------------------------------- | -------------------------------------------- | -------------------------------------------- | +| TAP Verifier | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Tiers de confiance (Escrow) | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | ### Passerelle (Gateway) -| Composant | Mainnet Node et Edge (Arbitrum Mainnet) | Testnet Node et Edge (Arbitrum Mainnet) | -| ----------- | --------------------------------------------- | --------------------------------------------- | -| Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| Signataires | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| Aggregateur | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| Composant | Mainnet Node et Edge (Arbitrum Mainnet) | Testnet Node et Edge (Arbitrum Mainnet) | +| -------------- | --------------------------------------------- | --------------------------------------------- | +| Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| Signataires | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Aggregateur | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### Prérequis From a9d0804dac95a6b3db13df87571ad91483a332c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:01:19 -0400 Subject: [PATCH 183/290] New translations tap.mdx (Russian) --- website/src/pages/ru/indexing/tap.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/ru/indexing/tap.mdx b/website/src/pages/ru/indexing/tap.mdx index 7703c14853a6..1007b2eaaa9e 100644 --- a/website/src/pages/ru/indexing/tap.mdx +++ b/website/src/pages/ru/indexing/tap.mdx @@ -45,19 +45,19 @@ GraphTally allows a sender to make multiple payments to a receiver, **Receipts** ### Контракты -| Контракт | Arbitrum Mainnet (42161) | Arbitrum Sepolia (421614) | -| ------------------- | -------------------------------------------- | -------------------------------------------- | -| TAP-верификатор | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | -| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | -| Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | +| Контракт | Arbitrum Mainnet (42161) | Arbitrum Sepolia (421614) | +| ---------------------- | -------------------------------------------- | -------------------------------------------- | +| TAP-верификатор | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | ### Шлюз -| Компонент | Edge и Node Mainnet (Arbitrum Mainnet) | Edge и Node Testnet (Arbitrum Sepolia) | -| ----------- | --------------------------------------------- | --------------------------------------------- | -| Отправитель | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| Подписанты | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | -| Агрегатор | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | +| Компонент | Edge и Node Mainnet (Arbitrum Mainnet) | Edge и Node Testnet (Arbitrum Sepolia) | +| --------------- | --------------------------------------------- | --------------------------------------------- | +| Отправитель | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| Подписанты | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Агрегатор | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### Предварительные требования From 8b6977dd0f82c65736f8b3e002220c386b06f92e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:01:26 -0400 Subject: [PATCH 184/290] New translations tap.mdx (Turkish) --- website/src/pages/tr/indexing/tap.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/website/src/pages/tr/indexing/tap.mdx b/website/src/pages/tr/indexing/tap.mdx index d59e66ef4a76..6d1a9ccad7b4 100644 --- a/website/src/pages/tr/indexing/tap.mdx +++ b/website/src/pages/tr/indexing/tap.mdx @@ -45,18 +45,18 @@ Ağ geçidi her sorgu için size veritabanınızda saklanan bir `signed receipt` ### Sözleşmeler -| Sözleşme | Arbitrum Ana Ağı (42161) | Arbitrum Sepolia (421614) | -| ------------------- | -------------------------------------------- | -------------------------------------------- | -| TAP Doğrulayıcı | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | -| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | -| Emanet (Escrow) | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | +| Sözleşme | Arbitrum Ana Ağı (42161) | Arbitrum Sepolia (421614) | +| ---------------------------- | -------------------------------------------- | -------------------------------------------- | +| TAP Doğrulayıcı | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Emanet (Escrow) | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | ### Ağ Geçidi -| Bileşen | Edge and Node Mainnet (Arbitrum Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | -| --- | --- | --- | -| Gönderen | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | -| İmzalayıcılar (Signers) | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Bileşen | Edge and Node Mainnet (Arbitrum Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | +| --------------------------- | --------------------------------------------- | --------------------------------------------- | +| Gönderen | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| İmzalayıcılar (Signers) | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | | Toplulaştırıcı (Aggregator) | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | ### Prerequisites From 086e8d5c6b2a73d66d75a83eb3ad33191557f4bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Mon, 14 Apr 2025 17:01:43 -0400 Subject: [PATCH 185/290] New translations tokenomics.mdx (Hindi) --- website/src/pages/hi/resources/tokenomics.mdx | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/website/src/pages/hi/resources/tokenomics.mdx b/website/src/pages/hi/resources/tokenomics.mdx index ac420f323ab7..00ea0f5b3cef 100644 --- a/website/src/pages/hi/resources/tokenomics.mdx +++ b/website/src/pages/hi/resources/tokenomics.mdx @@ -6,7 +6,7 @@ description: The Graph Network को शक्तिशाली टोकन ## Overview -The Graph एक **decentralized protocol** है, जो **blockchain data** तक आसान पहुँच प्रदान करता है। यह **blockchain data** को उसी तरह **index** करता है, जैसे **Google** वेब को **index** करता है। अगर आपने किसी ऐसे **dapp** का उपयोग किया है जो किसी **Subgraph** से डेटा प्राप्त करता है, तो आपने संभवतः **The Graph** के साथ इंटरैक्ट किया है। आज, **Web3 ecosystem** में हजारों [लोकप्रिय dapps](https://thegraph.com/explorer) **The Graph** का उपयोग कर रहे हैं। +The Graph एक **decentralized protocol** है, जो **blockchain data** तक आसान पहुँच प्रदान करता है। यह **blockchain data** को उसी तरह **index** करता है, जैसे **Google** वेब को **index** करता है। अगर आपने किसी ऐसे **dapp** का उपयोग किया है जो किसी **Subgraph** से डेटा प्राप्त करता है, तो आपने संभवतः **The Graph** के साथ इंटरैक्ट किया है। आज, **Web3 ecosystem** में हजारों [लोकप्रिय dapps](https://thegraph.com/explorer) **The Graph** का उपयोग कर रहे हैं। ## विशिष्टताएँ @@ -36,7 +36,7 @@ The Graph ब्लॉकचेन डेटा को अधिक सुलभ ## Delegator(निष्क्रिय रूप से GRT कमाएं) -**Indexers** को **Delegators** द्वारा **GRT** डेलिगेट किया जाता है, जिससे नेटवर्क पर Subgraphs में Indexer की **stake** बढ़ती है। इसके बदले में, **Delegators** को Indexer से मिलने वाले कुल **query fees** और **indexing rewards** का एक निश्चित प्रतिशत मिलता है। हर **Indexer** स्वतंत्र रूप से तय करता है कि वह **Delegators** को कितना रिवार्ड देगा, जिससे **Indexers** के बीच **Delegators** को आकर्षित करने की प्रतिस्पर्धा बनी रहती है। अधिकांश **Indexers** सालाना **9-12%** रिटर्न ऑफर करते हैं। +**Indexers** को **Delegators** द्वारा **GRT** डेलिगेट किया जाता है, जिससे नेटवर्क पर Subgraphs में Indexer की **stake** बढ़ती है। इसके बदले में, **Delegators** को Indexer से मिलने वाले कुल **query fees** और **indexing rewards** का एक निश्चित प्रतिशत मिलता है। हर **Indexer** स्वतंत्र रूप से तय करता है कि वह **Delegators** को कितना रिवार्ड देगा, जिससे **Indexers** के बीच **Delegators** को आकर्षित करने की प्रतिस्पर्धा बनी रहती है। अधिकांश **Indexers** सालाना **9-12%** रिटर्न ऑफर करते हैं। यदि कोई Delegator 15k GRT को किसी ऐसे Indexer को डेलिगेट करता है जो 10% की पेशकश कर रहा है, तो Delegator को वार्षिक रूप से ~1,500 GRT का इनाम प्राप्त होगा। @@ -46,7 +46,7 @@ The Graph ब्लॉकचेन डेटा को अधिक सुलभ ## Curators (GRT कमाएं) -**Curators** उच्च-गुणवत्ता वाले **Subgraphs** की पहचान करते हैं और उन्हें **"curate"** करते हैं (अर्थात, उन पर **GRT signal** करते हैं) ताकि **curation shares** कमा सकें। ये **curation shares** उस **Subgraph** द्वारा उत्पन्न सभी भविष्य की **query fees** का एक निश्चित प्रतिशत सुनिश्चित करते हैं। हालाँकि कोई भी स्वतंत्र नेटवर्क प्रतिभागी **Curator** बन सकता है, आमतौर पर **Subgraph developers** अपने स्वयं के **Subgraphs** के पहले **Curators** होते हैं, क्योंकि वे सुनिश्चित करना चाहते हैं कि उनका **Subgraph indexed** हो। +**Curators** उच्च-गुणवत्ता वाले **Subgraphs** की पहचान करते हैं और उन्हें **"curate"** करते हैं (अर्थात, उन पर **GRT signal** करते हैं) ताकि **curation shares** कमा सकें। ये **curation shares** उस **Subgraph** द्वारा उत्पन्न सभी भविष्य की **query fees** का एक निश्चित प्रतिशत सुनिश्चित करते हैं। हालाँकि कोई भी स्वतंत्र नेटवर्क प्रतिभागी **Curator** बन सकता है, आमतौर पर **Subgraph developers** अपने स्वयं के **Subgraphs** के पहले **Curators** होते हैं, क्योंकि वे सुनिश्चित करना चाहते हैं कि उनका **Subgraph indexed** हो। **Subgraph developers** को सलाह दी जाती है कि वे अपने **Subgraph** को कम से कम **3,000 GRT** के साथ **curate** करें। हालांकि, यह संख्या **network activity** और **community participation** के अनुसार बदल सकती है। @@ -54,11 +54,11 @@ The Graph ब्लॉकचेन डेटा को अधिक सुलभ ## डेवलपर्स -**Developers** **Subgraphs** बनाते हैं और उन्हें **query** करके **blockchain data** प्राप्त करते हैं। चूंकि **Subgraphs** **open source** होते हैं, **developers** मौजूदा **Subgraphs** को **query** करके अपने **dapps** में **blockchain data** लोड कर सकते हैं। **Developers** द्वारा किए गए **queries** के लिए **GRT** में भुगतान किया जाता है, जो नेटवर्क प्रतिभागियों के बीच वितरित किया जाता है। +**Developers** **Subgraphs** बनाते हैं और उन्हें **query** करके **blockchain data** प्राप्त करते हैं। चूंकि **Subgraphs** **open source** होते हैं, **developers** मौजूदा **Subgraphs** को **query** करके अपने **dapps** में **blockchain data** लोड कर सकते हैं। **Developers** द्वारा किए गए **queries** के लिए **GRT** में भुगतान किया जाता है, जो नेटवर्क प्रतिभागियों के बीच वितरित किया जाता है। ### Creating a Subgraph -**Developers** **[Subgraph create](/developing/creating-a-subgraph/)** करके **blockchain** पर डेटा **index** कर सकते हैं। **Subgraphs** यह निर्देश देते हैं कि **Indexers** को कौन सा डेटा **consumers** को उपलब्ध कराना चाहिए। +**Developers** **[Subgraph create](/developing/creating-a-subgraph/)** करके **blockchain** पर डेटा **index** कर सकते हैं। **Subgraphs** यह निर्देश देते हैं कि **Indexers** को कौन सा डेटा **consumers** को उपलब्ध कराना चाहिए। जब **developers** अपना **Subgraph** बना और टेस्ट कर लेते हैं, तो वे इसे **The Graph** के **decentralized network** पर **[publish](/subgraphs/developing/publishing/publishing-a-subgraph/)** कर सकते हैं। @@ -92,9 +92,8 @@ Indexers दो तरीकों से GRT रिवार्ड्स कम **प्रारंभिक टोकन आपूर्ति** 10 बिलियन **GRT** है, और **Indexers** को **Subgraphs** पर **stake allocate** करने के लिए प्रति वर्ष **3%** नई **GRT issuance** का लक्ष्य रखा गया है। इसका मतलब है कि हर साल **Indexers** के योगदान के लिए नए टोकन जारी किए जाएंगे, जिससे कुल **GRT आपूर्ति** 3% बढ़ेगी। -The Graph में नए टोकन **issuance** को संतुलित करने के लिए कई **burning mechanisms** शामिल किए गए हैं। सालाना लगभग **1% GRT supply** विभिन्न नेटवर्क गतिविधियों के माध्यम से **burn** हो जाती है, और यह संख्या नेटवर्क की वृद्धि के साथ बढ़ रही है। ये **burning mechanisms** शामिल हैं: - **0.5% Delegation Tax**: जब कोई **Delegator** किसी **Indexer** को **GRT** डेलीगेट करता है। - -- **1% Curation Tax**: जब **Curators** किसी **Subgraph** पर **GRT signal** करते हैं। +The Graph में नए टोकन **issuance** को संतुलित करने के लिए कई **burning mechanisms** शामिल किए गए हैं। सालाना लगभग **1% GRT supply** विभिन्न नेटवर्क गतिविधियों के माध्यम से **burn** हो जाती है, और यह संख्या नेटवर्क की वृद्धि के साथ बढ़ रही है। ये **burning mechanisms** शामिल हैं: - **0.5% Delegation Tax**: जब कोई **Delegator** किसी **Indexer** को **GRT** डेलीगेट करता है। +- **1% Curation Tax**: जब **Curators** किसी **Subgraph** पर **GRT signal** करते हैं। - **1% Query Fees Burn**: जब **ब्लॉकचेन डेटा** के लिए **queries** की जाती हैं। ![कुल जले हुए GRT](/img/total-burned-grt.jpeg) @@ -103,4 +102,4 @@ The Graph में नए टोकन **issuance** को संतुलि ## प्रोटोकॉल में सुधार करना -The Graph Network निरंतर विकसित हो रहा है और प्रोटोकॉल की आर्थिक संरचना में सुधार किए जा रहे हैं ताकि सभी नेटवर्क प्रतिभागियों को सर्वोत्तम अनुभव मिल सके। The Graph Council प्रोटोकॉल परिवर्तनों की निगरानी करता है और समुदाय के सदस्यों को भाग लेने के लिए प्रोत्साहित किया जाता है। प्रोटोकॉल सुधारों में शामिल हों [The Graph Forum] (https://forum.thegraph.com/) में। + The Graph Network निरंतर विकसित हो रहा है और प्रोटोकॉल की आर्थिक संरचना में सुधार किए जा रहे हैं ताकि सभी नेटवर्क प्रतिभागियों को सर्वोत्तम अनुभव मिल सके। The Graph Council प्रोटोकॉल परिवर्तनों की निगरानी करता है और समुदाय के सदस्यों को भाग लेने के लिए प्रोत्साहित किया जाता है। प्रोटोकॉल सुधारों में शामिल हों [The Graph Forum] (https://forum.thegraph.com/) में। From b64cfe7477a870fdd63509668717dd22c228bcad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:41:57 -0400 Subject: [PATCH 186/290] New translations quick-start.mdx (Japanese) --- website/src/pages/ja/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ja/substreams/quick-start.mdx b/website/src/pages/ja/substreams/quick-start.mdx index 6bbe99168657..48b581eedec3 100644 --- a/website/src/pages/ja/substreams/quick-start.mdx +++ b/website/src/pages/ja/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 0540caebc409303698a96597587ad9c88f4059ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:41:58 -0400 Subject: [PATCH 187/290] New translations quick-start.mdx (Russian) --- website/src/pages/ru/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ru/substreams/quick-start.mdx b/website/src/pages/ru/substreams/quick-start.mdx index 922ee9c9e2db..6a38efbd0e2b 100644 --- a/website/src/pages/ru/substreams/quick-start.mdx +++ b/website/src/pages/ru/substreams/quick-start.mdx @@ -31,6 +31,7 @@ sidebarTitle: Быстрый старт - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) Чтобы создать и оптимизировать свои Субпотоки с нуля, используйте минимальный путь внутри [контейнера для разработки](/substreams/developing/dev-container/). From cd9ef7cec2ad8beb0e8af4b95a43592b20595b4b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:00 -0400 Subject: [PATCH 188/290] New translations quick-start.mdx (Turkish) --- website/src/pages/tr/substreams/quick-start.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/src/pages/tr/substreams/quick-start.mdx b/website/src/pages/tr/substreams/quick-start.mdx index 7ff97c69968b..1695af116415 100644 --- a/website/src/pages/tr/substreams/quick-start.mdx +++ b/website/src/pages/tr/substreams/quick-start.mdx @@ -1,5 +1,5 @@ --- -title: 'Substreams: Hızlı Başlangıç' +title: "Substreams: Hızlı Başlangıç" sidebarTitle: Hızlı Başlangıç --- @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 763128a1bde9ffde6668261f884656ca691b8fb6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:01 -0400 Subject: [PATCH 189/290] New translations quick-start.mdx (French) --- website/src/pages/fr/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/fr/substreams/quick-start.mdx b/website/src/pages/fr/substreams/quick-start.mdx index 75da28206cb5..763e73918164 100644 --- a/website/src/pages/fr/substreams/quick-start.mdx +++ b/website/src/pages/fr/substreams/quick-start.mdx @@ -31,6 +31,7 @@ Si vous ne trouvez pas de package Substreams qui réponde à vos besoins spécif - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) Pour construire et optimiser vos Substreams à partir de zéro, utilisez le chemin minimal dans le [conteneur de développement](/substreams/developing/dev-container/). From 332220bfcde5ac00399b78db90ec578b47e7585e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:03 -0400 Subject: [PATCH 190/290] New translations quick-start.mdx (Romanian) --- website/src/pages/ro/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ro/substreams/quick-start.mdx b/website/src/pages/ro/substreams/quick-start.mdx index b5eec572b00a..acd3029d1376 100644 --- a/website/src/pages/ro/substreams/quick-start.mdx +++ b/website/src/pages/ro/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From c36c1048ea4e2217f639bee951aec0be60144234 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:05 -0400 Subject: [PATCH 191/290] New translations quick-start.mdx (Spanish) --- website/src/pages/es/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/es/substreams/quick-start.mdx b/website/src/pages/es/substreams/quick-start.mdx index 4e6ec88c0c0e..44847485b432 100644 --- a/website/src/pages/es/substreams/quick-start.mdx +++ b/website/src/pages/es/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 4ba5cd1b2bb33b8a258b7a71515d2bffc9fe78b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:07 -0400 Subject: [PATCH 192/290] New translations quick-start.mdx (Arabic) --- website/src/pages/ar/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ar/substreams/quick-start.mdx b/website/src/pages/ar/substreams/quick-start.mdx index 7428d67bf4ff..8698cc7102e3 100644 --- a/website/src/pages/ar/substreams/quick-start.mdx +++ b/website/src/pages/ar/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From d18cc610de82c051ecb7cbebc897825938e45964 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:08 -0400 Subject: [PATCH 193/290] New translations quick-start.mdx (Czech) --- website/src/pages/cs/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/cs/substreams/quick-start.mdx b/website/src/pages/cs/substreams/quick-start.mdx index 50a16d470cfe..ecf32732ba24 100644 --- a/website/src/pages/cs/substreams/quick-start.mdx +++ b/website/src/pages/cs/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 3a47aa79a30de42a6cb13df34aa45f6eff680571 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:09 -0400 Subject: [PATCH 194/290] New translations quick-start.mdx (German) --- website/src/pages/de/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/de/substreams/quick-start.mdx b/website/src/pages/de/substreams/quick-start.mdx index 6d82be0f8ac1..6c03ea9762a7 100644 --- a/website/src/pages/de/substreams/quick-start.mdx +++ b/website/src/pages/de/substreams/quick-start.mdx @@ -31,6 +31,7 @@ Wenn Sie kein Substreams-Paket finden können, das Ihren speziellen Anforderunge - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) Um Ihre Substreams von Anfang an zu erstellen und zu optimieren, verwenden Sie den minimalen Pfad innerhalb des [Dev Containers](/substreams/developing/dev-container/). From 829be8480505071165f2a099b36e845ebc4f14b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:11 -0400 Subject: [PATCH 195/290] New translations quick-start.mdx (Italian) --- website/src/pages/it/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/it/substreams/quick-start.mdx b/website/src/pages/it/substreams/quick-start.mdx index a4c82cb797d9..0f1eb0783b99 100644 --- a/website/src/pages/it/substreams/quick-start.mdx +++ b/website/src/pages/it/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 7743382444c3138451de900ef1cf8cbe41a69d21 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:13 -0400 Subject: [PATCH 196/290] New translations quick-start.mdx (Korean) --- website/src/pages/ko/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ko/substreams/quick-start.mdx b/website/src/pages/ko/substreams/quick-start.mdx index b5eec572b00a..acd3029d1376 100644 --- a/website/src/pages/ko/substreams/quick-start.mdx +++ b/website/src/pages/ko/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 4beaa2296cd18780e59697add8782676fb497e8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:15 -0400 Subject: [PATCH 197/290] New translations quick-start.mdx (Dutch) --- website/src/pages/nl/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/nl/substreams/quick-start.mdx b/website/src/pages/nl/substreams/quick-start.mdx index eaec3b713bfe..18abfcfda3a1 100644 --- a/website/src/pages/nl/substreams/quick-start.mdx +++ b/website/src/pages/nl/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 70e0f0a2a17fcff9e835cc52d9bcda20a8906ac7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:16 -0400 Subject: [PATCH 198/290] New translations quick-start.mdx (Polish) --- website/src/pages/pl/substreams/quick-start.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/src/pages/pl/substreams/quick-start.mdx b/website/src/pages/pl/substreams/quick-start.mdx index 96846fccaf05..d95fd2637fbd 100644 --- a/website/src/pages/pl/substreams/quick-start.mdx +++ b/website/src/pages/pl/substreams/quick-start.mdx @@ -1,6 +1,6 @@ --- title: Substreams Quick Start -sidebarTitle: ' Na start' +sidebarTitle: " Na start" --- Discover how to utilize ready-to-use substream packages or develop your own. @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 2077ca53596d38d7e9e2caea06df9b1d7ef288b6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:18 -0400 Subject: [PATCH 199/290] New translations quick-start.mdx (Portuguese) --- website/src/pages/pt/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/pt/substreams/quick-start.mdx b/website/src/pages/pt/substreams/quick-start.mdx index 9ee566780134..1a5c15ce76a4 100644 --- a/website/src/pages/pt/substreams/quick-start.mdx +++ b/website/src/pages/pt/substreams/quick-start.mdx @@ -31,6 +31,7 @@ Se não encontrar um pacote do Substreams que atenda às suas necessidades espec - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) Para construir e otimizar os seus Substreams do zero, use o caminho mínimo dentro do [Dev Container](/substreams/developing/dev-container/). From 299f2f138c7575ab1cb3a085d8338a267c9a4382 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:20 -0400 Subject: [PATCH 200/290] New translations quick-start.mdx (Swedish) --- website/src/pages/sv/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/sv/substreams/quick-start.mdx b/website/src/pages/sv/substreams/quick-start.mdx index 8a1d453f56a9..8a547799323a 100644 --- a/website/src/pages/sv/substreams/quick-start.mdx +++ b/website/src/pages/sv/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From b53a340d086d7818058c7c0b3f85dcadf02f668b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:22 -0400 Subject: [PATCH 201/290] New translations quick-start.mdx (Ukrainian) --- website/src/pages/uk/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/uk/substreams/quick-start.mdx b/website/src/pages/uk/substreams/quick-start.mdx index 056c7391e15c..74ddbc73a3de 100644 --- a/website/src/pages/uk/substreams/quick-start.mdx +++ b/website/src/pages/uk/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From d5446a14ae06808c8797a304f0bf1cb8c7a8bb89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:24 -0400 Subject: [PATCH 202/290] New translations quick-start.mdx (Chinese Simplified) --- website/src/pages/zh/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/zh/substreams/quick-start.mdx b/website/src/pages/zh/substreams/quick-start.mdx index be4fc19302f3..7826c8b747a7 100644 --- a/website/src/pages/zh/substreams/quick-start.mdx +++ b/website/src/pages/zh/substreams/quick-start.mdx @@ -31,6 +31,7 @@ sidebarTitle: 快速开始 - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) 若要从零构建和优化您的子流，请使用 [Dev容器](/substreams/developing/dev-container/)中的最小路径。 From a8f250b45487fb4a592488806d7b1bd0bce499b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:26 -0400 Subject: [PATCH 203/290] New translations quick-start.mdx (Urdu (Pakistan)) --- website/src/pages/ur/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/ur/substreams/quick-start.mdx b/website/src/pages/ur/substreams/quick-start.mdx index de7572a6bc59..a8a3a54ddbab 100644 --- a/website/src/pages/ur/substreams/quick-start.mdx +++ b/website/src/pages/ur/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From e020e378dd69c66344893336c1cc079420bb94ae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:27 -0400 Subject: [PATCH 204/290] New translations quick-start.mdx (Vietnamese) --- website/src/pages/vi/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/vi/substreams/quick-start.mdx b/website/src/pages/vi/substreams/quick-start.mdx index bca91aa19452..f97dedc8c547 100644 --- a/website/src/pages/vi/substreams/quick-start.mdx +++ b/website/src/pages/vi/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 29dd5097c05792f1ac2432e992d3f42a7948985a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:29 -0400 Subject: [PATCH 205/290] New translations quick-start.mdx (Marathi) --- website/src/pages/mr/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/mr/substreams/quick-start.mdx b/website/src/pages/mr/substreams/quick-start.mdx index a2f7e3e938bd..3b9ae824dd9b 100644 --- a/website/src/pages/mr/substreams/quick-start.mdx +++ b/website/src/pages/mr/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From 8daa2f25b407a69bfbe8ed43c5a0e2709f6c8222 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 15 Apr 2025 17:42:30 -0400 Subject: [PATCH 206/290] New translations quick-start.mdx (Hindi) --- website/src/pages/hi/substreams/quick-start.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/src/pages/hi/substreams/quick-start.mdx b/website/src/pages/hi/substreams/quick-start.mdx index c4a0d5be8e23..d775f2f6dc57 100644 --- a/website/src/pages/hi/substreams/quick-start.mdx +++ b/website/src/pages/hi/substreams/quick-start.mdx @@ -31,6 +31,7 @@ If you can't find a Substreams package that meets your specific needs, you can d - [Starknet](https://docs.substreams.dev/tutorials/intro-to-tutorials/starknet) - [Injective](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/injective) - [MANTRA](https://docs.substreams.dev/tutorials/intro-to-tutorials/on-cosmos/mantra) +- [Stellar](https://docs.substreams.dev/tutorials/intro-to-tutorials/stellar) To build and optimize your Substreams from zero, use the minimal path within the [Dev Container](/substreams/developing/dev-container/). From b4dc544c97eedc81b857111258d3293b021beb7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:19 -0400 Subject: [PATCH 207/290] New translations using-subgraph-studio.mdx (Romanian) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx index 77d10212c770..d44f9b375203 100644 --- a/website/src/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 99cad784ce0e42d3ceb8dd9b544b9789e9d6a4f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:20 -0400 Subject: [PATCH 208/290] New translations using-subgraph-studio.mdx (French) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 4582f8643eb7..e1a4559b28bf 100644 --- a/website/src/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Une fois que vous êtes prêt, vous pouvez déployer votre Subgraph dans Subgraph Studio. > Le déploiement d'un Subgraph à l'aide de la CLI le transfère dans le Studio, où vous pouvez le tester et mettre à jour les métadonnées. Cette action ne publie pas votre Subgraph sur le réseau décentralisé. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Utilisez la commande CLI suivante pour déployer votre Subgraph : @@ -104,6 +106,8 @@ Après avoir exécuté cette commande, la CLI demandera une étiquette de versio Après le déploiement, vous pouvez tester votre Subgraph (soit dans Subgraph Studio, soit dans votre propre application, avec l'URL de requête de déploiement), déployer une autre version, mettre à jour les métadonnées et publier sur [Graph Explorer](https://thegraph.com/explorer) lorsque vous êtes prêt. +> **Note**: The development query URL is limited to 3,000 queries per day. + Utilisez Subgraph Studio pour vérifier les journaux du tableau de bord et rechercher les erreurs éventuelles de votre Subgraph. ## Publiez votre subgraph From 0d7c6bb63d788fcde4ec263739da1413b52c4faa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:21 -0400 Subject: [PATCH 209/290] New translations using-subgraph-studio.mdx (Spanish) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx index 29eed7358005..82b865a94db2 100644 --- a/website/src/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 801dbb0b9362927742f45f5aee35ffc7cb774fd4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:23 -0400 Subject: [PATCH 210/290] New translations using-subgraph-studio.mdx (Arabic) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx index 1e0826bfe148..15ac3901d9fb 100644 --- a/website/src/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 7b93ecc618ffd3a088ebd2872a25817187544654 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:24 -0400 Subject: [PATCH 211/290] New translations using-subgraph-studio.mdx (Czech) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx index 14be0175123c..01056c092ca2 100644 --- a/website/src/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From cb48e0a545a3f48ce7417c552efb2f6d4363822e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:25 -0400 Subject: [PATCH 212/290] New translations using-subgraph-studio.mdx (German) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx index 4f784b4304b8..2428cc8eca51 100644 --- a/website/src/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Sobald Sie bereit sind, können Sie Ihren Subgraph in Subgraph Studio bereitstellen. > Wenn Sie einen Subgraphen mit der Befehlszeilenschnittstelle bereitstellen, wird er in das Studio übertragen, wo Sie ihn testen und die Metadaten aktualisieren können. Durch diese Aktion wird Ihr Subgraph nicht im dezentralen Netzwerk veröffentlicht. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Verwenden Sie den folgenden CLI-Befehl, um Ihren Subgraph zu verteilen: @@ -104,6 +106,8 @@ Nach der Ausführung dieses Befehls wird die CLI nach einer Versionsbezeichnung Nach dem Deployment können Sie Ihren Subgraph testen (entweder in Subgraph Studio oder in Ihrer eigenen Anwendung, mit der Deployment-Query-URL), eine weitere Version deployen, die Metadaten aktualisieren und im [Graph Explorer](https://thegraph.com/explorer) veröffentlichen, wenn Sie bereit sind. +> **Note**: The development query URL is limited to 3,000 queries per day. + Verwenden Sie Subgraph Studio, um die Protokolle auf dem Dashboard zu überprüfen und nach Fehlern in Ihrem Subgraphen zu suchen. ## Veröffentlichen Sie Ihren Subgraph From 2cd077e8b28250cda820eac6495f08f8ee9b1025 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:26 -0400 Subject: [PATCH 213/290] New translations using-subgraph-studio.mdx (Italian) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3a07d7d50b24..f1e69207ee72 100644 --- a/website/src/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 2e404e65802990bae3f1865d55886d6b1c152051 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:27 -0400 Subject: [PATCH 214/290] New translations using-subgraph-studio.mdx (Japanese) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx index 4e8503e208e4..3b4a1ecf9ba7 100644 --- a/website/src/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From c994a1f51476d0811cc76cc65fab838e55bd7632 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:29 -0400 Subject: [PATCH 215/290] New translations using-subgraph-studio.mdx (Korean) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx index 77d10212c770..d44f9b375203 100644 --- a/website/src/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From e05d1399045dbc1cb992c945e8d85f1f0ab39faf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:30 -0400 Subject: [PATCH 216/290] New translations using-subgraph-studio.mdx (Dutch) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx index 370e428284cc..c64fab1db15e 100644 --- a/website/src/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From ae733c0fe5f5523cd4ecfb65dd8d4da7d503b1f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:31 -0400 Subject: [PATCH 217/290] New translations using-subgraph-studio.mdx (Polish) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx index c21ff6dc2358..cd107113c9fd 100644 --- a/website/src/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From bda1fdef2e75b176084d066f8f02f14acdbb91f5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:32 -0400 Subject: [PATCH 218/290] New translations using-subgraph-studio.mdx (Portuguese) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx index 5a8e4fb9f905..5ba582a0ab0c 100644 --- a/website/src/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ Após executar este comando, a CLI solicitará um número de versão. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Edite o Seu Subgraph From b1069167e8141b63878f6e657971b93c013c41d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:33 -0400 Subject: [PATCH 219/290] New translations using-subgraph-studio.mdx (Russian) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3ff9c8594763..9e6a7496d87c 100644 --- a/website/src/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ graph deploy After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Публикация Вашего субграфа From f09d135c26adedce81e65733929d7159b3dfb5cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:35 -0400 Subject: [PATCH 220/290] New translations using-subgraph-studio.mdx (Swedish) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx index dc1facd6d5cb..0afc63760767 100644 --- a/website/src/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From d7f21bae673c6d5bb113b6c16a887b5b01b688a1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:36 -0400 Subject: [PATCH 221/290] New translations using-subgraph-studio.mdx (Turkish) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx index a4e8ca41d951..caa7b1cc5a3f 100644 --- a/website/src/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ Bu komutu çalıştırdıktan sonra CLI sizden bir sürüm etiketi isteyecektir. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Subgraph’inizi Yayımlama From 6356f2f4ebb58df97c97432738458ae6883f8562 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:37 -0400 Subject: [PATCH 222/290] New translations using-subgraph-studio.mdx (Ukrainian) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx index 2b4c1c11efa0..a3ebd8c532fc 100644 --- a/website/src/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 34b5907aaf92127e58d807acb9fea38a6ec81332 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:38 -0400 Subject: [PATCH 223/290] New translations using-subgraph-studio.mdx (Chinese Simplified) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx index 889dbf99a4a8..f0f956e93dea 100644 --- a/website/src/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth 一旦你准备好了，你可以将你的子图部署到子图工作室。 > 部署一个 CLI 的子图，推送它到工作室，在那里你可以测试它并更新元数据。 此操作不会将你的子图发布到去中心化的网络。 +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. 使用下面的 CLI 命令来部署您的子图： @@ -104,6 +106,8 @@ graph deploy 部署后，你可以测试你的子图(在SubgraStudio或在你自己的应用中，使用部署查询 URL)， 部署另一个版本，更新元数据，并在你准备就绪时发布到 [Graph Explorer](https://thegraph.com/explorer)。 +> **Note**: The development query URL is limited to 3,000 queries per day. + 使用子图工作室检查仪表板上的日志，并查找您的子图中的任何错误。 ## 发布子图 From 806d1283bd5fdf70b929c39e9493ce59a93f6abb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:39 -0400 Subject: [PATCH 224/290] New translations using-subgraph-studio.mdx (Urdu (Pakistan)) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx index f41499fd9c51..741771522fd9 100644 --- a/website/src/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From fe25695044a684ac51725792b9501a487e6bf075 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:40 -0400 Subject: [PATCH 225/290] New translations using-subgraph-studio.mdx (Vietnamese) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx index 8e89b2999d96..6c1cd5654231 100644 --- a/website/src/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 49fffcd2d7543a36701ece35afa6cbc0531c128f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:41 -0400 Subject: [PATCH 226/290] New translations using-subgraph-studio.mdx (Marathi) --- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 2319974d45ed..e07a0f3d1531 100644 --- a/website/src/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label. After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## Publish Your Subgraph From 320eff7c9d3b0976d8a2aea47f48f18d9e2e1826 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 16 Apr 2025 16:38:43 -0400 Subject: [PATCH 227/290] New translations using-subgraph-studio.mdx (Hindi) --- .../developing/deploying/using-subgraph-studio.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/src/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx index eab335f08623..e4a38c427323 100644 --- a/website/src/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/src/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -25,7 +25,7 @@ In Subgraph Studio,आप निम Deploy करने से पहले, आपको The Graph CLI इंस्टॉल करना होगा। -आपको The Graph CLI का उपयोग करने के लिए Node.js(https://nodejs.org/) और आपकी पसंद का पैकेज मैनेजर (npm, yarn या pnpm) स्थापित होना चाहिए। सबसे हालिया (https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI संस्करण की जांच करें। +आपको The Graph CLI का उपयोग करने के लिए Node.js(https://nodejs.org/) और आपकी पसंद का पैकेज मैनेजर (npm, yarn या pnpm) स्थापित होना चाहिए। सबसे हालिया (https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI संस्करण की जांच करें। ### इंस्टॉल करें 'yarn' के साथ @@ -88,6 +88,8 @@ graph auth Once you are ready, you can deploy your Subgraph to Subgraph Studio. > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network. +> +> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones. Use the following CLI command to deploy your Subgraph: @@ -104,6 +106,8 @@ graph deploy After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready. +> **Note**: The development query URL is limited to 3,000 queries per day. + Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph. ## अपने Subgraph को प्रकाशित करें From 6b1dd07d130d63fc19e4de3e228c829aba26c71e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:33 -0400 Subject: [PATCH 228/290] New translations quick-start.mdx (Romanian) --- website/src/pages/ro/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ro/token-api/quick-start.mdx b/website/src/pages/ro/token-api/quick-start.mdx index ef67bed88a5d..e49256d29a6d 100644 --- a/website/src/pages/ro/token-api/quick-start.mdx +++ b/website/src/pages/ro/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Quick Start The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 06c2fef117eac6833f4925d7b6eda1d8bae3a7a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:34 -0400 Subject: [PATCH 229/290] New translations quick-start.mdx (French) --- website/src/pages/fr/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/fr/token-api/quick-start.mdx b/website/src/pages/fr/token-api/quick-start.mdx index 40452d9f419a..6ab65ce4c573 100644 --- a/website/src/pages/fr/token-api/quick-start.mdx +++ b/website/src/pages/fr/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Démarrage rapide The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prérequis From e8cde648af5ec192686c4ef862826dfc4e292e2b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:36 -0400 Subject: [PATCH 230/290] New translations quick-start.mdx (Spanish) --- website/src/pages/es/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/es/token-api/quick-start.mdx b/website/src/pages/es/token-api/quick-start.mdx index 1af940b5b68f..74c1089a3314 100644 --- a/website/src/pages/es/token-api/quick-start.mdx +++ b/website/src/pages/es/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Comienzo Rapido The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 0c982c33bd4684a780bca891bb24d4fc2eb9a90e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:37 -0400 Subject: [PATCH 231/290] New translations quick-start.mdx (Arabic) --- website/src/pages/ar/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ar/token-api/quick-start.mdx b/website/src/pages/ar/token-api/quick-start.mdx index ff1a58015fc0..139c735421a8 100644 --- a/website/src/pages/ar/token-api/quick-start.mdx +++ b/website/src/pages/ar/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: بداية سريعة The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From ae23eedc6f16af4177f2dd043a73de1458af6511 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:38 -0400 Subject: [PATCH 232/290] New translations quick-start.mdx (Czech) --- website/src/pages/cs/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/cs/token-api/quick-start.mdx b/website/src/pages/cs/token-api/quick-start.mdx index 454ffd30b02f..caadce5531e1 100644 --- a/website/src/pages/cs/token-api/quick-start.mdx +++ b/website/src/pages/cs/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Rychlé spuštění The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From ae64e9b9d06b51653b14e945397ab8465eecfadf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:40 -0400 Subject: [PATCH 233/290] New translations quick-start.mdx (German) --- website/src/pages/de/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/de/token-api/quick-start.mdx b/website/src/pages/de/token-api/quick-start.mdx index b4074258c581..489da5b14760 100644 --- a/website/src/pages/de/token-api/quick-start.mdx +++ b/website/src/pages/de/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Schnellstart The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Voraussetzungen From 34e41fcff91bd821ca5889873e812d9b646986fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:41 -0400 Subject: [PATCH 234/290] New translations quick-start.mdx (Italian) --- website/src/pages/it/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/it/token-api/quick-start.mdx b/website/src/pages/it/token-api/quick-start.mdx index ef67bed88a5d..e49256d29a6d 100644 --- a/website/src/pages/it/token-api/quick-start.mdx +++ b/website/src/pages/it/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Quick Start The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 8ffcec0a6f0c6b92ecefe8f35fc99d6e753ad074 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:42 -0400 Subject: [PATCH 235/290] New translations quick-start.mdx (Japanese) --- website/src/pages/ja/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ja/token-api/quick-start.mdx b/website/src/pages/ja/token-api/quick-start.mdx index 059a2f43984d..494ca60a4c1f 100644 --- a/website/src/pages/ja/token-api/quick-start.mdx +++ b/website/src/pages/ja/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: クイックスタート The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 3686d3acf6a0d6c937329877c7a152aa0b642380 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:44 -0400 Subject: [PATCH 236/290] New translations quick-start.mdx (Korean) --- website/src/pages/ko/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ko/token-api/quick-start.mdx b/website/src/pages/ko/token-api/quick-start.mdx index ef67bed88a5d..e49256d29a6d 100644 --- a/website/src/pages/ko/token-api/quick-start.mdx +++ b/website/src/pages/ko/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Quick Start The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 6453bde23b611c36d499850cacfb3ad6d0a6f436 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:45 -0400 Subject: [PATCH 237/290] New translations quick-start.mdx (Dutch) --- website/src/pages/nl/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/nl/token-api/quick-start.mdx b/website/src/pages/nl/token-api/quick-start.mdx index b2c498a85f80..276fcc065ba3 100644 --- a/website/src/pages/nl/token-api/quick-start.mdx +++ b/website/src/pages/nl/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Snelle Start The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From bbcf52d8558e262be868de574dfa5597a4408502 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:46 -0400 Subject: [PATCH 238/290] New translations quick-start.mdx (Polish) --- website/src/pages/pl/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/pl/token-api/quick-start.mdx b/website/src/pages/pl/token-api/quick-start.mdx index 20663af633f4..98ed4f3fd724 100644 --- a/website/src/pages/pl/token-api/quick-start.mdx +++ b/website/src/pages/pl/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: " Na start" The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From 421e72fbe421ce2eecb7bcfa38f400f0a99eacc3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:48 -0400 Subject: [PATCH 239/290] New translations quick-start.mdx (Portuguese) --- website/src/pages/pt/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/pt/token-api/quick-start.mdx b/website/src/pages/pt/token-api/quick-start.mdx index 6ffc93937703..fe1907483c23 100644 --- a/website/src/pages/pt/token-api/quick-start.mdx +++ b/website/src/pages/pt/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Começo Rápido The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Pré-requisitos From d4f07e922005da9d09c1a15b5b33d234acdd1e8b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:49 -0400 Subject: [PATCH 240/290] New translations quick-start.mdx (Russian) --- website/src/pages/ru/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ru/token-api/quick-start.mdx b/website/src/pages/ru/token-api/quick-start.mdx index 59d60750c989..0930c3ceab94 100644 --- a/website/src/pages/ru/token-api/quick-start.mdx +++ b/website/src/pages/ru/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Быстрый старт The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Предварительные требования From 374d2023912e0d63ceed9744f30acbe142807053 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:51 -0400 Subject: [PATCH 241/290] New translations quick-start.mdx (Swedish) --- website/src/pages/sv/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/sv/token-api/quick-start.mdx b/website/src/pages/sv/token-api/quick-start.mdx index 4fabbaccb36e..14d8f13e5df7 100644 --- a/website/src/pages/sv/token-api/quick-start.mdx +++ b/website/src/pages/sv/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Snabbstart The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From ccca7b046e46856352c96f0c0e6a6fdc0dd6a204 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:52 -0400 Subject: [PATCH 242/290] New translations quick-start.mdx (Turkish) --- website/src/pages/tr/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/tr/token-api/quick-start.mdx b/website/src/pages/tr/token-api/quick-start.mdx index b321575025e9..6b4c6f410687 100644 --- a/website/src/pages/tr/token-api/quick-start.mdx +++ b/website/src/pages/tr/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Hızlı Başlangıç The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From a20c1b2a4a636f4d98048dbfdbe225fea4cb7714 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:53 -0400 Subject: [PATCH 243/290] New translations quick-start.mdx (Ukrainian) --- website/src/pages/uk/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/uk/token-api/quick-start.mdx b/website/src/pages/uk/token-api/quick-start.mdx index ea80878a9a0d..316cb901e8f6 100644 --- a/website/src/pages/uk/token-api/quick-start.mdx +++ b/website/src/pages/uk/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Швидкий старт The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From de953ce3978e4298a0e8d90c5c2a7ebb93815402 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:54 -0400 Subject: [PATCH 244/290] New translations quick-start.mdx (Chinese Simplified) --- website/src/pages/zh/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/zh/token-api/quick-start.mdx b/website/src/pages/zh/token-api/quick-start.mdx index 314459353ca6..9974b7bc59cf 100644 --- a/website/src/pages/zh/token-api/quick-start.mdx +++ b/website/src/pages/zh/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: 快速开始 The Graph的 代币API允许您通过 GET 请求访问区块链代币信息。 本指南旨在帮助您快速将 Token API 整合到您的应用程序中。 -代币API提供了访问网链代币数据的机会，包括余额、持有人、详细的代币元数据和历史传输。 此 API 还使用 Model Context 协议 (MCP) 来丰富原始区块链数据，并通过使用 Claude 等的 AI 工具来丰富相关联的洞察力。 +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## 先决条件 From d4325d4ea94fec8b30a12e3afd9a44c5fd828369 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:55 -0400 Subject: [PATCH 245/290] New translations quick-start.mdx (Urdu (Pakistan)) --- website/src/pages/ur/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/ur/token-api/quick-start.mdx b/website/src/pages/ur/token-api/quick-start.mdx index d3e0152a21b7..e0a75ff01acf 100644 --- a/website/src/pages/ur/token-api/quick-start.mdx +++ b/website/src/pages/ur/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: فورا شروع کریں The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From abd71cf91f1250dfb6da82971b34b40dc2ca42e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:57 -0400 Subject: [PATCH 246/290] New translations quick-start.mdx (Vietnamese) --- website/src/pages/vi/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/vi/token-api/quick-start.mdx b/website/src/pages/vi/token-api/quick-start.mdx index 93a5eae55597..7d9e37531ca4 100644 --- a/website/src/pages/vi/token-api/quick-start.mdx +++ b/website/src/pages/vi/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Bắt đầu nhanh The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From bc0ad8118357d173b1985618aa1e7c0547e7e67e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:58 -0400 Subject: [PATCH 247/290] New translations quick-start.mdx (Marathi) --- website/src/pages/mr/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/mr/token-api/quick-start.mdx b/website/src/pages/mr/token-api/quick-start.mdx index 9b6f9bb125a6..664228134ba7 100644 --- a/website/src/pages/mr/token-api/quick-start.mdx +++ b/website/src/pages/mr/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: क्विक स्टार्ट The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## Prerequisites From fb1e84f6c39e130ac2060c5fffced5da78d6b3be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Tue, 22 Apr 2025 20:52:59 -0400 Subject: [PATCH 248/290] New translations quick-start.mdx (Hindi) --- website/src/pages/hi/token-api/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/hi/token-api/quick-start.mdx b/website/src/pages/hi/token-api/quick-start.mdx index 494416568dc4..6a1848aeda79 100644 --- a/website/src/pages/hi/token-api/quick-start.mdx +++ b/website/src/pages/hi/token-api/quick-start.mdx @@ -9,7 +9,7 @@ sidebarTitle: Quick Start The Graph's Token API lets you access blockchain token information via a GET request. This guide is designed to help you quickly integrate the Token API into your application. -The Token API provides access to onchain token data, including balances, holders, detailed token metadata, and historical transfers. This API also uses the Model Context Protocol (MCP) to enrich raw blockchain data with contextual insights using AI tools, such as Claude. +The Token API provides access to onchain token data, including live and historical balances, holders, prices, market data, token metadata, and token transfers. This API also uses the Model Context Protocol (MCP) to allow AI tools such as Claude to enrich raw blockchain data with contextual insights. ## आवश्यक शर्तें From 9fc139227169b01ec412a5d5db3036dd9f1edc43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:33 -0400 Subject: [PATCH 249/290] New translations graphql-api.mdx (Romanian) --- .../ro/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ro/subgraphs/querying/graphql-api.mdx b/website/src/pages/ro/subgraphs/querying/graphql-api.mdx index e10201771989..6ff6a8777ce9 100644 --- a/website/src/pages/ro/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ro/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | Description | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | Description | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From e6497c3c3198396a90d0047f87d3ef34120dab27 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:34 -0400 Subject: [PATCH 250/290] New translations graphql-api.mdx (French) --- .../fr/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/fr/subgraphs/querying/graphql-api.mdx b/website/src/pages/fr/subgraphs/querying/graphql-api.mdx index ae81b6e5427c..912598c2fd97 100644 --- a/website/src/pages/fr/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/fr/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: API GraphQL --- -Découvrez l'API de requête GraphQL utilisée dans The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## Qu'est-ce que GraphQL ? [GraphQL](https://graphql.org/learn/) est un langage d'interrogation pour les API et un moteur d'exécution pour l'exécution de ces requêtes avec vos données existantes. Le graphe utilise GraphQL pour interroger les subgraphs. -Pour comprendre le rôle plus important joué par GraphQL, consultez [développer](/subgraphs/developing/introduction/) et [créer un subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Requêtes avec GraphQL -Dans votre schéma Subgraph, vous définissez des types appelés `Entities`. Pour chaque type `Entity`, les champs `entity` et `entities` seront générés sur le type `Query` de premier niveau. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note : `query` n'a pas besoin d'être inclus au début de la requête `graphql` lors de l'utilisation de The Graph. +### Example Queries -### Exemples +> Note : `query` n'a pas besoin d'être inclus au début de la requête `graphql` lors de l'utilisation de The Graph. Requête pour une seule entité `Token` définie dans votre schéma : @@ -44,7 +58,7 @@ Interroge toutes les entités `Token` : ### Tri -Lors de l'interrogation d'une collection, vous pouvez : +When querying a collection, you can: - Utilisez le paramètre `orderBy` pour trier les données en fonction d'un attribut spécifique. - Utilisez `orderDirection` pour spécifier la direction du tri, `asc` pour ascendant ou `desc` pour descendant. @@ -60,7 +74,7 @@ Lors de l'interrogation d'une collection, vous pouvez : } ``` -#### Exemple de tri d'entités imbriquées +#### Example for Nested Entity Sorting Depuis Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), les entités peuvent être triées sur la base des entités imbriquées. @@ -90,7 +104,7 @@ Lors de l'interrogation d'une collection, il est préférable de : - Utilisez le paramètre `skip` pour sauter des entités et paginer. Par exemple, `first:100` affiche les 100 premières entités et `first:100, skip:100` affiche les 100 entités suivantes. - Évitez d'utiliser les valeurs `skip` dans les requêtes car elles sont généralement peu performantes. Pour récupérer un grand nombre d'éléments, il est préférable de parcourir les entités en fonction d'un attribut, comme indiqué dans l'exemple précédent. -#### Exemple d'utilisation de `first` +#### Example Using `first` Interroger les 10 premiers tokens : @@ -103,9 +117,9 @@ Interroger les 10 premiers tokens : } ``` -Pour rechercher des groupes d'entités au milieu d'une collection, le paramètre `skip` peut être utilisé en conjonction avec le paramètre `first` pour sauter un nombre spécifié d'entités en commençant par le début de la collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Exemple utilisant `first` et `skip` +#### Example Using `first` and `skip` Interroger 10 entités `Token`, décalées de 10 places par rapport au début de la collection : @@ -118,7 +132,7 @@ Interroger 10 entités `Token`, décalées de 10 places par rapport au début de } ``` -#### Exemple utilisant `first` et `id_ge` +#### Example Using `first` and `id_ge` Si un client a besoin de récupérer un grand nombre d'entités, il est plus performant de baser les requêtes sur un attribut et de filtrer par cet attribut. Par exemple, un client pourrait récupérer un grand nombre de jetons en utilisant cette requête : @@ -138,9 +152,9 @@ La première fois, il enverra la requête avec `lastID = ""`, et pour les requê - Vous pouvez utiliser le paramètre `where` dans vos requêtes pour filtrer les différentes propriétés. - Vous pouvez filtrer sur plusieurs valeurs dans le paramètre `where`. -#### Exemple d'utilisation de `where` +#### Using `where` Filtering -Défis de la requête avec un résultat `failed` : +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -156,7 +170,7 @@ Défis de la requête avec un résultat `failed` : Vous pouvez utiliser des suffixes comme `_gt`, `_lte` pour comparer les valeurs : -#### Exemple de filtrage de plage +#### Range Filtering ```graphql { @@ -168,7 +182,7 @@ Vous pouvez utiliser des suffixes comme `_gt`, `_lte` pour comparer les valeurs } ``` -#### Exemple de filtrage par bloc +#### Block Filtering Vous pouvez également filtrer les entités qui ont été mises à jour dans ou après un bloc spécifié avec `_change_block(number_gte : Int)`. @@ -184,7 +198,7 @@ Cela peut être utile si vous cherchez à récupérer uniquement les entités qu } ``` -#### Exemple de filtrage d'entités imbriquées +#### Nested Entity Filtering Le filtrage sur la base d'entités imbriquées est possible dans les champs avec le suffixe `_`. @@ -202,11 +216,11 @@ Cela peut être utile si vous souhaitez récupérer uniquement les entités dont } ``` -#### Opérateurs logiques +### Logical Operators Depuis Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), vous pouvez regrouper plusieurs paramètres dans le même argument `where` en utilisant les opérateurs `and` ou `or` pour filtrer les résultats en fonction de plusieurs critères. -##### L'opérateur `AND` +#### Using `and` Operator L'exemple suivant filtre les défis avec `outcome` `succeeded` et `number` supérieur ou égal à `100`. @@ -236,7 +250,7 @@ L'exemple suivant filtre les défis avec `outcome` `succeeded` et `number` supé > } > ``` -##### L'opérateur `OR` +#### Using `or` Operator L'exemple suivant filtre les défis avec `outcome` `succeeded` ou `number` supérieur ou égal à `100`. @@ -252,7 +266,7 @@ L'exemple suivant filtre les défis avec `outcome` `succeeded` ou `number` supé } ``` -> **Note** : Lors de l'élaboration des requêtes, il est important de prendre en compte l'impact sur les performances de l'utilisation de l'opérateur `or`. Si `or` peut être un outil utile pour élargir les résultats d'une recherche, il peut aussi avoir des coûts importants. L'un des principaux problèmes de l'opérateur `or` est qu'il peut ralentir les requêtes. En effet, `or` oblige la base de données à parcourir plusieurs index, ce qui peut prendre beaucoup de temps. Pour éviter ces problèmes, il est recommandé aux développeurs d'utiliser les opérateurs and au lieu de or chaque fois que cela est possible. Cela permet un filtrage plus précis et peut conduire à des requêtes plus rapides et plus précises. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Tous les filtres @@ -289,7 +303,7 @@ En outre, les filtres globaux suivants sont disponibles en tant que partie de l' _change_block(numéro_gte : Int) ``` -### Interrogation des états précédents +### Time-travel Queries Vous pouvez interroger l'état de vos entités non seulement pour le dernier bloc, ce qui est le cas par défaut, mais aussi pour un bloc arbitraire dans le passé. Le bloc auquel une requête doit se produire peut être spécifié soit par son numéro de bloc, soit par son hash de bloc, en incluant un argument `block` dans les champs de niveau supérieur des requêtes. @@ -297,7 +311,7 @@ Le résultat d'une telle requête ne changera pas au fil du temps, c'est-à-dire > Remarque : l'implémentation actuelle est encore sujette à certaines limitations qui pourraient violer ces garanties. L'implémentation ne permet pas toujours de déterminer si un bloc donné n'est pas du tout sur la chaîne principale ou si le résultat d'une requête par bloc pour un bloc qui n'est pas encore considéré comme final peut être influencé par une réorganisation du bloc qui a lieu en même temps que la requête. Elles n'affectent pas les résultats des requêtes par hash de bloc lorsque le bloc est final et que l'on sait qu'il se trouve sur la chaîne principale. [Ce numéro](https://github.com/graphprotocol/graph-node/issues/1405) explique ces limitations en détail. -#### Exemple +#### Example Time-travel Queries ```graphql { @@ -313,8 +327,6 @@ Le résultat d'une telle requête ne changera pas au fil du temps, c'est-à-dire Cette requête renverra les entités `Challenge` et les entités `Application` qui leur sont associées, telles qu'elles existaient directement après le traitement du bloc numéro 8 000 000. -#### Exemple - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -329,24 +341,24 @@ Cette requête renverra les entités `Challenge` et les entités `Application` q Cette requête renverra les entités `Challenge`, et leurs entités `Application` associées, telles qu'elles existaient directement après le traitement du bloc avec le hash donné. -### Requêtes de recherche en texte intégral +### Full-text Search Queries -Les champs de recherche intégralement en texte fournissent une API de recherche textuelle expressive qui peut être ajoutée au schéma du subgraph et personnalisée. Reportez-vous à [Définir des champs de recherche en texte intégral](/developing/creating-a-subgraph/#defining-fulltext-search-fields) pour ajouter la recherche intégralement en texte à votre subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Les requêtes de recherche en texte intégral comportent un champ obligatoire, `text`, pour fournir les termes de la recherche. Plusieurs opérateurs spéciaux de texte intégral peuvent être utilisés dans ce champ de recherche `text`. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Opérateurs de recherche en texte intégral : +Full-text search operators: -| Symbole | Opérateur | Description | -| --- | --- | --- | -| `&` | `And` | Pour combiner plusieurs termes de recherche dans un filtre pour les entités incluant tous les termes fournis | -| | | `Or` | Les requêtes comportant plusieurs termes de recherche séparés par l'opérateur ou renverront toutes les entités correspondant à l'un des termes fournis | -| `<->` | `Follow by` | Spécifiez la distance entre deux mots. | -| `:*` | `Prefix` | Utilisez le terme de recherche de préfixe pour trouver les mots dont le préfixe correspond (2 caractères requis.) | +| Symbole | Opérateur | Description | | +| ------- | ----------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | Pour combiner plusieurs termes de recherche dans un filtre pour les entités incluant tous les termes fournis | | +| | | `Or` | Les requêtes comportant plusieurs termes de recherche séparés par l'opérateur ou renverront toutes les entités correspondant à l'un des termes fournis | +| `<->` | `Follow by` | Spécifiez la distance entre deux mots. | | +| `:*` | `Prefix` | Utilisez le terme de recherche de préfixe pour trouver les mots dont le préfixe correspond (2 caractères requis.) | | -#### Exemples +#### Full-text Query Examples -En utilisant l'opérateur `ou`, cette requête filtrera les entités de blog ayant des variations d' "anarchism" ou "crumpet" dans leurs champs de texte intégral. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -359,7 +371,7 @@ En utilisant l'opérateur `ou`, cette requête filtrera les entités de blog aya } ``` -L'opérateur `follow by` spécifie un mot à une distance spécifique dans les documents en texte intégral. La requête suivante renverra tous les blogs contenant des variations de "decentralize" suivies de "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -372,7 +384,7 @@ L'opérateur `follow by` spécifie un mot à une distance spécifique dans les d } ``` -Combinez des opérateurs de texte intégral pour créer des filtres plus complexes. Avec un opérateur de recherche de prétexte combiné à un suivi de cet exemple, la requête fera correspondre toutes les entités de blog avec des mots commençant par « lou » suivi de « musique ». +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -389,20 +401,6 @@ Combinez des opérateurs de texte intégral pour créer des filtres plus complex Graph Node met en œuvre une validation [basée sur les spécifications](https://spec.graphql.org/October2021/#sec-Validation) des requêtes GraphQL qu'il reçoit à l'aide de [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), qui est basée sur l'implémentation de référence [graphql-js](https://github.com/graphql/graphql-js/tree/main/src/validation). Les requêtes qui échouent à une règle de validation sont accompagnées d'une erreur standard - consultez les [spécifications GraphQL](https://spec.graphql.org/October2021/#sec-Validation) pour en savoir plus. -## Schema - -Le schéma de vos sources de données, c'est-à-dire les types d'entités, les valeurs et les relations qui peuvent être interrogés, est défini dans le [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -Les schémas GraphQL définissent généralement des types racines pour les `queries`, les `subscriptions` et les `mutations`. The Graph ne prend en charge que les `requêtes`. Le type racine `Query` pour votre subgraph est automatiquement généré à partir du schéma GraphQL qui est inclus dans votre [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Remarque : notre API n'expose pas les mutations car les développeurs sont censés émettre des transactions directement contre la blockchain sous-jacente à partir de leurs applications. - -### Entities - -Tous les types GraphQL avec des directives `@entity` dans votre schéma seront traités comme des entités et doivent avoir un champ `ID`. - -> **Note:** Actuellement, tous les types de votre schéma doivent avoir une directive `@entity`. Dans le futur, nous traiterons les types n'ayant pas la directive `@entity` comme des objets de valeur, mais cela n'est pas encore pris en charge. - ### Métadonnées du Subgraph Tous les subgraphs ont un objet `_Meta_` auto-généré, qui permet d'accéder aux métadonnées du subgraph. Cet objet peut être interrogé comme suit : From e721963e3ca0e005100cd97a0fd88e10ed1fbe5b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:35 -0400 Subject: [PATCH 251/290] New translations graphql-api.mdx (Spanish) --- .../es/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/es/subgraphs/querying/graphql-api.mdx b/website/src/pages/es/subgraphs/querying/graphql-api.mdx index 374291ce0a88..2ef3b093f4fe 100644 --- a/website/src/pages/es/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/es/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: API GraphQL --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entidades + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Esquema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Ejemplos +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Clasificación -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Ejemplo de filtrado de entidades anidadas +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Consulta los primeros 10 tokens: @@ -101,9 +115,9 @@ Consulta los primeros 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Ejemplo de filtrado de rango +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Ejemplo de filtrado de bloques +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Ejemplo de filtrado de entidades anidadas +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ Esto puede ser útil si estás buscando obtener solo entidades cuyas entidades d } ``` -#### Operadores lógicos +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Todos los filtros @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Consultas sobre Time-travel +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Ejemplo +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Ejemplo - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Consultas de Búsqueda de Texto Completo +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Operadores de búsqueda de texto completo: +Full-text search operators: -| Símbolo | Operador | Descripción | -| --- | --- | --- | -| `&` | `And` | Para combinar varios términos de búsqueda en un filtro para entidades que incluyen todos los términos proporcionados | -| | | `Or` | Las consultas con varios términos de búsqueda separados por o el operador devolverá todas las entidades que coincidan con cualquiera de los términos proporcionados | -| `<->` | `Follow by` | Especifica la distancia entre dos palabras. | -| `:*` | `Prefix` | Utilice el término de búsqueda del prefijo para encontrar palabras cuyo prefijo coincida (se requieren 2 caracteres.) | +| Símbolo | Operador | Descripción | | +| ------- | ----------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | Para combinar varios términos de búsqueda en un filtro para entidades que incluyen todos los términos proporcionados | | +| | | `Or` | Las consultas con varios términos de búsqueda separados por o el operador devolverá todas las entidades que coincidan con cualquiera de los términos proporcionados | +| `<->` | `Follow by` | Especifica la distancia entre dos palabras. | | +| `:*` | `Prefix` | Utilice el término de búsqueda del prefijo para encontrar palabras cuyo prefijo coincida (se requieren 2 caracteres.) | | -#### Ejemplos +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combina operadores de texto completo para crear filtros más complejos. Con un operador de búsqueda de pretexto combinado con una consulta de seguimiento de este ejemplo, se buscarán coincidencias con todas las entidades del blog con palabras que comiencen con "lou" seguido de "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combina operadores de texto completo para crear filtros más complejos. Con un o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Esquema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entidades - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Metadatos del subgrafo All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 36fe1cc05d0dd4d8a7a184eb6b7fdb058a90f4d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:37 -0400 Subject: [PATCH 252/290] New translations graphql-api.mdx (Arabic) --- .../ar/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ar/subgraphs/querying/graphql-api.mdx b/website/src/pages/ar/subgraphs/querying/graphql-api.mdx index 14e11ff80306..5f5a78a7e767 100644 --- a/website/src/pages/ar/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ar/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### المخطط + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| رمز | عامل التشغيل | الوصف | -| --- | --- | --- | -| `&` | `And` | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة | -| | | `Or` | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة | -| `<->` | `Follow by` | يحدد المسافة بين كلمتين. | -| `:*` | `Prefix` | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.) | +| رمز | عامل التشغيل | الوصف | | +| ----- | ------------ | ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة | | +| | | `Or` | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة | +| `<->` | `Follow by` | يحدد المسافة بين كلمتين. | | +| `:*` | `Prefix` | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## المخطط - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 9359522a3271c6ead8661ef8b7c5488b7424b24f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:38 -0400 Subject: [PATCH 253/290] New translations graphql-api.mdx (Czech) --- .../cs/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/cs/subgraphs/querying/graphql-api.mdx b/website/src/pages/cs/subgraphs/querying/graphql-api.mdx index e5dc52ccce1f..6997047e6da4 100644 --- a/website/src/pages/cs/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/cs/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Příklady +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Třídění -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Příklad vnořeného třídění entit +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Dotaz na prvních 10 tokenů: @@ -101,9 +115,9 @@ Dotaz na prvních 10 tokenů: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Příklad filtrování rozsahu +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Příklad pro filtrování bloků +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Příklad vnořeného filtrování entit +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ To může být užitečné, pokud chcete načíst pouze entity, jejichž entity } ``` -#### Logické operátory +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Všechny filtry @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Dotazy na cestování čase +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Příklad +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Příklad - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltextové Vyhledávání dotazy +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Operátory fulltextového vyhledávání: +Full-text search operators: -| Symbol | Operátor | Popis | -| --- | --- | --- | -| `&` | `And` | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy | -| | | `Or` | Dotazy s více hledanými výrazy oddělenými operátorem nebo vrátí všechny entity, které odpovídají některému z uvedených výrazů | -| `<->` | `Follow by` | Zadejte vzdálenost mezi dvěma slovy. | -| `:*` | `Prefix` | Pomocí předponového výrazu vyhledejte slova, jejichž předpona se shoduje (vyžadovány 2 znaky) | +| Symbol | Operátor | Popis | | +| ------ | ----------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy | | +| | | `Or` | Dotazy s více hledanými výrazy oddělenými operátorem nebo vrátí všechny entity, které odpovídají některému z uvedených výrazů | +| `<->` | `Follow by` | Zadejte vzdálenost mezi dvěma slovy. | | +| `:*` | `Prefix` | Pomocí předponového výrazu vyhledejte slova, jejichž předpona se shoduje (vyžadovány 2 znaky) | | -#### Příklady +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Kombinací fulltextových operátorů můžete vytvářet složitější filtry. S operátorem pretextového vyhledávání v kombinaci s operátorem follow by bude tento příklad dotazu odpovídat všem entitá blog se slovy začínajícími na "lou" a následovanými slovem "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Kombinací fulltextových operátorů můžete vytvářet složitější filtry. Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Metadata podgrafů All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 1c81afdfdc4d310a3d248bbd93aa34fe94ee6b7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:39 -0400 Subject: [PATCH 254/290] New translations graphql-api.mdx (German) --- .../de/subgraphs/querying/graphql-api.mdx | 108 ++++++++---------- 1 file changed, 50 insertions(+), 58 deletions(-) diff --git a/website/src/pages/de/subgraphs/querying/graphql-api.mdx b/website/src/pages/de/subgraphs/querying/graphql-api.mdx index effc56357802..1fde91ddab9b 100644 --- a/website/src/pages/de/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/de/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL-API --- -Erfahren Sie mehr über die GraphQL Query API, die in The Graph verwendet wird. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## Was ist GraphQL? [GraphQL] (https://graphql.org/learn/) ist eine Abfragesprache für APIs und eine Laufzeitumgebung für die Ausführung dieser Abfragen mit Ihren vorhandenen Daten. The Graph verwendet GraphQL zur Abfrage von Subgraphen. -Um die größere Rolle, die GraphQL spielt, zu verstehen, lesen Sie [Entwickeln](/subgraphs/entwickeln/einfuehrung/) und [Erstellen eines Subgraphen](/entwickeln/einen-subgraph-erstellen/). +## Core Concepts + +### Entitäten + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Abfragen mit GraphQL -In Ihrem Subgraph-Schema definieren Sie Typen namens `Entities`. Für jeden `Entity`-Typ werden `entity`- und `entities`-Felder auf der obersten Ebene des `Query`-Typs erzeugt. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Hinweis: Bei der Verwendung von The Graph muss `query` nicht am Anfang der `graphql`-Abfrage stehen. +### Example Queries -### Beispiele +> Hinweis: Bei der Verwendung von The Graph muss `query` nicht am Anfang der `graphql`-Abfrage stehen. Abfrage nach einer einzelnen, in Ihrem Schema definierten Entität `Token`: @@ -44,7 +58,7 @@ Abfrage aller `Token`-Entitäten: ### Sortierung -Wenn Sie eine Sammlung abfragen, können Sie: +When querying a collection, you can: - den Parameter `orderBy` verwenden, um nach einem bestimmten Attribut zu sortieren. - `orderDirection` verwenden, um die Sortierrichtung anzugeben, `asc` für aufsteigend oder `desc` für absteigend. @@ -60,7 +74,7 @@ Wenn Sie eine Sammlung abfragen, können Sie: } ``` -#### Beispiel für die Sortierung verschachtelter Entitäten +#### Example for Nested Entity Sorting Ab Graph Node [`v0.30.0`] (https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) können Entitäten auf der Basis von verschachtelten Entitäten sortiert werden. @@ -88,7 +102,7 @@ Wenn Sie eine Sammlung abfragen, ist es am besten, dies zu tun: - Verwenden Sie den Parameter `skip`, um Entitäten zu überspringen und zu paginieren. Zum Beispiel zeigt `first:100` die ersten 100 Entitäten und `first:100, skip:100` zeigt die nächsten 100 Entitäten. - Vermeiden Sie die Verwendung von `skip`-Werten in Abfragen, da diese im Allgemeinen schlecht funktionieren. Um eine große Anzahl von Elementen abzurufen, ist es am besten, die Entitäten auf der Grundlage eines Attributs zu durchblättern, wie im obigen Beispiel gezeigt. -#### Beispiel mit `first` +#### Example Using `first` Die Abfrage für die ersten 10 Token: @@ -101,9 +115,9 @@ Die Abfrage für die ersten 10 Token: } ``` -Um nach Gruppen von Entitäten in der Mitte einer Sammlung zu suchen, kann der Parameter `skip` in Verbindung mit dem Parameter `first` verwendet werden, um eine bestimmte Anzahl von Entitäten zu überspringen, beginnend am Anfang der Sammlung. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Beispiel mit `first` und `skip` +#### Example Using `first` and `skip` Abfrage von 10 „Token“-Entitäten, versetzt um 10 Stellen vom Beginn der Sammlung: @@ -116,7 +130,7 @@ Abfrage von 10 „Token“-Entitäten, versetzt um 10 Stellen vom Beginn der Sam } ``` -#### Beispiel mit `first` und `id_ge` +#### Example Using `first` and `id_ge` Wenn ein Client eine große Anzahl von Entitäten abrufen muss, ist es leistungsfähiger, Abfragen auf ein Attribut zu stützen und nach diesem Attribut zu filtern. Zum Beispiel könnte ein Client mit dieser Abfrage eine große Anzahl von Token abrufen: @@ -136,9 +150,9 @@ Beim ersten Mal würde es die Abfrage mit `lastID = „“` senden, und bei nach - Sie können den Parameter `where` in Ihren Abfragen verwenden, um nach verschiedenen Eigenschaften zu filtern. - Sie können nach mehreren Werten innerhalb des Parameters `where` filtern. -#### Beispiel mit `where` +#### Using `where` Filtering -Abfrage von Herausforderungen mit `failed`-Ergebnis: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Abfrage von Herausforderungen mit `failed`-Ergebnis: Sie können Suffixe wie `_gt`, `_lte` für den Wertevergleich verwenden: -#### Beispiel für Range-Filterung +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ Sie können Suffixe wie `_gt`, `_lte` für den Wertevergleich verwenden: } ``` -#### Beispiel für Block-Filterung +#### Block Filtering Sie können auch Entitäten filtern, die in oder nach einem bestimmten Block mit `_change_block(number_gte: Int)` aktualisiert wurden. @@ -182,7 +196,7 @@ Dies kann nützlich sein, wenn Sie nur Entitäten abrufen möchten, die sich ge } ``` -#### Beispiel für die Filterung verschachtelter Entitäten +#### Nested Entity Filtering Die Filterung nach verschachtelten Entitäten ist in den Feldern mit dem Suffix `_`möglich. @@ -200,11 +214,11 @@ Dies kann nützlich sein, wenn Sie nur die Entitäten abrufen möchten, deren un } ``` -#### Logische Operatoren +### Logical Operators Seit Graph Node [`v0.30.0`] (https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) können Sie mehrere Parameter im selben `where`-Argument gruppieren, indem Sie die `und`- oder `oder`-Operatoren verwenden, um Ergebnisse nach mehr als einem Kriterium zu filtern. -##### Operator `AND` +#### Using `and` Operator Das folgende Beispiel filtert nach Challenges mit `outcome` `succeeded` und `number` größer als oder gleich `100`. @@ -234,7 +248,7 @@ Das folgende Beispiel filtert nach Challenges mit `outcome` `succeeded` und `num > } > ``` -##### Operator `OR` +#### Using `or` Operator Das folgende Beispiel filtert nach Herausforderungen mit `outcome` `succeeded` oder `number` größer oder gleich `100`. @@ -250,13 +264,7 @@ Das folgende Beispiel filtert nach Herausforderungen mit `outcome` `succeeded` o } ``` -> Hinweis: Beim Erstellen von Abfragen ist es wichtig, die Auswirkungen der Verwendung des -> or-Operators auf die Leistung zu berücksichtigen. Obwohl or ein nützliches Tool zum -> Erweitern von Suchergebnissen sein kann, kann es auch erhebliche Kosten verursachen. Eines der Hauptprobleme mit -> or ist, dass Abfragen dadurch verlangsamt werden können. Dies liegt daran, dass or -> erfordert, dass die Datenbank mehrere Indizes durchsucht, was ein zeitaufwändiger Prozess sein kann. Um diese Probleme -> zu vermeiden, wird empfohlen, dass Entwickler and -Operatoren anstelle von oder verwenden, wann immer dies möglich -> ist. Dies ermöglicht eine präzisere Filterung und kann zu schnelleren und genaueren Abfragen führen. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Alle Filter @@ -293,7 +301,7 @@ Darüber hinaus sind die folgenden globalen Filter als Teil des Arguments `where _change_block(number_gte: Int) ``` -### Time-travel-Anfragen +### Time-travel Queries Sie können den Zustand Ihrer Entitäten nicht nur für den letzten Block abfragen, was der Standard ist, sondern auch für einen beliebigen Block in der Vergangenheit. Der Block, zu dem eine Abfrage erfolgen soll, kann entweder durch seine Blocknummer oder seinen Block-Hash angegeben werden, indem ein `block`-Argument in die Toplevel-Felder von Abfragen aufgenommen wird. @@ -301,7 +309,7 @@ Das Ergebnis einer solchen Abfrage wird sich im Laufe der Zeit nicht ändern, d. > Hinweis: Die derzeitige Implementierung unterliegt noch bestimmten Beschränkungen, die diese Garantien verletzen könnten. Die Implementierung kann nicht immer erkennen, dass ein bestimmter Block-Hash überhaupt nicht in der Hauptkette ist, oder ob ein Abfrageergebnis durch einen Block-Hash für einen Block, der noch nicht als endgültig gilt, durch eine gleichzeitig mit der Abfrage laufende Blockumstrukturierung beeinflusst werden könnte. Sie haben keinen Einfluss auf die Ergebnisse von Abfragen per Block-Hash, wenn der Block endgültig ist und sich bekanntermaßen in der Hauptkette befindet. In [Diese Ausgabe] (https://github.com/graphprotocol/graph-node/issues/1405) werden diese Einschränkungen im Detail erläutert. -#### Beispiel +#### Example Time-travel Queries ```graphql { @@ -317,8 +325,6 @@ Das Ergebnis einer solchen Abfrage wird sich im Laufe der Zeit nicht ändern, d. Diese Abfrage gibt die `Challenge`-Entitäten und die zugehörigen `Application`-Entitäten so zurück, wie sie unmittelbar nach der Verarbeitung von Block Nummer 8.000.000 bestanden. -#### Beispiel - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -333,24 +339,24 @@ Diese Abfrage gibt die `Challenge`-Entitäten und die zugehörigen `Application` Diese Abfrage gibt `Challenge`-Entitäten und die zugehörigen `Application`-Entitäten zurück, wie sie unmittelbar nach der Verarbeitung des Blocks mit dem angegebenen Hash vorhanden waren. -### Volltext-Suchanfragen +### Full-text Search Queries -Volltextsuchabfrage-Felder bieten eine aussagekräftige Textsuch-API, die dem Subgraph-Schema hinzugefügt und angepasst werden kann. Siehe [Definieren von Volltext-Suchfeldern](/developing/creating-a-subgraph/#defining-fulltext-search-fields), um die Volltextsuche zu Ihrem Subgraph hinzuzufügen. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Volltextsuchanfragen haben ein erforderliches Feld, `text`, für die Eingabe von Suchbegriffen. Mehrere spezielle Volltext-Operatoren sind verfügbar, die in diesem `text`-Suchfeld verwendet werden können. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Volltext-Suchanfragen: +Full-text search operators: -| Symbol | Operator | Beschreibung | -| --- | --- | --- | -| `&` | `And` | Zum Kombinieren mehrerer Suchbegriffe zu einem Filter für Entitäten, die alle bereitgestellten Begriffe enthalten | -| | | `Or` | Abfragen mit mehreren durch den Operator or getrennten Suchbegriffen geben alle Entitäten mit einer Übereinstimmung mit einem der bereitgestellten Begriffe zurück | -| `<->` | `Follow by` | Geben Sie den Abstand zwischen zwei Wörtern an. | -| `:*` | `Prefix` | Verwenden Sie den Präfix-Suchbegriff, um Wörter zu finden, deren Präfix übereinstimmt (2 Zeichen erforderlich) | +| Symbol | Operator | Beschreibung | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | Zum Kombinieren mehrerer Suchbegriffe zu einem Filter für Entitäten, die alle bereitgestellten Begriffe enthalten | | +| | | `Or` | Abfragen mit mehreren durch den Operator or getrennten Suchbegriffen geben alle Entitäten mit einer Übereinstimmung mit einem der bereitgestellten Begriffe zurück | +| `<->` | `Follow by` | Geben Sie den Abstand zwischen zwei Wörtern an. | | +| `:*` | `Prefix` | Verwenden Sie den Präfix-Suchbegriff, um Wörter zu finden, deren Präfix übereinstimmt (2 Zeichen erforderlich) | | -#### Beispiele +#### Full-text Query Examples -Mit dem Operator `or` filtert diese Abfrage nach Blog-Entitäten mit Variationen von entweder "anarchism" oder „crumpet“ in ihren Volltextfeldern. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -363,7 +369,7 @@ Mit dem Operator `or` filtert diese Abfrage nach Blog-Entitäten mit Variationen } ``` -Der Operator `follow by` gibt Wörter an, die in den Volltextdokumenten einen bestimmten Abstand zueinander haben. Die folgende Abfrage gibt alle Blogs mit Variationen von „decentralize“ gefolgt von „philosophy“ zurück +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -376,7 +382,7 @@ Der Operator `follow by` gibt Wörter an, die in den Volltextdokumenten einen be } ``` -Kombinieren Sie Volltextoperatoren, um komplexere Filter zu erstellen. Mit einem Präfix-Suchoperator in Kombination mit "follow by" von dieser Beispielabfrage werden alle Blog-Entitäten mit Wörtern abgeglichen, die mit „lou“ beginnen, gefolgt von „music“. +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -393,20 +399,6 @@ Kombinieren Sie Volltextoperatoren, um komplexere Filter zu erstellen. Mit einem Graph Node implementiert die [spezifikationsbasierte](https://spec.graphql.org/October2021/#sec-Validation) Validierung der empfangenen GraphQL-Abfragen mit [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), die auf der [graphql-js-Referenzimplementierung](https://github.com/graphql/graphql-js/tree/main/src/validation) basiert. Abfragen, die eine Validierungsregel nicht erfüllen, werden mit einem Standardfehler angezeigt - besuchen Sie die [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation), um mehr zu erfahren. -## Schema - -Das Schema Ihrer Datenquellen, d. h. die Entitätstypen, Werte und Beziehungen, die zur Abfrage zur Verfügung stehen, werden über die [GraphQL Interface Definition Language (IDL)] (https://facebook.github.io/graphql/draft/#sec-Type-System) definiert. - -GraphQL-Schemata definieren im Allgemeinen Wurzeltypen für „Abfragen“, „Abonnements“ und „Mutationen“. The Graph unterstützt nur `Abfragen`. Der Root-Typ „Abfrage“ für Ihren Subgraph wird automatisch aus dem GraphQL-Schema generiert, das in Ihrem [Subgraph-Manifest] enthalten ist (/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Hinweis: Unsere API stellt keine Mutationen zur Verfügung, da von den Entwicklern erwartet wird, dass sie aus ihren Anwendungen heraus Transaktionen direkt gegen die zugrunde liegende Blockchain durchführen. - -### Entitäten - -Alle GraphQL-Typen mit `@entity`-Direktiven in Ihrem Schema werden als Entitäten behandelt und müssen ein `ID`-Feld haben. - -> **Hinweis:** Derzeit müssen alle Typen in Ihrem Schema eine `@entity`-Direktive haben. In Zukunft werden wir Typen ohne `@entity`-Direktive als Wertobjekte behandeln, aber dies wird noch nicht unterstützt. - ### Subgraph-Metadaten Alle Subgraphen haben ein automatisch generiertes `_Meta_`-Objekt, das Zugriff auf die Metadaten des Subgraphen bietet. Dieses kann wie folgt abgefragt werden: From 21fa997f5da161f3324ea63498aae166f3344527 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:41 -0400 Subject: [PATCH 255/290] New translations graphql-api.mdx (Italian) --- .../it/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/it/subgraphs/querying/graphql-api.mdx b/website/src/pages/it/subgraphs/querying/graphql-api.mdx index 6449bb254449..e4ddad384d6d 100644 --- a/website/src/pages/it/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/it/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: API GraphQL --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entità + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Esempi +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Ordinamento -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Esempio di ordinamento di entità annidate +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Eseguire query di primi 10 token: @@ -101,9 +115,9 @@ Eseguire query di primi 10 token: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Esempio di filtraggio dell'intervallo +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Esempio di filtraggio dei blocchi +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Esempio di filtraggio di entità annidate +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ Questo può essere utile se si vuole recuperare solo le entità il cui livello d } ``` -#### Operatori logici +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Tutti i filtri @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Query Time-travel +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Esempio +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Esempio - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Query di ricerca fulltext +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Operatori di ricerca fulltext: +Full-text search operators: -| Simbolo | Operatore | Descrizione | -| --- | --- | --- | -| `&` | `And` | Per combinare più termini di ricerca in un filtro per le entità che includono tutti i termini forniti | -| | | `Or` | Le query con più termini di ricerca separati dall'operatore Or restituiranno tutte le entità con una corrispondenza tra i termini forniti | -| `<->` | `Follow by` | Specifica la distanza tra due parole. | -| `:*` | `Prefix` | Utilizzare il termine di ricerca del prefisso per trovare le parole il cui prefisso corrisponde (sono richiesti 2 caratteri.) | +| Simbolo | Operatore | Descrizione | | +| ------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | Per combinare più termini di ricerca in un filtro per le entità che includono tutti i termini forniti | | +| | | `Or` | Le query con più termini di ricerca separati dall'operatore Or restituiranno tutte le entità con una corrispondenza tra i termini forniti | +| `<->` | `Follow by` | Specifica la distanza tra due parole. | | +| `:*` | `Prefix` | Utilizzare il termine di ricerca del prefisso per trovare le parole il cui prefisso corrisponde (sono richiesti 2 caratteri.) | | -#### Esempi +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combinare gli operatori fulltext per creare filtri più complessi. Con un operatore di ricerca pretext combinato con un follow by questa query di esempio corrisponderà a tutte le entità del blog con parole che iniziano con "lou" seguite da "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combinare gli operatori fulltext per creare filtri più complessi. Con un operat Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entità - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Metadati del Subgraph All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From f6e48124e1d6b8cebf040c60fef8de24e3991db6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:42 -0400 Subject: [PATCH 256/290] New translations graphql-api.mdx (Japanese) --- .../ja/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ja/subgraphs/querying/graphql-api.mdx b/website/src/pages/ja/subgraphs/querying/graphql-api.mdx index c1700fb5e9da..19581d236459 100644 --- a/website/src/pages/ja/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ja/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### エンティティ + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### スキーマ + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### 例 +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### 並べ替え -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### ネストされたエンティティの並べ替えの例 +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` 最初の 10 個のトークンを照会します。 @@ -101,9 +115,9 @@ When querying a collection, it's best to: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### 範囲フィルタリングの例 +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### ブロックフィルタリングの例 +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### ネストされたエンティティ フィルタリングの例 +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ Filtering on the basis of nested entities is possible in the fields with the `_` } ``` -#### 論理演算子 +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### すべてのフィルター @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### タイムトラベル クエリ +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### 例 +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### 例 - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### 全文検索クエリ +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -全文検索演算子: +Full-text search operators: -| シンボル | オペレーター | 説明書き | -| --- | --- | --- | -| `&` | `And` | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。 | -| | | `Or` | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 | -| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。 | -| `:*` | `Prefix` | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要） | +| シンボル | オペレーター | 説明書き | | +| ----- | ----------- | ---------------------------------------------- | --------------------------------------------------------- | +| `&` | `And` | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。 | | +| | | `Or` | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 | +| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。 | | +| `:*` | `Prefix` | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要） | | -#### 例 +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -全文演算子を組み合わせて、より複雑なフィルターを作成します。口実検索演算子を follow by このサンプル クエリと組み合わせて使用​​すると、"lou" で始まり、その後に "music" が続く単語を持つすべてのブログ エンティティが一致します。 +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ The `follow by` operator specifies a words a specific distance apart in the full Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## スキーマ - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### エンティティ - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### サブグラフ メタデータ All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 65f96ad27f7b9c869173521cc8bf9e135b5ec0e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:43 -0400 Subject: [PATCH 257/290] New translations graphql-api.mdx (Korean) --- .../ko/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ko/subgraphs/querying/graphql-api.mdx b/website/src/pages/ko/subgraphs/querying/graphql-api.mdx index e10201771989..6ff6a8777ce9 100644 --- a/website/src/pages/ko/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ko/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | Description | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | Description | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 6bcfae3e8e0c40c82d890320e76d7ac6b5070b47 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:44 -0400 Subject: [PATCH 258/290] New translations graphql-api.mdx (Dutch) --- .../nl/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/nl/subgraphs/querying/graphql-api.mdx b/website/src/pages/nl/subgraphs/querying/graphql-api.mdx index e10201771989..6ff6a8777ce9 100644 --- a/website/src/pages/nl/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/nl/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | Description | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | Description | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 783463c771fe036c9a87cd1177fea926b7a6d6dd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:46 -0400 Subject: [PATCH 259/290] New translations graphql-api.mdx (Polish) --- .../pl/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/pl/subgraphs/querying/graphql-api.mdx b/website/src/pages/pl/subgraphs/querying/graphql-api.mdx index e10201771989..6ff6a8777ce9 100644 --- a/website/src/pages/pl/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/pl/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | Description | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | Description | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 399e07a413eeff305f6dff8f90ab37ecf1441295 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:47 -0400 Subject: [PATCH 260/290] New translations graphql-api.mdx (Portuguese) --- .../pt/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/pt/subgraphs/querying/graphql-api.mdx b/website/src/pages/pt/subgraphs/querying/graphql-api.mdx index 81070e023b76..1432f41e790d 100644 --- a/website/src/pages/pt/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/pt/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: API GraphQL --- -Aprenda sobre a API de Queries da GraphQL, usada no The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## O Que é a GraphQL? A [GraphQL](https://graphql.org/learn/) é uma linguagem de queries para APIs e um sistema de tempo de execução (runtime) para executar esses queries, com os seus dados já existentes. O The Graph usa a GraphQL para fazer queries em subgraphs. -Para entender melhor o papel maior da GraphQL, veja [como programar](/subgraphs/developing/introduction/) e [criar um subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entidades + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries com a GraphQL -No seu schema de subgraph, você definirá tipos chamados `Entities` ("Entidades"). Para cada tipo `Entity`, campos `entity` e `entities` serão gerados no tipo de nível superior `Query`. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Observação: `query` não precisa ser incluído no topo do query `graphql` enquanto usar o The Graph. +### Example Queries -### Exemplos +> Observação: `query` não precisa ser incluído no topo do query `graphql` enquanto usar o The Graph. Query para uma entidade `Token` definida no seu schema: @@ -44,7 +58,7 @@ Faça um query de todas as entidades `Token`: ### Organização -Quando fizer um query de uma coleção, você poderá: +When querying a collection, you can: - Use o parâmetro `orderBy` para organizar os resultados por atributos específicos. - Use `orderDirection` para especificar a direção da organização; `asc` para ordem crescente ou `desc` para decrescente. @@ -60,7 +74,7 @@ Quando fizer um query de uma coleção, você poderá: } ``` -#### Exemplo para organização de entidade aninhada +#### Example for Nested Entity Sorting Com o lançamento da versão [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) do Graph Node, as entidades podem ser organizadas com base nas entidades aninhadas. @@ -88,7 +102,7 @@ Quando fizer um query de uma coleção, recomendamos: - Usar o parâmetro `skip` para pular entidades e paginar. Por exemplo: `first:100` mostra as primeiras 100 entidades e `first:100, skip:100` mostra as próximas 100. - Evitar usar valores `skip` em queries, já que o desempenho destes normalmente não é bom. Para resgatar um grande volume de itens, recomendamos paginar entidades com base num atributo, conforme demonstrado no exemplo acima. -#### Exemplo com `first` +#### Example Using `first` Consulte os 10 primeiros tokens: @@ -101,9 +115,9 @@ Consulte os 10 primeiros tokens: } ``` -Para fazer queries sobre grupos de entidades no meio de uma coleção, o parâmetro `skip` pode ser usado em conjunto com o parâmetro `first` para pular um número especificado de entidades, a começar no início da coleção. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Exemplo com `first` e `skip` +#### Example Using `first` and `skip` Faça query de 10 entidades Token, deslocadas por 10 posições do começo da coleção: @@ -116,7 +130,7 @@ Faça query de 10 entidades Token, deslocadas por 10 posições do começo da co } ``` -#### Exemplo com `first` e `id_ge` +#### Example Using `first` and `id_ge` Se um cliente precisar retirar um grande volume de entidades, é muito mais eficiente basear queries num atributo e filtrar pelo mesmo. Por exemplo, um cliente retiraria um número grande de tokens com este query: @@ -136,9 +150,9 @@ Na primeira vez, ele enviaria o query com `lastID = ""`, e nas solicitações se - O parâmetro `where` pode ser usado nos seus queries para filtrar propriedades diferentes. - Vários valores podem ser filtrados dentro do parâmetro `where`. -#### Exemplo com `where` +#### Using `where` Filtering -Faça um query sobre desafios com o resultado `failed` (falha): +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Faça um query sobre desafios com o resultado `failed` (falha): É possível usar sufixos como `_gt`, ou `_lte`, para comparar valores: -#### Exemplo para filtragem de alcance +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ Faça um query sobre desafios com o resultado `failed` (falha): } ``` -#### Exemplo para filtragem de blocos +#### Block Filtering Também dá para filtrar entidades atualizadas dentro de, ou depois de, um bloco específico com `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ Isto pode servir caso o seu plano seja retirar apenas entidades que mudaram, por } ``` -#### Exemplo para filtragem de entidade ninhada +#### Nested Entity Filtering É possível usar filtros com base em entidades aninhadas nos campos com o sufixo `_`. @@ -200,11 +214,11 @@ Isto é bom caso mire retirar apenas entidades cujas entidades de nível-filho c } ``` -#### Operadores lógicos +### Logical Operators Com o lançamento da versão [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) do Graph Node, é possível agrupar vários parâmetros no mesmo argumento `where`, com os operadores `and` ou `or`, para filtrar resultados com base em mais de um critério. -##### Operador `AND` +#### Using `and` Operator O exemplo a seguir filtra por desafios com o `outcome` ("resultado") `succeeded` ("sucesso"), e `number` ("número") maior que ou igual a `100`. @@ -234,7 +248,7 @@ O exemplo a seguir filtra por desafios com o `outcome` ("resultado") `succeeded` > } > ``` -##### Operador `OR` +#### Using `or` Operator O exemplo a seguir filtra desafios com o `outcome` `succeeded`, e o `number` maior que ou igual a `100`. @@ -250,7 +264,7 @@ O exemplo a seguir filtra desafios com o `outcome` `succeeded`, e o `number` mai } ``` -> **Observação**: Ao construir queries, é importante considerar o impacto do desempenho do operador `or`. O `or` pode ser útil para ampliar os resultados da busca, mas também pode ter custos significativos. Um dos maiores problemas com o `or` é que pode desacelerar os queries. Isto é porque o `or` exige que o banco de dados escaneie através de vários índices, o que pode demorar muito. Para evitar estes problemas, recomendamos que os programadores usem operadores `and` em vez de `or` sempre que possível. Isto retorna filtragens mais precisas, e pode levar a queries mais rápidos e confiáveis. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Todos os Filtros @@ -287,7 +301,7 @@ Além disto, os seguintes filtros globais estão disponíveis como parte do argu _change_block(number_gte: Int) ``` -### Consultas de viagem no tempo +### Time-travel Queries É possível solicitar o estado das suas entidades não só para o bloco mais recente, que é o padrão, mas também para um bloco arbitrário no passado. O bloco em que acontece um query pode ser especificado pelo seu número, ou pelo seu hash, ao incluir um argumento `block` nos campos de nível superior de query. @@ -295,7 +309,7 @@ O resultado de um query assim não mudará com o tempo; por exemplo, queries num > Observação: a implementação atual ainda está sujeita a certas limitações que podem violar estas garantias. A implementação nem sempre percebe que um hash de bloco não está na chain principal, ou que um query por hash de bloco retorna um bloco que não pode ser considerado final, mas que pode ser influenciado por uma reorganização de bloco executada concorrente com a solicitação. Elas não afetam os resultados de queries por hash de bloco quando o bloco é final e tem sua presença conhecida na chain principal. [Este inquérito](https://github.com/graphprotocol/graph-node/issues/1405) explica estas limitações em detalhes. -#### Exemplo +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ O resultado de um query assim não mudará com o tempo; por exemplo, queries num Este query retornará entidades `Challenge` e as suas entidades `Application` associadas, já que existiram diretamente após processar o bloco de número 8.000.000. -#### Exemplo - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ Este query retornará entidades `Challenge` e as suas entidades `Application` as Este query retornará entidades `Challenge` e as suas entidades `Application` associadas, já que existiram diretamente após processar o bloco com o hash indicado. -### Consultas de Busca Fulltext +### Full-text Search Queries -Campos de busca em full-text fornecem uma API de busca de texto expressiva, que pode ser adicionada e personalizada ao schema do subgraph. Para adicionar buscas em full-text ao seu subgraph, veja [Como Definir Campos de Busca em Full-Text](/developing/creating-a-subgraph/#defining-fulltext-search-fields). +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Buscas em full-text têm um campo obrigatório, `text`, para ofertar termos de busca. Vários operadores especiais de full-text estão disponíveis para uso neste campo de busca `text`. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Operadores de busca fulltext: +Full-text search operators: -| Símbolo | Operador | Descrição | -| --- | --- | --- | -| `&` | `And` | Para combinar múltiplos termos de busca num filtro para entidades que incluem todos os termos fornecidos | -| | | `Or` | Consultas com vários termos de busca separados pelo operador or retornarão todas as entidades com uma correspondência de qualquer termo providenciado | -| `<->` | `Follow by` | Especifica a distância entre duas palavras. | -| `:*` | `Prefix` | Use o prefixo para encontrar palavras que correspondem a tal prefixo (2 caracteres necessários.) | +| Símbolo | Operador | Descrição | | +| ------- | ----------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | Para combinar múltiplos termos de busca num filtro para entidades que incluem todos os termos fornecidos | | +| | | `Or` | Consultas com vários termos de busca separados pelo operador or retornarão todas as entidades com uma correspondência de qualquer termo providenciado | +| `<->` | `Follow by` | Especifica a distância entre duas palavras. | | +| `:*` | `Prefix` | Use o prefixo para encontrar palavras que correspondem a tal prefixo (2 caracteres necessários.) | | -#### Exemplos +#### Full-text Query Examples -Com o operador `or`, esta consulta filtrará para entidades de blog com variações de "anarchism" ou "crumpet" nos seus campos fulltext. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Com o operador `or`, esta consulta filtrará para entidades de blog com variaç } ``` -O operador `follow by` especifica palavras separadas por uma distância específica nos documentos fulltext. A query a seguir retornará todos os blogs com variações de "decentralize" ("descentralizar") seguido por "philosophy" ("filosofia") +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ O operador `follow by` especifica palavras separadas por uma distância específ } ``` -Combine operadores de fulltext para fazer filtros mais complexos. Com um operador de busca pretext combinado com um 'follow by', este exemplo de consulta corresponderá todas as entidades de blog com palavras que começam com "lou" seguido de "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine operadores de fulltext para fazer filtros mais complexos. Com um operado O Graph Node implementa validações [baseadas em especificação](https://spec.graphql.org/October2021/#sec-Validation) dos queries da GraphQL que recebe, através do [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules) — que tem base na [referência de implementação graphql-js](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries que não aderem a uma regra de validação fazem isso com um erro comum — para saber mais, visite as [especificações da GraphQL](https://spec.graphql.org/October2021/#sec-Validation). -## Schema - -O schema dos seus dataSources — por exemplo, os tipos de entidade, valores, e conexões que podem ser solicitados num query — é definido através da [Linguagem de Definição de Interface da GraphQL (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -Os schemas GraphQL geralmente definem tipos de origem para `queries` (solicitações), `subscriptions` (inscrições) e `mutations` (mutações). O The Graph só apoia `queries`. A origem `Query` para o seu subgraph é gerada automaticamente a partir do schema GraphQL incluído no [manifest do seu subgraph](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Nota: A nossa API não expõe mutações, porque esperamos que os programadores emitam transações diretamente dos seus aplicativos perante a blockchain subjacente. - -### Entidades - -Todos os tipos GraphQL com diretivos `@entity` no seu schema serão tratados como entidades, e devem ter um campo `ID`. - -> **Observação:** Atualmente, todos os tipos no seu schema devem ter um diretivo `@entity`. No futuro, trataremos tipos sem um diretivo `@entity` como objetos de valor, mas ainda não há apoio a isto. - ### Metadados de Subgraph Todos os subgraphs devem ter um objeto `_Meta_` gerado automaticamente, que permite acesso aos metadados do subgraph. Isto pode ser solicitado num query como o query mostrado a seguir: From d3c3178f3b824280d70f11ea3322b0d79e4812df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:48 -0400 Subject: [PATCH 261/290] New translations graphql-api.mdx (Russian) --- .../ru/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ru/subgraphs/querying/graphql-api.mdx b/website/src/pages/ru/subgraphs/querying/graphql-api.mdx index 899c3e3caa7e..e9880cd1b395 100644 --- a/website/src/pages/ru/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ru/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: API GraphQL --- -Узнайте о GraphQL API запросах, используемых в The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## Что такое GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Объекты + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Схема + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Запросы с GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Примечание: `query` не нужно указывать в начале `graphql` запроса при использовании The Graph. +### Example Queries -### Примеры +> Примечание: `query` не нужно указывать в начале `graphql` запроса при использовании The Graph. Запрос для одного объекта `Token`, определенного в Вашей схеме: @@ -44,7 +58,7 @@ In your Subgraph schema you define types called `Entities`. For each `Entity` ty ### Сортировка -При запросе коллекции Вы можете: +When querying a collection, you can: - Использовать параметр `orderBy` для сортировки по определенному атрибуту. - Использовать параметр `orderDirection`, чтобы указать направление сортировки `asc` для возрастания или `desc` для убывания. @@ -60,7 +74,7 @@ In your Subgraph schema you define types called `Entities`. For each `Entity` ty } ``` -#### Пример сортировки вложенных объектов +#### Example for Nested Entity Sorting Начиная с Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), объекты можно сортировать на основе вложенных объектов. @@ -88,7 +102,7 @@ In your Subgraph schema you define types called `Entities`. For each `Entity` ty - Использовать параметр `skip`, чтобы пропускать объекты и осуществлять пагинацию. Например, `first:100` покажет первые 100 объектов, а `first:100, skip:100` покажет следующие 100 объектов. - Избегайте использования `skip` в запросах, так как это обычно приводит к низкой производительности. Для получения большого количества элементов лучше выполнять постраничную загрузку объектов на основе атрибута, как показано в предыдущем примере. -#### Пример использования `first` +#### Example Using `first` Запрос первых 10 токенов: @@ -101,9 +115,9 @@ In your Subgraph schema you define types called `Entities`. For each `Entity` ty } ``` -Чтобы запросить группы объектов в середине коллекции, параметр `skip` можно использовать в сочетании с параметром `first`, чтобы пропустить указанное количество объектов, начиная с начала коллекции. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Пример использования `first` и `skip` +#### Example Using `first` and `skip` Запрос 10 объектов `Token`, смещенных на 10 позиций от начала коллекции: @@ -116,7 +130,7 @@ In your Subgraph schema you define types called `Entities`. For each `Entity` ty } ``` -#### Пример использования `first` и `id_ge` +#### Example Using `first` and `id_ge` Если клиенту нужно получить большое количество объектов, эффективнее выполнять запросы на основе атрибута и фильтровать по этому атрибуту. Например, клиент может получить большое количество токенов с помощью следующего запроса: @@ -136,9 +150,9 @@ query manyTokens($lastID: String) { - Вы можете использовать параметр `where` в запросах для фильтрации по различным свойствам. - Вы можете фильтровать по нескольким значениям внутри параметра `where`. -#### Пример использования `where` +#### Using `where` Filtering -Запрос задач с результатом `failed`: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ query manyTokens($lastID: String) { Вы можете использовать такие суффиксы, как `_gt`, `_lte` для сравнения значений: -#### Пример фильтрации диапазона +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ query manyTokens($lastID: String) { } ``` -#### Пример фильтрации блока +#### Block Filtering Вы также можете фильтровать объекты, которые были обновлены на указанном блоке или позже, с помощью `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Пример фильтрации вложенных объектов +#### Nested Entity Filtering Фильтрация на основе вложенных объектов возможна в полях с суффиксом `_`. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Логические операторы +### Logical Operators Начиная с Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), Вы можете группировать несколько параметров в одном аргументе `where`, используя операторы `and` или `or` для фильтрации результатов по нескольким критериям. -##### Оператор `AND` +#### Using `and` Operator Следующий пример фильтрует задачи с `outcome` `succeeded` и `number` больше или равно `100`. @@ -234,7 +248,7 @@ This can be useful if you are looking to fetch only entities which have changed, > } > ``` -##### Оператор `OR` +#### Using `or` Operator Следующий пример фильтрует задачи с `outcome` `succeeded` или `number` больше или равно `100`. @@ -250,7 +264,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -> **Примечание**: При составлении запросов важно учитывать влияние оператора `or` на производительность. Хотя `or` может быть полезным инструментом для расширения результатов поиска, он также может значительно замедлить запросы. Основная проблема в том, что `or` заставляет базу данных сканировать несколько индексов, что может быть ресурсоемким процессом. Чтобы избежать этих проблем, рекомендуется по возможности использовать оператор `and` вместо `or`. Это позволяет выполнять более точную фильтрацию и делает запросы быстрее и эффективнее. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Все фильтры @@ -287,7 +301,7 @@ _not_ends_with_nocase _change_block(number_gte: Int) ``` -### Запросы на Time-travel +### Time-travel Queries Вы можете запрашивать состояние своих объектов не только для последнего блока, который используется по умолчанию, но и для произвольного блока в прошлом. Блок, в котором должен выполняться запрос, можно указать либо по номеру блока, либо по его хэшу, включив аргумент `block` в поля верхнего уровня запросов. @@ -295,7 +309,7 @@ _change_block(number_gte: Int) > Примечание: Текущая реализация все еще подвержена определенным ограничениям, которые могут нарушить эти гарантии. Реализация не всегда может точно определить, что данный хэш блока вообще не находится на основном чейне, или что результат запроса по хэшу блока для блока, который еще не считается окончательным, может быть изменен из-за реорганизации блоков, происходящей одновременно с запросом. Эти ограничения не влияют на результаты запросов по хэшу блока, если блок окончателен и подтвержден на основном чейне. [Этот вопрос](https://github.com/graphprotocol/graph-node/issues/1405) подробно объясняет, в чем состоят эти ограничения. -#### Пример +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ _change_block(number_gte: Int) Этот запрос вернет объекты `Challenge` и связанные с ними объекты `Application` в том виде, в каком они существовали сразу после обработки блока номер 8,000,000. -#### Пример - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ _change_block(number_gte: Int) Этот запрос вернет объекты `Challenge` и связанные с ними объекты `Application` в том виде, в каком они существовали сразу после обработки блока с заданным хешем. -### Полнотекстовые поисковые запросы +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Запросы полнотекстового поиска имеют одно обязательное поле, `text`, для предоставления поисковых запросов. В этом поле поиска `text` можно использовать несколько специальных операторов полнотекстового поиска. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Полнотекстовые поисковые операторы: +Full-text search operators: -| Символ | Оператор | Описание | -| --- | --- | --- | -| `&` | `And` | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия | -| | | `Or` | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий | -| `<->` | `Follow by` | Укажите расстояние между двумя словами. | -| `:*` | `Prefix` | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа) | +| Символ | Оператор | Описание | | +| ------ | ----------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия | | +| | | `Or` | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий | +| `<->` | `Follow by` | Укажите расстояние между двумя словами. | | +| `:*` | `Prefix` | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа) | | -#### Примеры +#### Full-text Query Examples -Используя оператор `or`, этот запрос отфильтрует объекты блога, содержащие варианты слов "anarchism" или "crumpet" в их полнотекстовых полях. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Fulltext search query fields provide an expressive text search API that can be a } ``` -Оператор `follow by` определяет слова, находящиеся на определённом расстоянии друг от друга в полнотекстовых документах. Следующий запрос вернёт все блоги, содержащие варианты слова "decentralize", за которым следует "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ Fulltext search query fields provide an expressive text search API that can be a } ``` -Комбинируйте полнотекстовые операторы, чтобы создавать более сложные фильтры. С оператором поиска по префиксу в сочетании с запросом «follow by» будут найдены все объекты блога со словами, начинающимися с «lou», за которыми следует «music». +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Fulltext search query fields provide an expressive text search API that can be a Graph Node реализует валидацию [на основе спецификации](https://spec.graphql.org/October2021/#sec-Validation) для получаемых GraphQL-запросов с использованием [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), которая основана на [референсной реализации graphql-js](https://github.com/graphql/graphql-js/tree/main/src/validation). Запросы, не прошедшие проверку валидации, завершаются стандартной ошибкой. Ознакомьтесь со [спецификацией GraphQL](https://spec.graphql.org/October2021/#sec-Validation), чтобы узнать больше. -## Схема - -Схема Ваших источников данных, то есть типы объектов, значения и связи, доступные для запросов, определяется с помощью [Языка определения интерфейсов GraphQL (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Примечание: Наш API не подвергается мутациям, поскольку ожидается, что разработчики будут отправлять транзакции напрямую на базовый блокчейн из своих приложений. - -### Объекты - -Все типы GraphQL с директивами `@entity` в Вашей схеме будут рассматриваться как объекты и должны содержать поле `ID`. - -> **Примечание:** В настоящее время все типы в Вашей схеме должны иметь директиву `@entity`. В будущем мы будем рассматривать типы без директивы `@entity` как объекты значений, но на данный момент это не поддерживается. - ### Метаданные субграфа All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 55f00c4d191dbcc0707a19a2b8d1f2e7c05dab6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:49 -0400 Subject: [PATCH 262/290] New translations graphql-api.mdx (Swedish) --- .../sv/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/sv/subgraphs/querying/graphql-api.mdx b/website/src/pages/sv/subgraphs/querying/graphql-api.mdx index 535f48fc7790..72d0f0e3eb59 100644 --- a/website/src/pages/sv/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/sv/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entiteter + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Exempel +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sortering -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Exempel på sortering av nästlade entiteter +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Fråga efter de första 10 tokens: @@ -101,9 +115,9 @@ Fråga efter de första 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Exempel på filtrering av intervall +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Exempel på blockfiltrering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Exempel på filtrering av inbäddade entiteter +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ Detta kan vara användbart om du vill hämta endast entiteter vars entiteter på } ``` -#### Logiska operatorer +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Alla filter @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Tidsreseförfrågningar +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Exempel +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Exempel - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltextsökförfrågningar +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltextsökoperatorer: +Full-text search operators: -| Symbol | Operatör | Beskrivning | -| --- | --- | --- | -| `&` | `And` | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna | -| | | `Or` | Förfrågningar med flera söktermer separerade av ellipsen kommer att returnera alla entiteter med en matchning från någon av de angivna termerna | -| `<->` | `Follow by` | Ange avståndet mellan två ord. | -| `:*` | `Prefix` | Använd prefixsöktermen för att hitta ord vars prefix matchar (2 tecken krävs.) | +| Symbol | Operatör | Beskrivning | | +| ------ | ----------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna | | +| | | `Or` | Förfrågningar med flera söktermer separerade av ellipsen kommer att returnera alla entiteter med en matchning från någon av de angivna termerna | +| `<->` | `Follow by` | Ange avståndet mellan två ord. | | +| `:*` | `Prefix` | Använd prefixsöktermen för att hitta ord vars prefix matchar (2 tecken krävs.) | | -#### Exempel +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Kombinera fulltextoperatorer för att skapa mer komplexa filter. Med en pretext-sökoperatör kombinerad med en follow by kommer detta exempel att matcha alla bloggenheter med ord som börjar med "lou" följt av "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Kombinera fulltextoperatorer för att skapa mer komplexa filter. Med en pretext- Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entiteter - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Metadata för undergrafer All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 0e97935e1c0e4accd636f8f99cfa0528f14d5c2c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:51 -0400 Subject: [PATCH 263/290] New translations graphql-api.mdx (Turkish) --- .../tr/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/tr/subgraphs/querying/graphql-api.mdx b/website/src/pages/tr/subgraphs/querying/graphql-api.mdx index f843969ea758..faafcbbe1af9 100644 --- a/website/src/pages/tr/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/tr/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API'ı --- -The Graph'te kullanılan GraphQL Sorgu API'ı hakkında bilgi edinin. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## GraphQL Nedir? [GraphQL] (https://graphql.org/learn/), API'lar için bir sorgu dili ve bu sorguları mevcut verileriniz üzerinde çalıştıran bir sorgu dilidir. The Graph, Subgraph'leri sorgulamak için GraphQL kullanır. -GraphQL’in daha kapsamlı rolünü anlamak için [geliştirme](/subgraphs/developing/introduction/) ve [bir Subgraph oluşturma](/developing/creating-a-subgraph/) bölümlerini inceleyin. +## Core Concepts + +### Varlıklar + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Şema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## GraphQL Sorguları -Subgraph şemanızda, `Entities` (Varlıklar) olarak adlandırılan türleri tanımlarsınız. Her bir `Entity` (Varlık) türü için, üst düzey `Query` türü üzerinde `entity` ve `entities` alanları otomatik olarak oluşturulur. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Not: The Graph'te, `graphql` sorgularının başına `query` (sorgu) ifadesinin eklenmesi gerekmez. +### Example Queries -### Örnekler +> Not: The Graph'te, `graphql` sorgularının başına `query` (sorgu) ifadesinin eklenmesi gerekmez. Şemanızda tanımlı tek bir `Token` varlığı için sorgu: @@ -44,7 +58,7 @@ Tüm `Token` varlıklarını sorgulama: ### Sıralama -Bir koleksiyon sorgularken şunları yapabilirsiniz: +When querying a collection, you can: - Belirli bir özniteliğe göre sıralama yapmak için `orderBy` parametresini kullanın. - Sıralama yönünü belirtmek için `orderDirection` kullanın; artan sıralama için `asc`, azalan sıralama için `desc`. @@ -60,7 +74,7 @@ Bir koleksiyon sorgularken şunları yapabilirsiniz: } ``` -#### İç içe varlık sıralaması için örnek +#### Example for Nested Entity Sorting Graph Düğümü [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) sürümünden itibaren, varlıklar iç içe ve varlıklara göre sıralanabilir. @@ -88,7 +102,7 @@ Bir koleksiyon sorgularken aşağıdakileri uygulamanız önerilir: - Varlıkları atlamak ve sayfalama yapmak için `skip` parametresini kullanın. Örneğin, `first:100` ilk 100 varlığı gösterir. `first:100, skip:100` ise sonraki 100 varlığı gösterir. - Sorgularda `skip` değerlerini kullanmaktan kaçının, çünkü genellikle düşük performans gösterirler. Çok sayıda ögeyi getirmek için, yukarıdaki örnekte gösterildiği gibi bir özniteliğe göre varlıklar arasında sayfalama yapmak en iyi yaklaşımdır. -#### `first` kullanımına örnek +#### Example Using `first` İlk 10 tokeni sorgulayın: @@ -101,9 +115,9 @@ Bir koleksiyon sorgularken aşağıdakileri uygulamanız önerilir: } ``` -Bir koleksiyonun ortasındaki varlık gruplarını sorgulamak için, `skip` parametresi `first` parametresiyle birlikte kullanılabilir. Bu, koleksiyonun başından itibaren belirli sayıda varlığı atlayarak sorgulama yapmanızı sağlar. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### `first` ve `skip` kullanımına örnek +#### Example Using `first` and `skip` Koleksiyonun başından itibaren 10 öge atlayarak 10 `Token` varlığı sorgulama: @@ -116,7 +130,7 @@ Koleksiyonun başından itibaren 10 öge atlayarak 10 `Token` varlığı sorgula } ``` -#### `first` ve `id_ge` kullanımına örnek +#### Example Using `first` and `id_ge` Bir istemcinin çok sayıda varlık alması gerektiğinde, sorguları bir öznitelik temelinde oluşturmak ve bu özniteliğe göre filtrelemek daha yüksek performans sağlar. Örneğin, bir istemci aşağıdaki sorguyu kullanarak çok sayıda token alabilir: @@ -136,9 +150,9 @@ query manyTokens($lastID: String) { - `where` parametresini sorgularınızda farklı özellikleri filtrelemek için kullanabilirsiniz. - Birden çok değeri `where` parametresi içinde filtreleyebilirsiniz. -#### `where` kullanımına örnek +#### Using `where` Filtering -`outcome` değeri `failed` olan challenge'ları sorgulama: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ query manyTokens($lastID: String) { `_gt`, `_lte` gibi son ekleri değer karşılaştırması için kullanabilirsiniz: -#### Aralık filtreleme için örnek +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ query manyTokens($lastID: String) { } ``` -#### Blok filtreleme için örnek +#### Block Filtering Belirtilen bir blokta veya sonrasında güncellenen varlıkları, `_change_block(number_gte: Int)` ile de filtreleyebilirsiniz. @@ -182,7 +196,7 @@ Bu, yalnızca değişen varlıkları getirmek istiyorsanız kullanışlı olabil } ``` -#### İç içe varlık filtreleme örneği +#### Nested Entity Filtering İç içe varlıklara göre filtreleme, `_` son ekine sahip alanlarda mümkündür. @@ -200,11 +214,11 @@ Bu, yalnızca alt düzey varlıkları sağlanan koşulları karşılayan varlık } ``` -#### Mantıksal operatörler +### Logical Operators Graph Düğümü [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) sürümünden itibaren, birden fazla kritere dayalı sonuçları filtrelemek için aynı `where` argümanı içinde birden çok parametreyi `and` veya `or` operatörleriyle gruplayabilirsiniz. -##### `AND` Operatörü +#### Using `and` Operator Aşağıdaki örnek, `outcome` değeri `succeeded` olan ve `number` alanı `100` veya daha büyük olan challenge'ları filtreler. @@ -234,7 +248,7 @@ Aşağıdaki örnek, `outcome` değeri `succeeded` olan ve `number` alanı `100` > } > ``` -##### `OR` Operatörü +#### Using `or` Operator Aşağıdaki örnek, `outcome` değeri `succeeded` olan veya `number` alanı `100` veya daha büyük olan challenge'ları filtreler. @@ -250,7 +264,7 @@ Aşağıdaki örnek, `outcome` değeri `succeeded` olan veya `number` alanı `10 } ``` -> **Not:** Sorguları oluştururken `or` operatörünün performans üzerindeki etkisini dikkate almak önemlidir. `or`, arama sonuçlarını genişletmek için faydalı bir araç olsa da, ciddi performans maliyetlerine yol açabilir. `or` operatörünün başlıca sorunlarından biri, sorguların yavaşlamasına neden olmasıdır. Bunun nedeni, `or` kullanıldığında veritabanının birden fazla endeksi taramak zorunda kalmasıdır; bu da zaman alıcı bir işlemdir. Bu tür sorunlardan kaçınmak için geliştiricilere mümkün olduğunca `or` yerine `and` operatörlerini kullanmaları önerilir. Bu sayede daha hassas filtreleme yapılabilir ve sorgular daha hızlı ve doğru şekilde çalışabilir. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### Tüm Filtreler @@ -287,7 +301,7 @@ Ayrıca, `where` argümanının bir parçası olarak aşağıdaki genel filtrele _change_block(number_gte: Int) ``` -### Zaman yolculuğu sorguları +### Time-travel Queries Varlıklarınızın durumunu en son blok için (varsayılan), ya da geçmişteki herhangi bir blok için sorgulayabilirsiniz. Sorgunun hangi blokta yapılacağını belirtmek için, üst seviye sorgu alanlarında `block` argümanı eklenerek ilgili blok numarası veya blok hash’i kullanılabilir. @@ -295,7 +309,7 @@ Böyle bir sorgunun sonucu zamanla değişmez; yani, geçmişteki belirli bir bl > **Not:** Mevcut uygulama, bu güvenceleri ihlal edebilecek bazı sınırlamalara hâlâ tabidir. Uygulama, verilen bir blok hash’inin ana zincirde yer almadığını her zaman tespit edemez veya henüz kesin (final) olarak kabul edilmeyen bir blok için yapılan bir blok hash sorgusunun, sorgu ile eşzamanlı olarak gerçekleşen bir zincir yeniden düzenlemesinden etkilenip etkilenmeyeceğini öngöremez. Ancak bu sınırlamalar, blok kesinleşmiş ve ana zincirde yer aldığı biliniyorsa, blok hash ile yapılan sorguların sonuçlarını etkilemez. Bu sınırlamalar hakkında ayrıntılı bilgi için [bu GitHub issue'su](https://github.com/graphprotocol/graph-node/issues/1405) incelenebilir. -#### Örnek +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ Böyle bir sorgunun sonucu zamanla değişmez; yani, geçmişteki belirli bir bl Bu sorgu, blok numarası 8.000.000 işlendiği andan hemen sonraki halleriyle `Challenge` varlıklarını ve bunlara bağlı `Application` varlıklarını döndürecektir. -#### Örnek - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ Bu sorgu, blok numarası 8.000.000 işlendiği andan hemen sonraki halleriyle `C Bu sorgu, verilen hash’e sahip blok işlendiği andan hemen sonraki halleriyle `Challenge` varlıklarını ve bunlara bağlı `Application` varlıklarını döndürecektir. -### Tam Metin Arama Sorguları +### Full-text Search Queries -Tam metin arama sorgu alanları, Subgraph şemasına eklenebilen ve özelleştirilebilen gelişmiş bir metin arama API’si sağlar. Subgraph'inize tam metin arama eklemek için [Tam Metin Arama Alanlarını Tanımlama](/developing/creating-a-subgraph/#defining-fulltext-search-fields) bölümüne bakın. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Tam metin arama sorgularında, arama terimlerinin girildiği zorunlu bir `text` alanı bulunur. Bu `text` arama alanında kullanılabilecek çeşitli özel tam metin operatörleri mevcuttur. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Tam metin arama operatörleri: +Full-text search operators: -| Sembol | Operatör | Tanım | -| --- | --- | --- | -| `&` | `And` | Sağlanan tüm arama terimlerini içeren varlıkları filtrelemek için birden fazla arama terimini birleştirir | -| | | `Or` | Or (veya) operatörüyle ayrılmış birden fazla arama terimi içeren sorgular, sağlanan terimlerden herhangi biriyle eşleşen tüm varlıkları döndürür | -| `<->` | `Follow by` | İki kelime arasındaki mesafeyi belirtmeyi sağlar. | -| `:*` | `Prefix` | Ön eki (Prefix'i) eşleşen kelimeleri bulmak için ön ek arama terimini kullanın (en az 2 karakter gereklidir). | +| Sembol | Operatör | Tanım | | +| ------ | ----------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | Sağlanan tüm arama terimlerini içeren varlıkları filtrelemek için birden fazla arama terimini birleştirir | | +| | | `Or` | Or (veya) operatörüyle ayrılmış birden fazla arama terimi içeren sorgular, sağlanan terimlerden herhangi biriyle eşleşen tüm varlıkları döndürür | +| `<->` | `Follow by` | İki kelime arasındaki mesafeyi belirtmeyi sağlar. | | +| `:*` | `Prefix` | Ön eki (Prefix'i) eşleşen kelimeleri bulmak için ön ek arama terimini kullanın (en az 2 karakter gereklidir). | | -#### Örnekler +#### Full-text Query Examples -`or` operatörü kullanılarak yapılan bu sorgu, tam metin alanlarında "anarchism" veya "crumpet" kelimelerinin varyasyonlarını içeren blog varlıklarını döndürecektir. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Tam metin arama operatörleri: } ``` -`follow by` operatörü, tam metin belgelerinde belirli bir mesafe ile birbirini izleyen kelimeleri belirtir. Aşağıdaki sorgu, "decentralize" kelimesinin varyasyonları ardından belirli bir mesafede "philosophy" kelimesini içeren tüm blogları döndürecektir. +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ Tam metin arama operatörleri: } ``` -Daha karmaşık filtreler oluşturmak için tam metin operatörlerini birleştirin. Bu örnek sorgu, bir pretext arama işleci ile bir follow by işlecini birleştirerek "lou" ile başlayan ve ardından "music" ile devam eden sözcükleri içeren tüm blog varlıklarıyla eşleşecektir. +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Daha karmaşık filtreler oluşturmak için tam metin operatörlerini birleştir Graph Düğümü, [graphql-js referans uygulamasını](https://github.com/graphql/graphql-js/tree/main/src/validation) temel alan [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules)'yi kullanarak aldığı GraphQL sorgularının [spesifikasyon tabanlı](https://spec.graphql.org/October2021/#sec-Validation) doğrulamasını gerçekleştirir. Bir doğrulama kuralını geçemeyen sorgular standart bir hata ile sonuçlanır. Daha fazla bilgi için [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation)'i ziyaret edin. -## Şema - -Veri kaynaklarınızın şeması, yani sorgulanabilir olan entity türleri, değerler ve ilişkiler, [GraphQL Arayüz Tanım Dili (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System) kullanılarak tanımlanır. - -GraphQL şemaları genellikle `queries`, `subscriptions` ve `mutations` için kök türleri tanımlar. The Graph yalnızca `queries` desteği sunar. Subgraph’iniz için kök `Query` türü, [Subgraph manifesto](/developing/creating-a-subgraph/#components-of-a-subgraph) dosyanıza dahil edilen GraphQL şemasından otomatik olarak oluşturulur. - -> Not: API'miz mutation (mutasyon) işlemlerini desteklemez, çünkü geliştiricilerin kendi uygulamaları üzerinden doğrudan temel blokzincirine işlem göndermeleri beklenir. - -### Varlıklar - -Şemanızda `@entity` yönergesiyle tanımlanan tüm GraphQL türleri varlık olarak kabul edilir ve bir `ID` alanına sahip olmaları gerekir. - -> **Not:** Şu anda, şemanızdaki tüm türlerin `@entity` yönergesine sahip olması gerekir. Gelecekte, `@entity` yönergesi olmayan türler değer nesnesi olarak değerlendirilecek, ancak bu henüz desteklenmemektedir. - ### Subgraph Üst Verisi Tüm Subgraph'lerde, Subgraph metadatasına erişim sağlayan otomatik olarak oluşturulmuş bir `_Meta_` nesnesi bulunur. Buna aşağıdaki şekilde sorgu yapabilirsiniz: From 08610750ca8d933bf77bb205ae6fa08eec970a4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:52 -0400 Subject: [PATCH 264/290] New translations graphql-api.mdx (Ukrainian) --- .../uk/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/uk/subgraphs/querying/graphql-api.mdx b/website/src/pages/uk/subgraphs/querying/graphql-api.mdx index e10201771989..6ff6a8777ce9 100644 --- a/website/src/pages/uk/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/uk/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Example +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Example - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | Description | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | Description | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 39a5025779d0c66d86629117c9b2856c944b31ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:56 -0400 Subject: [PATCH 265/290] New translations graphql-api.mdx (Chinese Simplified) --- .../zh/subgraphs/querying/graphql-api.mdx | 104 +++++++++--------- 1 file changed, 51 insertions(+), 53 deletions(-) diff --git a/website/src/pages/zh/subgraphs/querying/graphql-api.mdx b/website/src/pages/zh/subgraphs/querying/graphql-api.mdx index 0e408a66bc0d..caa006a14d9e 100644 --- a/website/src/pages/zh/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/zh/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -了解在The Graph中使用的 GraphQL 查询 API。 +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## 什么是GraphQL？ [GraphQL](https://graphql.org/learn/)是API的查询语言，也是用您现有数据执行这些查询的运行时间。The Graph使用GraphQL查询子图。 -要理解GraphQL所起的更大作用，请查看 [developing](/subgraphs/developing/introduction/) 和 [创建一个子图](/developing/creating-a-subgraph/)。 +## Core Concepts + +### 实体 + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### 模式 + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## 用GraphQL查询 -在你的子图模式中，定义了叫做`Entities`的类型。对于每个`Entity`类型，`entity` 和 `entities`字段将生成在顶级`Query`类型上。 +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> 注意：在使用The Graph时，`query` 不需要包含在`graphql`查询的顶部。 +### Example Queries -### 例子 +> 注意：在使用The Graph时，`query` 不需要包含在`graphql`查询的顶部。 查询在您的模式中定义的单个`Token`实体： @@ -44,7 +58,7 @@ title: GraphQL API ### 排序 -查询集合时，您可以： +When querying a collection, you can: - 使用 `orderBy` 参数按特定属性排序。 - 使用 `orderDirection` 来指定排序方向, `asc` 用于升序或 `desc` 用于降序。 @@ -60,7 +74,7 @@ title: GraphQL API } ``` -#### 嵌套实体筛选示例 +#### Example for Nested Entity Sorting 从Graph节点[`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) 可以根据嵌套实体排序。 @@ -88,7 +102,7 @@ title: GraphQL API - 使用 `skip` 参数跳过实体和分页。例如，`first:100` 会显示前100个实体，`first:100, skip:100`会显示后100个实体。 - 避免在查询中使用 `skip` 值，因为它们通常表现很差。 要检索大量条目，最好是通过上面示例中显示的属性的实体进行查找。 -#### 使用 `first` 示例 +#### Example Using `first` 查询前10 个代币： @@ -101,9 +115,9 @@ title: GraphQL API } ``` -查询集合中间的实体群组， `skip`参数可以与 `first`参数一起使用，以跳过从集合开始的指定数量的实体。 +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### 使用 `first` 和 `skip` 的示例 +#### Example Using `first` and `skip` 查询 10 `Token` 实体，由集合开始时的10个地方抵消： @@ -116,7 +130,7 @@ title: GraphQL API } ``` -#### 使用 `first` 和 `id_ge` 的示例 +#### Example Using `first` and `id_ge` 如果客户端需要检索大量实体，则基于属性进行查询和过滤会明显提高性能。 例如，客户端可以使用以下查询检索大量代币： @@ -136,9 +150,9 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last - 您可以在查询中使用 `where` 参数来过滤不同的属性。 - 您可以在 `where` 参数中筛选多个值。 -#### 使用 `where` 的示例 +#### Using `where` Filtering -使用 '失败的' 结果查询挑战： +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last 你可以使用后缀，例如`_gt`, `_lte`来进行值比较： -#### 范围过滤示例 +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last } ``` -#### 区块过滤示例 +#### Block Filtering 您也可以筛选在指定的区块中或之后更新的实体使用 `_change_block(number_gte: Int)`。 @@ -182,9 +196,9 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last } ``` -#### 嵌套实体筛选示例 +#### Nested Entity Filtering -在后缀是\`\_'的字段中可以根据嵌套的实体进行过滤。 +在后缀是\`_'的字段中可以根据嵌套的实体进行过滤。 如果您希望只获取其子级实体满足条件的实体，那么这可能很有用。 @@ -200,11 +214,11 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last } ``` -#### 逻辑运算符 +### Logical Operators 对于Graph节点[`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0)，您可以在同一个`where`参数中使用`and`或`or`运算符，根据多个标准过滤结果。 -##### `AND`运算符 +#### Using `and` Operator 下面的示例对大于或等于`100`的`outcome`、`successed`和`number`的挑战进行过滤。 @@ -234,7 +248,7 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last > } > ``` -##### `OR`运算符 +#### Using `or` Operator 下面的示例对大于或等于`100`的`outcome`、`successed`和`number`的挑战进行过滤。 @@ -250,7 +264,7 @@ query manyTokens($lastID: String) { tokens(first: 1000, where: { id_gt: $last } ``` -> **注意**：在构建查询时，重要的是要考虑使用`or`运算符的性能影响。 虽然`or`可以成为扩大搜索结果的一个有用工具，但它也可能有很高的费用。 `or`的主要问题之一是它可能导致查询减缓。 这是因为`or`需要数据库通过多个索引进行扫描，这可能是一个耗时的过程。 为了避免这些问题，建议开发人员使用和操作人员，而不是在任何可能的情况下使用。 这样可以进行更精确的过滤，可以更快、更准确的查询。 +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### 所有过滤器 @@ -287,7 +301,7 @@ _not_ends_with_nocase _change_block(number_gte: Int) ``` -### 跨时间查询 +### Time-travel Queries 您可以查询您的实体状态，不仅仅是为了最新的区块， 它是默认的，但也是过去的任意区块的。 可以在查询的顶级字段中包含一个 ' block' 参数来指定查询的要么用其区块编号或区块哈希。 @@ -295,7 +309,7 @@ _change_block(number_gte: Int) > 请注意，当前的实现仍然受到某些限制，这些限制可能会违反这些保证。该实现不能总是判断给定的区块哈希根本不在主链上，或者对于一个不能被认为是最终的区块，逐块哈希查询的结果可能会受到与查询同时运行的区块重组的影响。当区块是最终区块并且已知在主链上时，它们不会影响区块哈希查询的结果。[这个](https://github.com/graphprotocol/graph-node/issues/1405)问题详细解释了这些限制是什么。 -#### 示例 +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ _change_block(number_gte: Int) 此查询将返回 `Challenge` 实体及其关联的 `Application` 实体，因为它们在处理8,000,000个区块后就存在了。 -#### 示例 - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ _change_block(number_gte: Int) 此查询将返回 `Challenge` 实体及其关联的 `Application` 实体，因为它们在处理具有给定哈希值的区块后就存在了。 -### 全文搜索查询 +### Full-text Search Queries -全文搜索查询字段提供了一个表达性的文本搜索 API，可以添加到子图模式中并进行自定义。 请参阅[定义全文搜索字段](/developing/creating-a-subgraph/#defining-fulltext-search-fields)以将全文搜索添加到您的子图中。 +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -全文搜索查询有一个必填字段 `text`，用于提供搜索词。 在这个 `text` 搜索字段中可以使用几个特殊的全文运算符。 +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -全文搜索运算符： +Full-text search operators: -| 符号 | 运算符 | 描述 | -| ------ | ----------- | ---------------------------------------------------------------------- | -| `&` | `And` | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中 | -| | | `Or` | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 | -| `<->` | `Follow by` | 指定两个单词之间的距离。 | -| `:*` | `Prefix` | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符） | +| 符号 | 运算符 | 描述 | | +| ----- | ----------- | --------------------------- | ------------------------------------- | +| `&` | `And` | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中 | | +| | | `Or` | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 | +| `<->` | `Follow by` | 指定两个单词之间的距离。 | | +| `:*` | `Prefix` | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符） | | -#### 例子 +#### Full-text Query Examples -使用 `or` 运算符，这个查询将过滤到在其全文字段中具有"anarchism" or "crumpet"变化的博客实体。 +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ _change_block(number_gte: Int) } ``` -`follow by` 运算符指定全文文档中相隔特定距离的单词。 以下查询将返回所有“decentralize”后跟着“philosophy”变体的日志。 +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ _change_block(number_gte: Int) } ``` -可以将全文运算符进行组合来制作更复杂的过滤器。 在下面的查询示例中，使用前缀搜索运算符与其他运算符的结合，可以实现匹配所有以“lou”开头后，跟着“music”单词的日志实体。 +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ _change_block(number_gte: Int) Graph节点实现使用 [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules)验证它收到的 GraphQL 查询的 [specification-based](https://spec.graphql.org/October2021/#sec-Validation) 验证基于 [graphql-js 参考实现](https://github.com/graphql/graphql-js/tree/main/src/validation)。 查询失败的验证规则有一个标准错误 - 请访问 [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation)来了解更多信息。 -## 模式 - -您的数据源模式，例如可用于查询的实体类型、值和关系是通过 [GraphQL 接口定义语言(IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System)定义的。 - -GraphQL模式通常定义`查询`、`订阅`和`突变`的根类型。The Graph仅支持`查询`。子图的根`查询`类型是从[子图清单](/developing/creating-a-subgraph/#components-of-a-subgraph)中包含的GraphQL模式自动生成的。 - -> 注意：我们的 API 不提供对突变的支持，因为开发人员会从他们的应用程序中直接针对底层区块链发出交易。 - -### 实体 - -模式定义中所有带有 `@entity` 指示的 GraphQL 类型都将被视为实体，并且必须具有 `ID` 字段。 - -> **注意：** 目前，您的模式中的所有类型都必须有一个 `@entity` 指令。 今后，我们将把没有`@entity`指令的类型视为值对象，但这还不被支持。 - ### 子图元数据 所有子图都有一个自动生成的`_Meta_`对象，它提供对子图元数据的访问。可按如下方式查询： From 2b24952aff367796caa6d2ec3511f15e07d243ef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:57 -0400 Subject: [PATCH 266/290] New translations graphql-api.mdx (Urdu (Pakistan)) --- .../ur/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/ur/subgraphs/querying/graphql-api.mdx b/website/src/pages/ur/subgraphs/querying/graphql-api.mdx index 79ecfe95c599..9f9117c00b19 100644 --- a/website/src/pages/ur/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/ur/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### ہستیوں + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### سکیما + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### مثالیں +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### سورٹنگ -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### نیسٹڈ ہستی کی چھانٹی کی مثال +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` پہلے 10 ٹوکنز سے کیوری کریں: @@ -101,9 +115,9 @@ When querying a collection, it's best to: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### رینج فلٹرنگ کی مثال +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### بلاک فلٹرنگ کی مثال +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### نیسٹڈ ہستی فلٹرنگ کی مثال +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ Filtering on the basis of nested entities is possible in the fields with the `_` } ``` -#### منطقی آپریٹرز +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### تمام فلٹرز @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### ٹائم ٹریول کے کیوریز +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### مثال +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### مثال - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### فل ٹیکسٹ تلاش کے کیوریز +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -فل ٹیکسٹ سرچ آپریٹرز: +Full-text search operators: -| علامت | آپریٹر | تفصیل | -| --- | --- | --- | -| `&` | `And` | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں | -| | | `Or` | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے | -| `<->` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں. | -| `:*` | `Prefix` | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.) | +| علامت | آپریٹر | تفصیل | | +| ----- | ----------- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں | | +| | | `Or` | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے | +| `<->` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں. | | +| `:*` | `Prefix` | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.) | | -#### مثالیں +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -مزید پیچیدہ فلٹرز بنانے کے لیے فل ٹیکسٹ آپریٹرز کو یکجا کریں۔ ایک بہانہ سرچ آپریٹر کے ساتھ اس مثال کے کیوری کی پیروی کے ساتھ مل کر بلاگ کے تمام ہستیوں کو ایسے الفاظ سے مماثل کرے گا جو "lou" کے بعد "موسیقی" سے شروع ہوتے ہیں. +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ The `follow by` operator specifies a words a specific distance apart in the full Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## سکیما - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### ہستیوں - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### سب گراف میٹا ڈیٹا All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 7c0c93fbf4745bab7022c55f77a03b73311a827a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:58 -0400 Subject: [PATCH 267/290] New translations graphql-api.mdx (Vietnamese) --- .../vi/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/vi/subgraphs/querying/graphql-api.mdx b/website/src/pages/vi/subgraphs/querying/graphql-api.mdx index 65547da41195..0b7fc21754b0 100644 --- a/website/src/pages/vi/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/vi/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Lược đồ + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### Ví dụ +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### Ví dụ - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Biểu tượng | Toán tử | Miêu tả | -| --- | --- | --- | -| `&` | `And` | Để kết hợp nhiều cụm từ tìm kiếm thành một bộ lọc cho các thực thể bao gồm tất cả các cụm từ được cung cấp | -| | | `Or` | Các truy vấn có nhiều cụm từ tìm kiếm được phân tách bằng toán tử hoặc sẽ trả về tất cả các thực thể có kết quả khớp với bất kỳ cụm từ nào được cung cấp | -| `<->` | `Follow by` | Chỉ định khoảng cách giữa hai từ. | -| `:*` | `Prefix` | Sử dụng cụm từ tìm kiếm tiền tố để tìm các từ có tiền tố khớp với nhau (yêu cầu 2 ký tự.) | +| Biểu tượng | Toán tử | Miêu tả | | +| ---------- | ----------- | ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `&` | `And` | Để kết hợp nhiều cụm từ tìm kiếm thành một bộ lọc cho các thực thể bao gồm tất cả các cụm từ được cung cấp | | +| | | `Or` | Các truy vấn có nhiều cụm từ tìm kiếm được phân tách bằng toán tử hoặc sẽ trả về tất cả các thực thể có kết quả khớp với bất kỳ cụm từ nào được cung cấp | +| `<->` | `Follow by` | Chỉ định khoảng cách giữa hai từ. | | +| `:*` | `Prefix` | Sử dụng cụm từ tìm kiếm tiền tố để tìm các từ có tiền tố khớp với nhau (yêu cầu 2 ký tự.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Lược đồ - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From ee2aac253dc887b61824736ea117bb15a16eacdb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:33:59 -0400 Subject: [PATCH 268/290] New translations graphql-api.mdx (Marathi) --- .../mr/subgraphs/querying/graphql-api.mdx | 102 +++++++++--------- 1 file changed, 50 insertions(+), 52 deletions(-) diff --git a/website/src/pages/mr/subgraphs/querying/graphql-api.mdx b/website/src/pages/mr/subgraphs/querying/graphql-api.mdx index 049248616399..fb8c43d4fc0c 100644 --- a/website/src/pages/mr/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/mr/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: GraphQL API --- -Learn about the GraphQL Query API used in The Graph. +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## What is GraphQL? [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query Subgraphs. -To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a Subgraph](/developing/creating-a-subgraph/). +## Core Concepts + +### Entities + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### Schema + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## Queries with GraphQL -In your Subgraph schema you define types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. +### Example Queries -### Examples +> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph. Query for a single `Token` entity defined in your schema: @@ -44,7 +58,7 @@ Query all `Token` entities: ### Sorting -When querying a collection, you may: +When querying a collection, you can: - Use the `orderBy` parameter to sort by a specific attribute. - Use the `orderDirection` to specify the sort direction, `asc` for ascending or `desc` for descending. @@ -60,7 +74,7 @@ When querying a collection, you may: } ``` -#### Example for nested entity sorting +#### Example for Nested Entity Sorting As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) entities can be sorted on the basis of nested entities. @@ -88,7 +102,7 @@ When querying a collection, it's best to: - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities. - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above. -#### Example using `first` +#### Example Using `first` Query the first 10 tokens: @@ -101,9 +115,9 @@ Query the first 10 tokens: } ``` -To query for groups of entities in the middle of a collection, the `skip` parameter may be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### Example using `first` and `skip` +#### Example Using `first` and `skip` Query 10 `Token` entities, offset by 10 places from the beginning of the collection: @@ -116,7 +130,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect } ``` -#### Example using `first` and `id_ge` +#### Example Using `first` and `id_ge` If a client needs to retrieve a large number of entities, it's more performant to base queries on an attribute and filter by that attribute. For example, a client could retrieve a large number of tokens using this query: @@ -136,9 +150,9 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r - You can use the `where` parameter in your queries to filter for different properties. - You can filter on multiple values within the `where` parameter. -#### Example using `where` +#### Using `where` Filtering -Query challenges with `failed` outcome: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -154,7 +168,7 @@ Query challenges with `failed` outcome: You can use suffixes like `_gt`, `_lte` for value comparison: -#### Example for range filtering +#### Range Filtering ```graphql { @@ -166,7 +180,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison: } ``` -#### Example for block filtering +#### Block Filtering You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`. @@ -182,7 +196,7 @@ This can be useful if you are looking to fetch only entities which have changed, } ``` -#### Example for nested entity filtering +#### Nested Entity Filtering Filtering on the basis of nested entities is possible in the fields with the `_` suffix. @@ -200,11 +214,11 @@ This can be useful if you are looking to fetch only entities whose child-level e } ``` -#### Logical operators +### Logical Operators As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) you can group multiple parameters in the same `where` argument using the `and` or the `or` operators to filter results based on more than one criteria. -##### `AND` Operator +#### Using `and` Operator The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`. @@ -234,7 +248,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num > } > ``` -##### `OR` Operator +#### Using `or` Operator The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`. @@ -250,7 +264,7 @@ The following example filters for challenges with `outcome` `succeeded` or `numb } ``` -> **Note**: When constructing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### All Filters @@ -287,7 +301,7 @@ In addition, the following global filters are available as part of `where` argum _change_block(number_gte: Int) ``` -### Time-travel queries +### Time-travel Queries You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries. @@ -295,7 +309,7 @@ The result of such a query will not change over time, i.e., querying at a certai > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### उदाहरण +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ The result of such a query will not change over time, i.e., querying at a certai This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing block number 8,000,000. -#### उदाहरण - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ This query will return `Challenge` entities, and their associated `Application` This query will return `Challenge` entities, and their associated `Application` entities, as they existed directly after processing the block with the given hash. -### Fulltext Search Queries +### Full-text Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your Subgraph. +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -Fulltext search operators: +Full-text search operators: -| Symbol | Operator | वर्णन | -| --- | --- | --- | -| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | -| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | -| `<->` | `Follow by` | Specify the distance between two words. | -| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | +| Symbol | Operator | वर्णन | | +| ------ | ----------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms | | +| | | `Or` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms | +| `<->` | `Follow by` | Specify the distance between two words. | | +| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) | | -#### Examples +#### Full-text Query Examples -Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields. +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Using the `or` operator, this query will filter to blog entities with variations } ``` -The `follow by` operator specifies a words a specific distance apart in the fulltext documents. The following query will return all blogs with variations of "decentralize" followed by "philosophy" +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ The `follow by` operator specifies a words a specific distance apart in the full } ``` -Combine fulltext operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Combine fulltext operators to make more complex filters. With a pretext search o Graph Node implements [specification-based](https://spec.graphql.org/October2021/#sec-Validation) validation of the GraphQL queries it receives using [graphql-tools-rs](https://github.com/dotansimha/graphql-tools-rs#validation-rules), which is based on the [graphql-js reference implementation](https://github.com/graphql/graphql-js/tree/main/src/validation). Queries which fail a validation rule do so with a standard error - visit the [GraphQL spec](https://spec.graphql.org/October2021/#sec-Validation) to learn more. -## Schema - -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). - -GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your Subgraph is automatically generated from the GraphQL schema that's included in your [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). - -> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications. - -### Entities - -All GraphQL types with `@entity` directives in your schema will be treated as entities and must have an `ID` field. - -> **Note:** Currently, all types in your schema must have an `@entity` directive. In the future, we will treat types without an `@entity` directive as value objects, but this is not yet supported. - ### Subgraph Metadata All Subgraphs have an auto-generated `_Meta_` object, which provides access to Subgraph metadata. This can be queried as follows: From 839ae7d52f0d358c29ea78e0905c5237de37a459 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Wed, 23 Apr 2025 16:34:00 -0400 Subject: [PATCH 269/290] New translations graphql-api.mdx (Hindi) --- .../hi/subgraphs/querying/graphql-api.mdx | 118 +++++++++--------- 1 file changed, 58 insertions(+), 60 deletions(-) diff --git a/website/src/pages/hi/subgraphs/querying/graphql-api.mdx b/website/src/pages/hi/subgraphs/querying/graphql-api.mdx index a0e9da503a74..761e645fc479 100644 --- a/website/src/pages/hi/subgraphs/querying/graphql-api.mdx +++ b/website/src/pages/hi/subgraphs/querying/graphql-api.mdx @@ -2,21 +2,35 @@ title: ग्राफक्यूएल एपीआई --- -The Graph में उपयोग किए जाने वाले GraphQL Query API के बारे में जानें। +Explore the GraphQL Query API for interacting with Subgraphs on The Graph Network. ## GraphQL क्या है? [GraphQL](https://graphql.org/learn/) एक API के लिए क्वेरी भाषा है और मौजूदा डेटा के साथ उन क्वेरियों को निष्पादित करने के लिए एक रनटाइम है। The Graph, GraphQL का उपयोग करके Subgraphs से क्वेरी करता है। -To समझने के लिए कि GraphQL बड़ी भूमिका कैसे निभाता है, [developing](/subgraphs/developing/introduction/) और [creating a Subgraph](/developing/creating-a-subgraph/) की समीक्षा करें। +## Core Concepts + +### इकाइयां + +- **What they are**: Persistent data objects defined with `@entity` in your schema +- **Key requirement**: Must contain `id: ID!` as primary identifier +- **Usage**: Foundation for all query operations + +### योजना + +- **Purpose**: Blueprint defining the data structure and relationships using GraphQL [IDL](https://facebook.github.io/graphql/draft/#sec-Type-System) +- **Key characteristics**: + - Auto-generates query endpoints + - Read-only operations (no mutations) + - Defines entity interfaces and derived fields ## GraphQL के साथ क्वेरीज़ -आपकी Subgraph schema में `Entities` नामक प्रकारों को परिभाषित किया जाता है। प्रत्येक `Entity` प्रकार के लिए, शीर्ष-स्तरीय Query प्रकार पर `entity` और `entities` फ़ील्ड जेनरेट की जाएंगी। +In the Subgraph schema, types called `Entities`. For each `Entity` type, `entity` and `entities` fields will be generated on the top-level `Query` type. -> ध्यान दें: 'queries' को The Graph का उपयोग करते समय 'graphql' क्वेरी के शीर्ष पर शामिल करने की आवश्यकता नहीं है। +### Example Queries -### उदाहरण +> ध्यान दें: 'queries' को The Graph का उपयोग करते समय 'graphql' क्वेरी के शीर्ष पर शामिल करने की आवश्यकता नहीं है। एकल 'Token' एंटिटी के लिए क्वेरी करें जो आपके स्कीमा में परिभाषित है @@ -44,7 +58,7 @@ To समझने के लिए कि GraphQL बड़ी भूमिक ### Her translation means sorting out -जब आप एक संग्रह के लिए क्वेरी कर रहे हों, तो आप: +When querying a collection, you can: - 'orderBy' पैरामीटर का उपयोग किसी विशिष्ट गुण द्वारा सॉर्ट करने के लिए करें। - 'orderDirection' का उपयोग सॉर्ट दिशा निर्दिष्ट करने के लिए करें, 'asc' के लिए आरोही या 'desc' के लिए अवरोही। @@ -60,7 +74,7 @@ To समझने के लिए कि GraphQL बड़ी भूमिक } ``` -#### नेस्टेड इकाई छँटाई के लिए उदाहरण +#### Example for Nested Entity Sorting Graph Node ['v0.30.0'](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) के अनुसार, entities को nested entities के आधार पर क्रमबद्ध किया जा सकता है। @@ -88,7 +102,7 @@ Graph Node ['v0.30.0'](https://github.com/graphprotocol/graph-node/releases/tag/ - `skip` पैरामीटर का उपयोग entities को स्किप करने और पेजिनेट करने के लिए करें। instancesके लिए, first:100 पहले 100 entities दिखाता है और first:100, skip:100 अगले 100 entities दिखाता है। - `skip` मानों का उपयोग queries में करने से बचें क्योंकि ये सामान्यतः खराब प्रदर्शन करते हैं। एक बड़ी संख्या में आइटम प्राप्त करने के लिए, पिछले उदाहरण में दिखाए गए अनुसार किसी गुण के आधार पर entities के माध्यम से पेज करना सबसे अच्छा होता है। -#### उदाहरण जो `first` का उपयोग करता है +#### Example Using `first` पहले 10 टोकन पूछें: @@ -101,9 +115,9 @@ Graph Node ['v0.30.0'](https://github.com/graphprotocol/graph-node/releases/tag/ } ``` -संग्रह के मध्य में स्थित entities के समूहों के लिए queries करने के लिए, `skip` पैरामीटर को `first` पैरामीटर के साथ उपयोग किया जा सकता है, ताकि संग्रह की शुरुआत से निर्धारित संख्या में entities को छोड़ दिया जा सके। +To query for groups of entities in the middle of a collection, the `skip` parameter can be used in conjunction with the `first` parameter to skip a specified number of entities starting at the beginning of the collection. -#### `first` और `skip` का उपयोग करते हुए उदाहरण +#### Example Using `first` and `skip` कलेक्शन की शुरुआत से 10 स्थानों के बाद 10 `Token` entities को queries करें। @@ -116,7 +130,7 @@ Graph Node ['v0.30.0'](https://github.com/graphprotocol/graph-node/releases/tag/ } ``` -#### उदाहरण 'first' और 'id_ge' का उपयोग करते हुए। +#### Example Using `first` and `id_ge` यदि एक क्लाइंट को बड़ी संख्या में एंटिटीज़ पुनर्प्राप्त करने की आवश्यकता है, तो एट्रिब्यूट पर आधारित क्वेरी बनाना और उस एट्रिब्यूट द्वारा फ़िल्टर करना अधिक प्रभावशाली है। उदाहरण के लिए, एक क्लाइंट इस क्वेरी का उपयोग करके बड़ी संख्या में टोकन पुनर्प्राप्त कर सकता है: @@ -136,9 +150,9 @@ query manyTokens($lastID: String) { - आप अपनी क्वेरी में विभिन्न गुणों को फ़िल्टर करने के लिए 'where' पैरामीटर का उपयोग कर सकते हैं। - आप 'where' पैरामीटर के भीतर कई मानों पर फ़िल्टर कर सकते हैं। -#### उदाहरण 'where' का उपयोग करते हुए +#### Using `where` Filtering -'failed' परिणाम वाली क्वेरी चुनौतियाँ: +Query challenges with `failed` outcome using 'where' filter: ```graphql { @@ -152,9 +166,9 @@ query manyTokens($lastID: String) { } ``` -आप मूल्य तुलना के लिए '\_gt' , '\_lte' जैसे प्रत्ययों का उपयोग कर सकते हैं। +आप मूल्य तुलना के लिए '_gt' , '_lte' जैसे प्रत्ययों का उपयोग कर सकते हैं। -#### श्रेणी फ़िल्टरिंग के लिए उदाहरण +#### Range Filtering ```graphql { @@ -166,9 +180,9 @@ query manyTokens($lastID: String) { } ``` -#### ब्लॉक फ़िल्टरिंग के लिए उदाहरण +#### Block Filtering -आप उन इकाइयों entities को भी फ़िल्टर कर सकते हैं जिन्हें किसी निर्दिष्ट ब्लॉक में या उसके बाद अपडेट किया गया था, '\_change_block(number_gte: Int)' के साथ। +आप उन इकाइयों entities को भी फ़िल्टर कर सकते हैं जिन्हें किसी निर्दिष्ट ब्लॉक में या उसके बाद अपडेट किया गया था, '_change_block(number_gte: Int)' के साथ। यह उपयोगी हो सकता है यदि आप केवल उन entities को लाना चाहते हैं जो बदल गई हैं, उदाहरण के लिए, पिछली बार जब आपने पोल किया था तब से। या वैकल्पिक रूप से, यह जांचने या डिबग करने के लिए उपयोगी हो सकता है कि आपकी Subgraph में entities कैसे बदल रही हैं (यदि इसे एक ब्लॉक फ़िल्टर के साथ जोड़ा जाए, तो आप केवल उन्हीं entities को अलग कर सकते हैं जो एक विशिष्ट ब्लॉक में बदली हैं)। @@ -182,9 +196,9 @@ query manyTokens($lastID: String) { } ``` -#### नेस्टेड इकाई फ़िल्टरिंग के लिए उदाहरण +#### Nested Entity Filtering -नेस्टेड इकाइयों के आधार पर फ़िल्टरिंग उन फ़ील्ड्स में संभव है जिनके अंत में '\_' प्रत्यय होता है। +नेस्टेड इकाइयों के आधार पर फ़िल्टरिंग उन फ़ील्ड्स में संभव है जिनके अंत में '_' प्रत्यय होता है। यह उपयोगी हो सकता है यदि आप केवल उन संस्थाओं को लाना चाहते हैं जिनके चाइल्ड-स्तरीय निकाय प्रदान की गई शर्तों को पूरा करते हैं। @@ -200,13 +214,13 @@ query manyTokens($lastID: String) { } ``` -#### लॉजिकल ऑपरेटर्स +### Logical Operators ग्राफ-नोड ['v0.30.0'](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) से, आप एक ही 'where' आर्गुमेंट में कई पैरामीटर्स को समूहित कर सकते हैं और 'and' या 'or' ऑपरेटर्स का उपयोग करके एक से अधिक मानदंडों के आधार पर परिणामों को फ़िल्टर कर सकते हैं। -##### `AND` ऑपरेटर +#### Using `and` Operator -निम्नलिखित उदाहरण उन चुनौतियों को फ़िल्टर करता है जिनका `outcome`` succeeded` है और जिनका `number` `100` या उससे अधिक है। +निम्नलिखित उदाहरण उन चुनौतियों को फ़िल्टर करता है जिनका ```outcome`` succeeded``` है और जिनका `number` `100` या उससे अधिक है। ```graphql { @@ -220,7 +234,7 @@ query manyTokens($lastID: String) { } ``` -> **सिंटैक्टिक शुगर**: आप उपरोक्त को queriesसरल बना सकते हैं `and` ऑपरेटर को हटाकर और उप-वाक्यांश को कॉमा से अलग करके पास करके। +> **सिंटैक्टिक शुगर**: आप उपरोक्त को queriesसरल बना सकते हैं `and` ऑपरेटर को हटाकर और उप-वाक्यांश को कॉमा से अलग करके पास करके। > > ```graphql > { @@ -234,7 +248,7 @@ query manyTokens($lastID: String) { > } > ``` -##### `OR` ऑपरेटर। +#### Using `or` Operator निम्नलिखित उदाहरण उन चुनौतियों को फ़िल्टर करता है जिनका `outcome` `succeeded` है या जिनका `number` `100` या उससे अधिक है। @@ -250,7 +264,7 @@ query manyTokens($lastID: String) { } ``` -> **नोट**: queries बनाते समय, `or` ऑपरेटर के उपयोग से होने वाले प्रदर्शन प्रभावों पर विचार करना महत्वपूर्ण है। हालांकि `or` खोज परिणामों को व्यापक बनाने के लिए एक उपयोगी उपकरण हो सकता है, लेकिन इसके कुछ महत्वपूर्ण लागतें भी होती हैं। `or` के साथ मुख्य समस्या यह है कि यह queries को धीमा कर सकता है। इसका कारण यह है कि `or` के उपयोग से डेटाबेस को कई इंडेक्स स्कैन करने पड़ते हैं, जो एक समय-सापेक्ष प्रक्रिया हो सकती है। इन समस्याओं से बचने के लिए, यह अनुशंसा की जाती है कि डेवलपर्स or के बजाय and ऑपरेटर का उपयोग करें जब भी संभव हो। यह अधिक सटीक फ़िल्टरिंग की अनुमति देता है और तेज़, अधिक सटीक queries प्रदान कर सकता है। +> **Note**: When writing queries, it is important to consider the performance impact of using the `or` operator. While `or` can be a useful tool for broadening search results, it can also have significant costs. One of the main issues with `or` is that it can cause queries to slow down. This is because `or` requires the database to scan through multiple indexes, which can be a time-consuming process. To avoid these issues, it is recommended that developers use and operators instead of or whenever possible. This allows for more precise filtering and can lead to faster, more accurate queries. #### सभी फ़िल्टर @@ -279,7 +293,7 @@ _not_ends_with _not_ends_with_nocase ``` -> कुछ प्रत्यय केवल विशिष्ट प्रकारों के लिए समर्थित होते हैं। उदाहरण के लिए, `Boolean` केवल` _not, _in`, और `_not_`in का समर्थन करता है, लेकिन \_ केवल ऑब्जेक्ट और इंटरफेस प्रकारों के लिए उपलब्ध है। +> कुछ प्रत्यय केवल विशिष्ट प्रकारों के लिए समर्थित होते हैं। उदाहरण के लिए, `Boolean` केवल` _not, _in`, और `_not_`in का समर्थन करता है, लेकिन _ केवल ऑब्जेक्ट और इंटरफेस प्रकारों के लिए उपलब्ध है। इसके अलावा, `where` आर्ग्यूमेंट के हिस्से के रूप में निम्नलिखित वैश्विक फ़िल्टर उपलब्ध हैं: @@ -287,15 +301,15 @@ _not_ends_with_nocase _change_block(number_gte: Int) ``` -### समय-यात्रा क्वेरी +### Time-travel Queries -आप न केवल नवीनतम ब्लॉक के लिए, जो डिफ़ॉल्ट होता है, बल्कि अतीत के किसी भी मनमाने ब्लॉक के लिए भी अपनी entities की स्थिति को queries कर सकते हैं। जिस ब्लॉक पर queries होनी चाहिए, उसे या तो उसके ब्लॉक नंबर या उसके ब्लॉक हैश द्वारा निर्दिष्ट किया जा सकता है, इसके लिए queries के शीर्ष स्तर के फ़ील्ड्स में block आर्ग्यूमेंट शामिल किया जाता है। +आप न केवल नवीनतम ब्लॉक के लिए, जो डिफ़ॉल्ट होता है, बल्कि अतीत के किसी भी मनमाने ब्लॉक के लिए भी अपनी entities की स्थिति को queries कर सकते हैं। जिस ब्लॉक पर queries होनी चाहिए, उसे या तो उसके ब्लॉक नंबर या उसके ब्लॉक हैश द्वारा निर्दिष्ट किया जा सकता है, इसके लिए queries के शीर्ष स्तर के फ़ील्ड्स में block आर्ग्यूमेंट शामिल किया जाता है। ऐसे queries का परिणाम समय के साथ नहीं बदलेगा, यानी किसी निश्चित पिछले ब्लॉक परqueries करने से हमेशा वही परिणाम मिलेगा, चाहे इसे कभी भी निष्पादित किया जाए। इसका एकमात्र अपवाद यह है कि यदि आप किसी ऐसे ब्लॉक पर queries करते हैं जो chain के हेड के बहुत करीब है, तो परिणाम बदल सकता है यदि वह ब्लॉक मुख्य chain पर **not** होता है और chain का पुनर्गठन हो जाता है। एक बार जब किसी ब्लॉक को अंतिम (final) माना जा सकता है, तो queries का परिणाम नहीं बदलेगा। > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail. -#### उदाहरण +#### Example Time-travel Queries ```graphql { @@ -311,8 +325,6 @@ _change_block(number_gte: Int) यह queries `Challenge` entities और उनके संबद्ध `Application` entities को लौटाएगी, जैसा कि वे ब्लॉक संख्या 8,000,000 के प्रोसेस होने के ठीक बाद मौजूद थे। -#### उदाहरण - ```graphql { challenges(block: { hash: "0x5a0b54d5dc17e0aadc383d2db43b0a0d3e029c4c" }) { @@ -327,24 +339,24 @@ _change_block(number_gte: Int) यह queries `Challenge` entities और उनसे संबंधित `Application` entities को वापस करेगी, जैसा कि वे दिए गए हैश वाले ब्लॉक को प्रोसेस करने के तुरंत बाद मौजूद थीं। -### पूर्ण पाठ खोज प्रश्न +### Full-text Search Queries -Fulltext search query fields एक अभिव्यक्तिपूर्ण टेक्स्ट खोज API प्रदान करते हैं जिसे Subgraph schema में जोड़ा जा सकता है और अनुकूलित किया जा सकता है। Fulltext search को अपने Subgraph में जोड़ने के लिए [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) देखें। +Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph. -फ़ुलटेक्स्ट सर्च क्वेरीज़ में एक आवश्यक फ़ील्ड होता है, ' text ', जिसमें सर्च शब्द प्रदान किए जाते हैं। इस ' text ' सर्च फ़ील्ड में उपयोग करने के लिए कई विशेष फ़ुलटेक्स्ट ऑपरेटर उपलब्ध हैं। +Full-text search queries have one required field, `text`, for supplying search terms. Several special full-text operators are available to be used in this `text` search field. -पूर्ण पाठ खोज ऑपरेटर: +Full-text search operators: -| प्रतीक | ऑपरेटर | Description | -| --- | --- | --- | -| `&` | `And` | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए | -| | | ' Or' | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी | -| `<->` | ' द्वारा अनुसरण करें ' | दो शब्दों के बीच की दूरी निर्दिष्ट करें। | -| `:*` | ' उपसर्ग ' | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।) | +| प्रतीक | ऑपरेटर | Description | | +| ------ | ---------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `&` | `And` | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए | | +| | | ' Or' | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी | +| `<->` | ' द्वारा अनुसरण करें ' | दो शब्दों के बीच की दूरी निर्दिष्ट करें। | | +| `:*` | ' उपसर्ग ' | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।) | | -#### उदाहरण +#### Full-text Query Examples -' or 'ऑपरेटर का उपयोग करके, यह क्वेरी उन ब्लॉग एंटिटीज़ को फ़िल्टर करेगी जिनके पूर्ण-पाठ (fulltext) फ़ील्ड में "anarchism" या "crumpet" में से किसी एक के विभिन्न रूप शामिल हैं। +Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their full-text fields. ```graphql { @@ -357,7 +369,7 @@ Fulltext search query fields एक अभिव्यक्तिपूर् } ``` -' follow by ' ऑपरेटर पूर्ण-पाठ दस्तावेज़ों में विशिष्ट दूरी पर स्थित शब्दों को निर्दिष्ट करता है। निम्नलिखित क्वेरी उन सभी ब्लॉगों को लौटाएगी जिनमें "विकेंद्रीकृत" के विभिन्न रूप "philosophy" के बाद आते हैं। +The `follow by` operator specifies that two words must appear a specific distance apart in full-text documents.. The following query will return all blogs with variations of "decentralize" followed by "philosophy" ```graphql { @@ -370,7 +382,7 @@ Fulltext search query fields एक अभिव्यक्तिपूर् } ``` -अधिक जटिल फिल्टर बनाने के लिए फुलटेक्स्ट ऑपरेटरों को मिलाएं। इस उदाहरण क्वेरी के अनुसरण के साथ एक बहाना खोज ऑपरेटर संयुक्त रूप से सभी ब्लॉग संस्थाओं को उन शब्दों से मिलाएगा जो "लू" से शुरू होते हैं और उसके बाद "संगीत"। +Combine full-text operators to make more complex filters. With a pretext search operator combined with a follow by this example query will match all blog entities with words that start with "lou" followed by "music". ```graphql { @@ -387,20 +399,6 @@ Fulltext search query fields एक अभिव्यक्तिपूर् Graph Node अपने द्वारा प्राप्त GraphQL क्वेरी की स्पेसिफिकेशन-आधारित(https://spec.graphql.org/October2021/#sec-Validation) वैलिडेशन करता है, जो graphql-tools-rs(https://github.com/dotansimha/graphql-tools-rs#validation-rules) पर आधारित है, जो graphql-js संदर्भ कार्यान्वयन(https://github.com/graphql/graphql-js/tree/main/src/validation) पर आधारित है। क्वेरी जो वैलिडेशन नियम में विफल होती हैं, वे एक मानक त्रुटि के साथ विफल होती हैं - अधिक जानने के लिए GraphQL स्पेसिफिकेशन(https://spec.graphql.org/October2021/#sec-Validation) पर जाएं। -## योजना - -आपके डेटा स्रोतों का स्कीमा, अर्थात् उपलब्ध प्रश्न करने के लिए संस्थाओं की प्रकार, मान और उनके बीच के संबंध, GraphQL Interface Definition Language (IDL)(https://facebook.github.io/graphql/draft/#sec-Type-System) के माध्यम से परिभाषित किए गए हैं। - -GraphQL स्कीमाएँ आमतौर पर queries, subscriptions और mutations के लिए रूट टाइप्स को परिभाषित करती हैं। The Graph केवल queries को सपोर्ट करता है। आपके Subgraph के लिए रूट Query टाइप अपने आप उत्पन्न हो जाता है, जो कि आपके [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph) में शामिल GraphQL स्कीमा से आता है। - -> ध्यान दें: हमारा एपीआई म्यूटेशन को उजागर नहीं करता है क्योंकि डेवलपर्स से उम्मीद की जाती है कि वे अपने एप्लिकेशन से अंतर्निहित ब्लॉकचेन के खिलाफ सीधे लेन-देन(transaction) जारी करेंगे। - -### इकाइयां - -आपके स्कीमा में जिन भी GraphQL प्रकारों में @entity निर्देश होते हैं, उन्हें संस्थाएँ (entities) माना जाएगा और उनमें एक ID फ़ील्ड होना चाहिए। - -> नोट: वर्तमान में, आपकी स्कीमा में सभी प्रकारों में @entity निर्देश होना चाहिए। भविष्य में, हम उन प्रकारों को मूल्य वस्तुएं मानेंगे जिनमें @entity निर्देश नहीं होगा, लेकिन यह अभी तक समर्थित नहीं है। - ### सबग्राफ मेटाडेटा सभी Subgraph में एक स्वचालित रूप से उत्पन्न `_Meta_` ऑब्जेक्ट होता है, जो Subgraph मेटाडाटा तक पहुंच प्रदान करता है। इसे निम्नलिखित तरीके से क्वेरी किया जा सकता है: @@ -423,7 +421,7 @@ GraphQL स्कीमाएँ आमतौर पर queries, subscriptions deployment एक विशिष्ट ID है, जो subgraph.yaml फ़ाइल के IPFS CID के अनुरूप है। -block नवीनतम ब्लॉक के बारे में जानकारी प्रदान करता है (किसी भी ब्लॉक सीमाओं को ध्यान में रखते हुए जो कि \_meta में पास की जाती हैं): +block नवीनतम ब्लॉक के बारे में जानकारी प्रदान करता है (किसी भी ब्लॉक सीमाओं को ध्यान में रखते हुए जो कि _meta में पास की जाती हैं): - हैश: ब्लॉक का हैश - नंबर: ब्लॉक नंबर From bb594ea9d81f87186ff9043e17a2e722ca32f7ab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:24 -0400 Subject: [PATCH 270/290] New translations graph-node.mdx (Romanian) --- website/src/pages/ro/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ro/indexing/tooling/graph-node.mdx b/website/src/pages/ro/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/ro/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ro/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 7ee7edd92d8d927fc86e41b8d836f1a171fc7999 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:25 -0400 Subject: [PATCH 271/290] New translations graph-node.mdx (French) --- website/src/pages/fr/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/fr/indexing/tooling/graph-node.mdx b/website/src/pages/fr/indexing/tooling/graph-node.mdx index dbed55fcd2d6..a425ac25b17a 100644 --- a/website/src/pages/fr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/fr/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Il s'agit d'une nouvelle fonctionnalité qui sera disponible dans Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 0158e8c5fae832886ab6f3727f6ef0dac04e282c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:26 -0400 Subject: [PATCH 272/290] New translations graph-node.mdx (Spanish) --- website/src/pages/es/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/es/indexing/tooling/graph-node.mdx b/website/src/pages/es/indexing/tooling/graph-node.mdx index 3e87e3a58908..f0dbc4756468 100644 --- a/website/src/pages/es/indexing/tooling/graph-node.mdx +++ b/website/src/pages/es/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Se trata de una nueva funcionalidad, que estará disponible en Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 7c59e23aab2a8b4ac23a2e10d0225dada4991821 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:28 -0400 Subject: [PATCH 273/290] New translations graph-node.mdx (Arabic) --- website/src/pages/ar/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ar/indexing/tooling/graph-node.mdx b/website/src/pages/ar/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/ar/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ar/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From b136c7382c4edb1c5354b88179c614e122ca93b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:29 -0400 Subject: [PATCH 274/290] New translations graph-node.mdx (Czech) --- website/src/pages/cs/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/cs/indexing/tooling/graph-node.mdx b/website/src/pages/cs/indexing/tooling/graph-node.mdx index b6335d705be8..a06e72d7103d 100644 --- a/website/src/pages/cs/indexing/tooling/graph-node.mdx +++ b/website/src/pages/cs/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Jedná se o novou funkci, která bude k dispozici v uzlu Graf 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 1ea97ba6ab48d65e5dbbbfd3323a7c129c46e4a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:30 -0400 Subject: [PATCH 275/290] New translations graph-node.mdx (German) --- website/src/pages/de/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/de/indexing/tooling/graph-node.mdx b/website/src/pages/de/indexing/tooling/graph-node.mdx index 81b54b23959c..a4857509324d 100644 --- a/website/src/pages/de/indexing/tooling/graph-node.mdx +++ b/website/src/pages/de/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Entfernen von Subgraphen -> This is new functionality, which will be available in Graph Node 0.29.x - Irgendwann möchte ein Indexer vielleicht einen bestimmten Subgraph entfernen. Dies kann einfach mit `graphman drop` gemacht werden, welches einen Einsatz und alle indizierten Daten löscht. Der Einsatz kann entweder als Name eines Subgraphen, als IPFS-Hash `Qm..` oder als Datenbank-Namensraum `sgdNNN` angegeben werden. Weitere Dokumentation ist [hier](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop) verfügbar. From ef5375b427d5665d1e013d7f7b6006e39a54168e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:32 -0400 Subject: [PATCH 276/290] New translations graph-node.mdx (Italian) --- website/src/pages/it/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/it/indexing/tooling/graph-node.mdx b/website/src/pages/it/indexing/tooling/graph-node.mdx index 29d3066cb2ae..7c50775bfe03 100644 --- a/website/src/pages/it/indexing/tooling/graph-node.mdx +++ b/website/src/pages/it/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Si tratta di una nuova funzionalità, che sarà disponibile in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 114e021a6c444b8cb510c968776090a503fe83bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:33 -0400 Subject: [PATCH 277/290] New translations graph-node.mdx (Japanese) --- website/src/pages/ja/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ja/indexing/tooling/graph-node.mdx b/website/src/pages/ja/indexing/tooling/graph-node.mdx index 93a57db23e2e..88b32b795699 100644 --- a/website/src/pages/ja/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ja/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> これは新しい機能で、Graph Node 0.29.xで利用可能になる予定です。 - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From eb28b7f02b5772a4dfdf97a45d928f09d21b8f6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:37 -0400 Subject: [PATCH 278/290] New translations graph-node.mdx (Korean) --- website/src/pages/ko/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ko/indexing/tooling/graph-node.mdx b/website/src/pages/ko/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/ko/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ko/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 26550348cc1ae57a895169b2c59758dc7efcd6eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:40 -0400 Subject: [PATCH 279/290] New translations graph-node.mdx (Dutch) --- website/src/pages/nl/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/nl/indexing/tooling/graph-node.mdx b/website/src/pages/nl/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/nl/indexing/tooling/graph-node.mdx +++ b/website/src/pages/nl/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 035c762d0954422ddec85099d39b41b9de4ea0d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:42 -0400 Subject: [PATCH 280/290] New translations graph-node.mdx (Polish) --- website/src/pages/pl/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/pl/indexing/tooling/graph-node.mdx b/website/src/pages/pl/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/pl/indexing/tooling/graph-node.mdx +++ b/website/src/pages/pl/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 35c1ea265549a359c251ee8c07a8547ec5384d90 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:43 -0400 Subject: [PATCH 281/290] New translations graph-node.mdx (Portuguese) --- website/src/pages/pt/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/pt/indexing/tooling/graph-node.mdx b/website/src/pages/pt/indexing/tooling/graph-node.mdx index 8d85735d60bf..f521db588759 100644 --- a/website/src/pages/pt/indexing/tooling/graph-node.mdx +++ b/website/src/pages/pt/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ Para subgraphs parecidos com o Uniswap, as tábuas `pair` e `token` são ótimas #### Como remover subgraphs -> Esta é uma funcionalidade nova, que estará disponível no Graph Node 0.29.x - Em certo ponto, o indexador pode querer remover um subgraph. É só usar o `graphman drop`, que apaga uma implantação e todos os seus dados indexados. A implantação pode ser especificada como o nome de um subgraph, um hash IPFS `Qm..`, ou o namespace de banco de dados `sgdNNN`. Mais documentos sobre o processo [aqui](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 5d15b79cf2f6faec68c987f03520129775966e81 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:44 -0400 Subject: [PATCH 282/290] New translations graph-node.mdx (Russian) --- website/src/pages/ru/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ru/indexing/tooling/graph-node.mdx b/website/src/pages/ru/indexing/tooling/graph-node.mdx index 05fabb843b74..31c4e4aca1cd 100644 --- a/website/src/pages/ru/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ru/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Это новый функционал, который будет доступен в Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 0fa2f7e276895ab03d3b280f16747a2d59b9ab67 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:46 -0400 Subject: [PATCH 283/290] New translations graph-node.mdx (Swedish) --- website/src/pages/sv/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/sv/indexing/tooling/graph-node.mdx b/website/src/pages/sv/indexing/tooling/graph-node.mdx index 3e624ab52527..10f8e8793b0f 100644 --- a/website/src/pages/sv/indexing/tooling/graph-node.mdx +++ b/website/src/pages/sv/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Detta är ny funktionalitet, som kommer att vara tillgänglig i Graf Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From b6ac4084ebe2c84541f4e926a5590e4aea1ecb7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:47 -0400 Subject: [PATCH 284/290] New translations graph-node.mdx (Turkish) --- website/src/pages/tr/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/tr/indexing/tooling/graph-node.mdx b/website/src/pages/tr/indexing/tooling/graph-node.mdx index da782fe0afdc..dc97a872ff32 100644 --- a/website/src/pages/tr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/tr/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> Bu, Graph Node 0.29.x sürümünde kullanılabilir olan yeni bir fonksiyonelliktir - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 311d107e05e031317c1ea39902eebf6bd956829b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:49 -0400 Subject: [PATCH 285/290] New translations graph-node.mdx (Ukrainian) --- website/src/pages/uk/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/uk/indexing/tooling/graph-node.mdx b/website/src/pages/uk/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/uk/indexing/tooling/graph-node.mdx +++ b/website/src/pages/uk/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 46566ba4daa7815f1dcd9110411dfc52efb01f46 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:50 -0400 Subject: [PATCH 286/290] New translations graph-node.mdx (Chinese Simplified) --- website/src/pages/zh/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/zh/indexing/tooling/graph-node.mdx b/website/src/pages/zh/indexing/tooling/graph-node.mdx index ee1e0df027d4..28b672699dc8 100644 --- a/website/src/pages/zh/indexing/tooling/graph-node.mdx +++ b/website/src/pages/zh/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ The command `graphman stats show ` shows, for each entity type/table in #### 删除子图 -> 这是一项新功能，将在Graph节点0.29.x中提供。 - 在某个时刻，索引人可能想要删除给定的子图。这可以通过删除部署及其所有索引数据的`graphman drop`, 轻松完成。部署可以被指定为子图名称、IPFS has、`Qm..`，或数据库命名空间`sgdNNN`。[此处](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop)提供了更多文档。 From 268974fab6da0ae85ec8a8648ea1a98a8da34d2c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:51 -0400 Subject: [PATCH 287/290] New translations graph-node.mdx (Urdu (Pakistan)) --- website/src/pages/ur/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/ur/indexing/tooling/graph-node.mdx b/website/src/pages/ur/indexing/tooling/graph-node.mdx index 9d4206086f59..4ced6b7faf14 100644 --- a/website/src/pages/ur/indexing/tooling/graph-node.mdx +++ b/website/src/pages/ur/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> یہ نئی فعالیت ہے، جو گراف نوڈ 0.29.x میں دستیاب ہوگی - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 408f4c6e1572c6e616ae685d06c645f3af764b77 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:52 -0400 Subject: [PATCH 288/290] New translations graph-node.mdx (Vietnamese) --- website/src/pages/vi/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/vi/indexing/tooling/graph-node.mdx b/website/src/pages/vi/indexing/tooling/graph-node.mdx index b3317ca9716f..673a3ece4d12 100644 --- a/website/src/pages/vi/indexing/tooling/graph-node.mdx +++ b/website/src/pages/vi/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 71d58fe3e38288304f43f98184179e7400725c06 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:54 -0400 Subject: [PATCH 289/290] New translations graph-node.mdx (Marathi) --- website/src/pages/mr/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/mr/indexing/tooling/graph-node.mdx b/website/src/pages/mr/indexing/tooling/graph-node.mdx index 10e682be7f67..15ba0fbb69ab 100644 --- a/website/src/pages/mr/indexing/tooling/graph-node.mdx +++ b/website/src/pages/mr/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ For Uniswap-like Subgraphs, the `pair` and `token` tables are prime candidates f #### Removing Subgraphs -> This is new functionality, which will be available in Graph Node 0.29.x - At some point an indexer might want to remove a given Subgraph. This can be easily done via `graphman drop`, which deletes a deployment and all it's indexed data. The deployment can be specified as either a Subgraph name, an IPFS hash `Qm..`, or the database namespace `sgdNNN`. Further documentation is available [here](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop). From 5ba8cd26049e2129f811764043ebb787677df8e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= Date: Fri, 25 Apr 2025 15:19:55 -0400 Subject: [PATCH 290/290] New translations graph-node.mdx (Hindi) --- website/src/pages/hi/indexing/tooling/graph-node.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/src/pages/hi/indexing/tooling/graph-node.mdx b/website/src/pages/hi/indexing/tooling/graph-node.mdx index 4b6911f0c5cf..c78de7612036 100644 --- a/website/src/pages/hi/indexing/tooling/graph-node.mdx +++ b/website/src/pages/hi/indexing/tooling/graph-node.mdx @@ -340,6 +340,4 @@ Uniswap जैसी Subgraphs के लिए, `pair` और `token` टेब #### सबग्राफ हटाना -> यह new functionality है, जो garph node 0.29.x में उपलब्ध होगी - At some point, एक Indexer किसी दिए गए Subgraph को हटाना चाह सकता है। यह आसानी से `graphman drop` के माध्यम से किया जा सकता है, जो एक deployment और उसके सभी indexed डेटा को हटा देता है। Deployment को या तो सबग्राफ नाम, एक IPFS हैश `Qm..`, या डेटाबेस namespace `sgdNNN` के रूप में निर्दिष्ट किया जा सकता है। आगे का दस्तावेज़ [यहाँ](https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md#-drop) उपलब्ध है।